Where it fits
Organisations that want tailored content models and an editor-friendly website, with a team able to maintain a .NET application.
Trade-offs and limitations
The CMS core uses the MIT licence. Umbraco Cloud and commercial add-ons have separate terms and costs. Custom code, packages and major-version upgrades still need engineering.
Deployment and technology
ASP.NET Core and a database supported by the selected Umbraco release; hosting and .NET requirements vary by version. 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 | Opt-in Content Delivery API for headless content; custom business integrations require design and testing |
|---|---|
| Authentication | Backoffice users and permissions; validate any external identity or member sign-in integration for the chosen version |
| Data export | Recovery needs the database, media, application source and configuration. A content API response alone is not a complete site backup |
Migration considerations
Map document types, content, media, languages, URLs and integrations. Check the supported upgrade path and package compatibility, then rehearse on staging with backups and a rollback plan.
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-27. Verify the exact release, edition and extensions before implementation.