Confluence is a collaboration and content sharing platform used primarily by customers who are already using Atlassian's Jira project tracking product. The product appeals particularly to IT users.
$0
Free for 10 Users
Zeplin
Score 6.8 out of 10
N/A
Zeplin, from the company of the same name, is a platform supporting collaboration in application development by engineers and designers by providing an API with popular collaboration, development and prototyping tools and creating a space where productions can be shared and reviewed.
$0
up to 1 project
Pricing
Atlassian Confluence
Zeplin
Editions & Modules
Free
$0
Free for 10 Users
Standard
$6.40
per month per user
Premium
$12.30
per month per user
Data Center
220,000.00
40,001+ Users - Annually
Enterprise
Contact Sales
Free
$0
up to 1 project
Advanced
$15
per month per seat (up to 50 projects)
Basic
$15
per month per project
Enterprise
Contact sales team
Offerings
Pricing Offerings
Confluence
Zeplin
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Prices shown here reflect prices for deployments with 100 users or less. The prices decrease wien the user base surpasses 100.
—
More Pricing Information
Community Pulse
Atlassian Confluence
Zeplin
Considered Both Products
Confluence
Verified User
Anonymous
Chose Confluence
Atlassian Confluence has a more comprehensive and flexible set of capabilities that stand out and made the decision upfront more straightforward for our team. The tools we evaluated have knowledge management, task management and collaboration capabilities, however Atlassian …
Atlassian Confluence is way popular for a larger team and makes collaboration way easier. The community is strong and you get easier resolution against any request. It's integration with other Atlassian products like JIRA is an icing on the cake.
In my experience, Atlassian Confluence is at the top of these tools. I've had first hand experience with other tools and they are not at par with Atlassian Confluence. The versatility of the tool is very well recognized and utilized. Being a new user is not a probably as all …
Atlassian Confluence is a super handy hub for sharing ideas and keeping all your docs in one place. While Jira Service Management is more about handling tickets and support issues, Atlassian Confluence really makes teamwork easy. I feel Atlassian Confluence is user-friendly, …
We choose Atlassian Confluence because it is the reference for managing a SAAS wiki service. And having such a solution in our company to manage the knowledge and especially the knowledge transfer is crucial.
Confluence has a more robust set of capabilities compared to Dovetail and Trello and also was already approved by our legal and compliance teams, so it tends to keep its stickiness due to that. It's also widely known in the market as a knowledge management tool. I would say it …
Overall, Atlassian Confluence is a user-friendly tool and offers such a vast array of capabilities for project and knowledge management purposes and beyond. Other tools listed above have much more limited capabilities, although they are great tools for very specific needs and …
Confluence, since it is part of the overall infrastructure of Atlassian, makes it immensely powerful internally, to build an internal knowledgebase, and is far ahead of its counterparts in Zendesk and Hubspot, which is more centered towards their customers. Confluence is just …
Sharepoint in out organisation was mostly used for collaborating on documents, which to some degree has been moved to Confluence, where the Confluence pages have replaced the specific documents.
Being a company which uses other Atlassian tools, Atlassian Confluence was a great fit; the natural and automatic linking of assets from other platforms made following paper trails seamless. Though the editing options aren't as advanced as some other options out there, it does …
We find Atlassian better for its ease of use, real time editing, integration with Jira for bug tracking, stores our security compliance documents in structured way, it is feature rich and have lots of capabilities.
In the past, I have used MediaWiki hosted locally as well as Microsoft Team Foundation Server. Wiki was simply a nightmare so all the money saved from paying for Atlassian subscriptions was lost in time while trying to use Wiki and format something properly. I haven't used …
Atlassian Confluence is better suited for documenting and acting as a repository for information than the more immediate what is currently being worked on things that are better suited for in Jira. In my opinion, Atlassian Confluence certainly has it's short comings but it is …
We still use Atlassian Confluence only for its integration with Jira and Bitbucket. For everything else, we moved away from it and are using more modern solutions.
We chose Atlassian Confluence over SharePoint because it's much more user-friendly and intuitive. Atlassian Confluence makes collaboration and knowledge sharing easier with its simpler interface and better search. While SharePoint can be powerful, it often feels clunky and …
The alternatives tested are based only on the whiteboarding functionality added by Confluence Whiteboard, and not the core Confluence functionality (documentation).
Again, Atlassian Confluence is efficient when paired with Jira and can do most of what a company needs it to do. But, I thi Spekit is better for "just-in-time" learning, Sharepoint is better for file hosting and organization, Asana is much better for project/task management, …
We were inclined to use Atlassian Confluence for its easy collaboration with Jira which is used for tracking project development tasks and issues. Using Atlassian Confluence, content creation became easy and even applying access control to the created content was possible. It …
We used to use a Wiki site, but that was locally hosted, and when the server was powered off, you could not access it. Moving to Confluence in the cloud is much easier. Also, the interface is much easier to use and expand.
Zeplin is used for us purely as a handoff tool. It keeps it clean and clear for devs and product managers what is completed. It has some good labels and other organizing features. The different levels of access are also super helpful to give the correct people the view they …
As our project is large and there are many modules and they should be consistent. So, Zeplin's style guide can be shared globally across different projects and we can easily ensure consistency across all modules. Zeplin automatically exports assets in multiple file formats like …
Actually, we didn't select Zeplin. After a long time of internal discussions, the majority of the team decided that we want to move to Figma. We still use Zeplin as a legacy, but we don't use it for new features. In my opinion, it's less flexible than Figma, which allows …
We went without a tool like Zeplin for a long time, but as we grew we needed to get a better handle on the design process and handoff to engineering. We went straight to Zeplin off of numerous recommendations and didn't look back. We have had a great experience with Zeplin.
Zeplin is more focused on the handoff than in the creation itself. The other alternatives can do both, but Zeplin is an awesome tool for the handoff part. It depends in how big is your team and how the workflow is organized to understand whats the best tool for your team.
It was a business need from different departments. From an IT point of view, we have been a part of purchasing and setting up. However, the decision to go with Zeplin was not ours.
Out of all of the products that I have used to support design-to-development handoffs, Zeplin is my favorite. It’s pretty lightweight and easy to use (once you get the hang of it). Zeplin also has a smooth interface and is, generally, clearer to use than other tools, such as …
These other tools are really helpful products for creating and sharing wireframes / prototypes. However, Zeplin is the best tool for the actual hand off between the design and development teams once the design is actually ready to share. Zeplin fills this gap and improves the …
Zeplin is simpler. Zeplin lacks prototyping on par with Invision. Zeplin doesn't give a direct code for Android and iOS like Figma does. Zeplin doesn't have a lot of advanced features like Invision, for example, whiteboard. But Zeplin is good for at its job which is to share …
Zeplin is a really nice lightweight app, that is easier to use than Invision for sharing purposes. Invision does primarily handle prototyping, which Zeplin does not do. Abstract is my product of choice but is also a slightly different tool — almost a Github for design. It …
We chose Zeplin because it allowed our product and design teams to collaborate more effectively, while providing the rest of the organization an easily accessible location to access up-to-date assets. While InVision's interface can be more intuitive, we prefer Zeplin because it …
Marvel is a pretty expensive application for what it gives you, it is a pretty good tool but I think the handoff is not as good as Zeplin's. I think the style of Zeplin is more oriented to developers and Marvel is more oriented to the designers. I like the way Zeplin is …
Zeplin is great to inspect and share user interfaces, specifications and assets, perfect for developers. Tools like Invision and Marvel are much better to create prototypes for both developers, coworkers and even stakeholders, but they don't have this kind of feature …
For my company needs, Zeplin comes as the best tool in its category. Zeplin's competitors are great tools but they either offer way too many features or are priced above Zeplin with the same features.
Zeplin is in the right spot for both pricing and features.
I know there are other products out there but Zeplin has been so effective that I haven't even bothered to look elsewhere. The whole experience of Zeplin has been excellent. However, once Adobe XD is more built out Zeplin will finally have a formidable competitor as it will be …
Zeplin is much better when it comes to seeing the properties and CSS code of the design elements. Our developers love it when they get all that info from the Zeplin file.
Zeplin is the only solution tailored for this common use case. Previously we just shared files in dropbox but that was messy and didn't allow for specific comments, etc.
Atlassian Confluence is a great tool for housing important information and resources across the organization, as it's very easy to search and find content across different teams and departments. The search function is mostly very accurate and the additional tagging with keywords also helps in the search experience. It's also good at tagging other team members, which triggers an automated email to them. Atlassian Confluence also has an extensive template library for all kinds of purposes like project management, etc., which saves time overall.
I still have some issues, especially with color integration between the style guide and also project. When we update the colors, it's not automatically sync to every project. Aside from that, zeplin solves my problem for hand-off design from design to developer. I set zeplin is source of truth design file
Its integration with Jira for tracking development and the bugs and work linked to detailed Confluence documentation.
We use it extensively for writing Software Product Requirement Documents, feature specs, architecture designs, and retrospectives.
Our company follows compliance very seriously, so it helps in streamlining all documentation for ISO27001/27017 compliance and security-related information.
Its integration with various tools allows us to create flow diagrams which are often required to make client and customer understand the overall flow of interactions across various modules of the design architecture
I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.
It's very intuitive for most things, making it easy to jump in and start creating pages and collaborating. This makes it ideal for onboarding new members to the team. There are a few areas that could be a little smoother, but overall it's a great experience.
Zeplin's component management and style guide help us to be consistent across whole product and it so easy to use for non-technical person. It is now easy to collaboration for designes between different teams like stackholders, product owner, UI/UX, developers and testers. Now there is only one point of reference is Zeplin so it is so easy to get details without asking designer or developer again and again.
We never worked against the tide while using Confluence. Everything loads considerably fast, even media components like videos (hosted on the platform or embed external videos from Youtube, for example). We are not using heavy media components a lot, but in the rare occasion we happen to use one we have no problems whatsoever.
This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.
Zeplin has classic support with a chat from the website. It's working fine, and we're also getting the support needed when needed. However, Zeplin is very good at closing the incidents and moving on. It was a while ago we had a case with their support so that it might have improved since then.
Atlassian Confluence is a super handy hub for sharing ideas and keeping all your docs in one place. While Jira Service Management is more about handling tickets and support issues, Atlassian Confluence really makes teamwork easy. I feel Atlassian Confluence is user-friendly, integrates smoothly with other Atlassian tools, and helps everyone stay in sync. It's great for brainstorming, and project planning as well. Overall, it is a great way to boost collaboration and ensure all team members are on the same page.
Out of all of the products that I have used to support design-to-development handoffs, Zeplin is my favorite. It’s pretty lightweight and easy to use (once you get the hang of it). Zeplin also has a smooth interface and is, generally, clearer to use than other tools, such as InVision. Plus, all of the plug-ins that you can use with Zeplin have supported the design-development relationship and workflows in which I’ve been involved in more efficient, clear, and effective ways than I’ve seen with any other product.
Merging instances has saved search time - We used to have several instances of Atlassian Confluence, which means they're separate and so can't communicate with each other. We've since merged into one instance and now with the help of the search feature can find the documents you're looking for in seconds rather than several minutes.
Cross linking product assets streamlines following paper trails - Being able to click on a BitBucket link from a Confluence page which then links to a JIRA ticket means you can follow paper trails really easily; seconds rather than several minutes.
We're using the free plan, so it fits in our needs, although we're limited to create only one project at a time
Sketch has some plugins that offers exactly what Zeplin does, for free
The integration with design apps (Sketch, Photoshop, XD) and collaboration (Slack and Trello) helps our team to better communicate and be notified on every update