Document360 by Kovai is presented by the vendor as a knowledge base software that scales with a product. Document360 helps users' teams create, collaborate and publish self-service knowledge base.
N/A
Paligo
Score 9.8 out of 10
N/A
Paligo, headquartered in Stockholm, offers their component content management system (CCMS), supporting the creation and publishing of technical documentation and help systems.
$4,800
per year per seat
Pricing
Document360
Paligo
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Document360
Paligo
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
Document360
Paligo
Considered Both Products
Document360
No answer on this topic
Paligo
Verified User
Employee
Chose Paligo
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
DOC360 is more than just a resource.Doc360 is an indispensable tool for any team seeking something distinctive, visually appealing, and highly efficient. Having tried various Knowledge bases in the past, DOC360 stands out for its exceptional ease of use, functionality and aesthetic appeal earning praise both from me and my team
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.
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
Document360 is an exceptional knowledge base software that streamlines our documentation processes, empowers collaboration, and enhances our efficiency in training our consultant
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.
All the support requests I've submitted have been resolved in one way or another. Sometimes it takes some back and forth, which is to be expected. This is where being on a different continent becomes a drawback. Since we became Enterprise users, we've also had an additional level of help and support from a dedicated account manager in the US, and the resolutions seem to come more quickly
Document360 is the first knowledge base customer support tool that our organization implemented, and this tool has increased our team's productivity drastically. One of the reasons we purchased this tool was the price. Document360 has a lot of online video tutorials which again helped our decision to purchase this tool.
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 Flare desktop product was prone to errors and issues. The flexibility of assigning Paligo licenses was a huge factor, as was the stability of the cloud platform.
I am not involved in the financial decisions for my company regarding Paligo; the decision to migrate our content to this environment predates my hiring. However, I know that the migration effort from WordPress to Paligo was an initially heavy lift, but any content migration effort would be. I believe that ultimately, getting our content out of WordPress was a positive move, and I look forward to seeing what Paligo will help us accomplish in the future. Sorry, no hard numbers from me. :)
