Hubspot Content Hub is used to take control of content assets. The unified platform is used to manage, update, and distribute content from a central location, ensuring everyone has access to the most up-to-date and relevant materials.
$20
per month
Paligo
Score 9.4 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
HubSpot Content Hub
Paligo
Editions & Modules
Starter
$20
per month per seat
Content Hub Professional
$500
per month 3 seats included, $50 for each additional seat
Content Hub Enterprise
$1500
per month 5 seats included, $75 for each additional seat
Professional
from $4800
per year
Business
Contact Sales
per year
Enterprise
Contact Sales
per year
Offerings
Pricing Offerings
HubSpot Content Hub
Paligo
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
Annual commitment required. A discount is offered for annual billing.
If you want all your marketing activities to be in one place, where your CRM and customer data exist, go for Hubspot's entire suite, which could include CMS, depending on your needs. If you have to create a company blog, marketing landing pages for events or lead generation, or send decently designed newsletters, Hubspot does the job well. Any company that has grown to enterprise level or has fragmented marketing should probably not use Hubspot CMS because of the fragmented activities that might occur. Hubspot's reporting can also break. Also, if you want your designed pages to be very creative with many animations, Hubspot CMS is probably not the way to go. But for anyone who is still finding their footing, go for it.
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.
Although you can integrate it with Google Analytics, there is still a significant difference between what each tells you about [a] number of visitors to a given page, etc.
There's a lot to the program and it's not always intuitive where to go for a feature. Though the help center and academy are good and usually have the answers, having to look things up isn't.
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 don't think we justify the amount of usage we have of CMS Hub professional. We might discontinue it to save some bucks. But if we ever need an extensive solution, we'll come back to it, as we already other products of Hubspot (Sales Hub, Reporting, Automations)
HubSpot CMS HUB is well-rounded and brings a robust list of capabilities while maintaining an ease-of-use that beginners can engage. HubSpot is by far the best at doing this among the half-dozen or so CMS platforms I've used in my 20+ years experience. It turns glorified business card websites into purposeful marketing machines that become a key part of a marketing strategy rather than a complicated and frustrating mess.
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
We have about 10 seats that were needed. Wanted a sales platform that had good status and reputation. HubSpot was the best choice for me given Salesforce not being the best in the past. Price was appealing and our team liked the overlay. Other options do not provide the same ability with data
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. :)
