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.
$6.40
per month per user
zeroheight
Score 8.6 out of 10
N/A
zeroheight helps teams create, manage and maintain their design systems. Using zeroheight, designers, engineers, and product teams can collaborate and build design systems that can be easily shared across teams.
$49
month
Pricing
Atlassian Confluence
zeroheight
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
Starter
$49
month
Enterprise
Custom Pricing
Offerings
Pricing Offerings
Confluence
zeroheight
Free Trial
Yes
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
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
zeroheight
Considered Both Products
Confluence
Verified User
Manager
Chose Atlassian Confluence
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.
I would recommend Atlassian Confluence for companies that want to have internal documentation and minimum governance processes to ensure documentation is useful and doesn't have a lot of duplicated and non-updated content. I wouldn't recommend Atlassian Confluence for companies with a low budget since this product might be a little costly (especially with add-ons).
For creating and maintaining a component library, it is a fantastic tool that creates an interface between Developers, UX Engineers and Designers. It is easy to get both general information about a component, but also incredibly detailed information when looking at the component on a pixel-level, where information on paddings, margins, colors, fonts etc. can be easily accessed.
Cross product linking - If you use other Atlassian products then Atlassian Confluence is a no-brainer for your source of documentation, knowledge management etc. You can show previews of the linked asset natively E.g. showing a preview of a JIRA ticket in a Atlassian Confluence page.
Simple editing - Though the features available may not be super complex right now, this does come with the benefit of making it easy to edit and create documents. Some documentation editors can be overwhelming, Atlassian Confluence is simple and intuitive.
Native marketplace - If you want to install add-ons to your Atlassian Confluence space it's really easy. Admins can explore the Atlassian marketplace natively and install them to your instance in a few clicks. You can customise your Atlassian Confluence instance in many different ways using add-ons.
UI Design is very simplistic and basic could make use of more visually interesting colour choices, layout choices, etc.
Under the 'Content' menu, it defaults to having a landing page for all L1 and L2 category pages. Meaning as long as the broader content category has a sub-category, it still creates a separate landing page. In my team's case, this often creates blank pages, as we only fill out the page at the lowest sub-category (L3).
Hyperlinks are traditionally shown as blue, however, this results into very monotonously blue pages in cases where a lot of information is being linked.
when opening a component image (which opens a new page where the detailed information like paddings and colors are shown), the zoom can only be done by buttons, I'd prefer to be able to use my mouse scroll and for vertical / horizontal scrolling to do ctrl+scroll or ctrl+shift+scroll or something like that
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.
Great for organizing knowledge in a hierarchical format. Seamless for engineering and product teams managing software development. Helps in formatting pages effectively, reducing manual work. Tracks changes well and allows for easy rollbacks. Granular controls for who can view/edit pages. Search function is not great which needs improvement. Hire some google engineers
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.
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 complex, making it harder for our team to actually use it.
I have used and still use Sketch and Zeplin too, but they serve other purposes for us. Sketch is used to design the components themselves and they are then exported to Zeroheight where they are showcased and enriched with textual information. Zeplin is used to design application pages, and again the components are exported to Zeplin from Sketch. But Zeroheight is mainly used for the development of the components themselves as well as a documentation for our design guideline in general. It is also used by us for design tokens and patterns, as well as other information on the design guideline, so if someone wants to understand the "why" of a design decision, the explanation can be usually found in Zeroheight too.
increased quality, as less misunderstandings or communication problems occur
increased speed of development, as it is a single source of truth for us. The developer can rely on the information in Zeroheight being correct so that he doesn't have to iterate his code again and again.
