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
Paligo
Score 9.0 out of 10
N/A
Paligo is a component content management system (CCMS) that helps teams manage complex technical documentation through structured authoring, content reuse, and controlled publishing.
$4,800
per year
Pricing
Atlassian Confluence
Paligo
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
Professional
from $4800
per year
Business
Contact Sales
per year
Enterprise
Contact Sales
per year
Offerings
Pricing Offerings
Confluence
Paligo
Free Trial
Yes
No
Free/Freemium Version
No
No
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.
It has great features like integration and real time collaboration with new features like AI and automation. So it gives an edge over other tools I have used in the past few years. I am sure there are a lot of features which I have not explored yet, but the features I am using …
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 …
The main reason for moving to Atlassian Confluence was for: 1) Having 1 space that holds all of the org's documentation and knowledge sharing 2)We already used JSM and Jira so it would an organic move to have Atlassian Confluence as our main documentation hub 3) The cost …
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 …
I was working with 10+ CMS:es (list here is not possible choose them from) “all my active work life” and Paligo GUI is unique: No or very few systems of this complexity have a rational GUI. Paligo stands out here and is very user friendly! When it comes to style sheets and …
Paligo gives you the benefits of a fully integrated XML content database, making the whole package much easier to setup and use than a system using Oxygen. It's much easier to set up and far less expensive than Adobe's XML offerings. The cost is comparable to MadCap, but all …
I was not part of the selection process / did not evaluate other tools. I had previously been authoring my content in Google Suite or directly in our Learning Management System. Both of those were hells of information duplication.
We were using our own, custom management scheme - relying on tools like Sharepoint to store and collaboratively edit. But we were lacking the reusability feature and content control features that Paligo provides.
Compared to Author-It, Paligo is a godsend. It's so much more performant, the output quality is much higher, and the user experience is unmatched. Before we switched to Paligo, I had to spend multiple working days just fixing the broken output that Author-It has given me, …
We moved from Flare to Paligo. One of the main reasons was the fact that Paligo is a cloud product. Collaboration with anyone outside of our team was more difficult with Flare. Also, maintaining a server for Flare content was going to become an issue, and overall I felt the …
They are both good documentation options, but the cloud-native capabilities and intuitive UI of Paligo, plus it's ability to produce excellent output for both PDF and HTML5 were the main reasons I chose Paligo. I am very satisfied with my choice.
We selected Paligo over the alternatives for a variety of reasons: It was cloud-based (usable on a Mac) It had the features we needed: Content reuse Variables Easy restructuring and maneuverability of content
Better Support than any of the others; Ability to migrate at cost (unlike AIT and Flare); Teamwork and centralized variables (unlike Word, Google Docs, FM); Diff and Revert (must-have feature); L10N features (better than all others).
I trialed a version of Oxygen XML editor, but the fact that Paligo is cloud-based and integrates directly to Zendesk sold me, even though Oxygen XML is essentially the de facto standard for most structured authoring.
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.
Paligo is particularly well suited for developing similar document sets for multiple products or product lines. It is not a page layout application, so don't expect the same capabilities as popular applications for graphics-heavy documentation. With some up-front time developing good layouts, however, Paligo does manage to create very usable PDF output for customer-facing documents.
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
The review mode is super convenient. Comparing a snapshot of the previous versions with the current one clearly outlines the respective changes and reduces the necessary content to review tremendously.
The option to reuse text fragments is another handy feature. Text fragments will be updated whenever the original text fragment is altered is also extremely helpful.
Managing a content's structure was never easier. An intuitive drag & drop functionality allows you to design your document's structure however you like.
You can also fork content, in addition to reuse text fragments. This is another helpful option that no longer requires you to create repetetive chapters over and over.
The amount of CSS/JS required to customize a site's appearance can be cumbersome
Product documentation can be lacking, specifically with integrations; in some cases, support offered no real help when trying to solve a problem with an integrated service
Some features require extensive development experience to use, which can sometimes be an obstacle to less-experienced team members
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.
Generally, I'm very happy with Paligo and the productivity gains that I get from using it. There are a few arbitrary limitations on structure, and when applying conditional formatting, that I don't really understand. Unlinking / editing reused text uses this broadly inscrutible colour-coding that I just hate. It would be nice to double-click a component, make edits, then respond to a popup asking if I want to confirm the edit for all linked content, or unlink this instance. Likewise converting from an informal topic insertion to duplicates of its raw contents.
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.
So far, support has been excellent. They reply very quickly and give in-depth replies. Solutions advisors and account managers have also been very responsive and clearly focused on creating the best experience for implementation. And that's only when the answers can't be found in excellent product documentation. The online training class and tutorials are also very good.
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.
Paligo gives you the benefits of a fully integrated XML content database, making the whole package much easier to setup and use than a system using Oxygen. It's much easier to set up and far less expensive than Adobe's XML offerings. The cost is comparable to MadCap, but all our content was already in Docbook, so the transition to Paligo was nearly seamless.
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.
Positive - has allowed us to create templates for integration documentation. this has greatly sped up our process for creating articles for each of our integrations, which we haven't had up to this point.
Positive - has created greater alignment between the self-service content team and the marketing team.
Positive - has introduced a review and feedback workflow for our content creation that was not available in ZenDesk. The feedback directly in the app allows me to pinpoint comments about text and other elements so my writers can address them directly and become better writers in the long term.
Negative - long ramp up time due to a completely different approach to creating content. My team was training in early August and we have not yet published our new help center (though, to be fair, it is a lot of content that had to be completely rewritten)
Positive - any UI updates only require updating a single image, which has saved us dozens of hours of updating already.