Comparing Exponential on facts
Contents
Rules for a fair comparison
- The same requirements for every system, weighted before you look at any of them.
- The same kind of evidence: a proof of concept for each finalist, not a demo for one and a brochure for another.
- Documented facts only. For Exponential, every fact has a source in the repository or this help; ask the same of the others.
- The same time horizon for cost: several years, not the first invoice.
The sales section uses the same discipline: Comparing Exponential factually.
What to compare
| Dimension | For Exponential, see |
|---|---|
| Content model | The Exponential 6 kernel |
| License and lock-in | Licensing for adopters |
| Hosting flexibility | The PHP stack |
| Security process | SECURITY.md |
| Total cost | Total cost of ownership |
| Ecosystem and help | The ecosystem for decision makers |
| Migration effort | Migrating |
Traps
- Feature lists. A checkmark says nothing about how well a feature fits your work. Test the ones that matter.
- Numbers without dates. Ask when and how a number was measured.
- License fees as the only cost. Work, hosting and upgrades usually cost more (What you do not pay for).
- Comparing a product line with one product. Exponential has a family; compare the product that fits (Choosing a product).
Related pages
- Evaluating Exponential
- The evaluation scorecard
- Objection: why not another CMS
- Positioning and value proposition
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.