Where it fits
Organisations needing content types, editorial permissions and a maintainable publishing architecture.
Trade-offs and limitations
Module compatibility and major-version upgrades need planning. Open code does not remove agency or hosting dependency.
Deployment and technology
PHP, Composer and a supported database. Self-hosting requires a supported deployment, capacity planning and a named maintainer. Consult the official installation guide for the current version.
Portability and integration
| API | Core JSON:API and REST capabilities when configured |
|---|---|
| Authentication | Core roles and permissions; SSO typically requires additional configuration or modules |
| Data export | Database, files and configuration export; migration mappings remain important |
Migration considerations
Map content fields, languages, aliases, media and permissions; reconcile redirects and metadata after import.
Security and ongoing costs
Budget for infrastructure, implementation, monitoring, patching, backups, restore tests and user support. Check the supported release and current advisories with the project. An open licence is not a security guarantee.
Freedom score and exit difficulty
A complete, evidence-backed assessment of all 15 criteria is required before publishing a score. Exit difficulty depends on your customisations, data model, integrations and operating documentation. This profile does not claim a hands-on benchmark or a complete security assessment.
Primary sources
Profile reviewed 2026-09-13. Verify the exact release, edition and extensions before implementation.