Componize vs. Paligo Comparison Chart

Pros

• Native SaaS, not built on an older technology base. The product is robust, intuitive with good functionality. Supports versions (branching), workflows and meta-tagging. We use it for a flat model w/o versions and only use branching for making changes then merge back. We don't localize so haven't experience that workflow. The product seems very stable. And for a SaaS solution you don't feel the latency and doesn't impact work.
• The simplicity, a very intuitive interface, a reliable uptime, and a first-class support for small and large issues that may arise. Notably simple image processing can be added. When it comes to managing translations, Paligo has made it very convenient for the user and you soon get a feel for how the other languages are developing, while the original language can be version managed, so that a possible update of e.g. a product manual does not become a big burden for the user, but on the contrary, Paligo offers a very controlled way of working, even for groups of authors. In short, Paligo is a professional content management system but which has retained simplicity and logic for ordinary people.
• All tools are well-designed for our uses, it's not a simple editor. Very easy to learn as well, all good!
• Search capability, content reuse options, assignments with approvals/rejections and format stability.