What is Umbraco in October 2026?
Umbraco is an open source CMS on .NET, released under the MIT licence. According to Umbraco’s own support policy page, Umbraco 17 is the current long-term support release (released 27 November 2025, end of life 27 November 2028) and runs on .NET 10. Umbraco 18, a short-term release, followed on 25 June 2026.
Two older lines matter if you own a site. Umbraco 13 LTS reaches end of life on 14 December 2026. Umbraco 16 reached end of life on 12 June 2026. Those dates drive most of the upgrade work we get asked about.
Who Umbraco suits
Umbraco suits organizations on the Microsoft stack: .NET developers, SQL Server or SQLite, Azure hosting and Active Directory or Entra sign-in. It is widely used for corporate sites, intranets and multi-site marketing builds in Northern Europe. Editors get a friendly backoffice with document types, blocks and scheduled publishing.
It is a weaker choice if nobody on your side writes C#. A PHP or Node team will be happier on a platform that matches their skills.
The Delivery API and headless Umbraco
Umbraco ships a Content Delivery API that returns content as JSON. It is opt-in: you enable it through the Umbraco:CMS:DeliveryApi:Enabled setting and register it in Program.cs. The endpoints are described in an OpenAPI document. Rich text is HTML by default, and can be output as JSON, which handles internal links better.
Umbraco also sells Heartcore, a hosted headless version. Our Umbraco Heartcore page covers when the SaaS route is worth it. If you already run Umbraco CMS, the Delivery API usually gives you headless without a second product.
Keep Umbraco and add a headless frontend
Keep Umbraco when editors are productive and the backoffice has custom property editors, dashboards or workflow your team paid for. Replace the Razor views with a Next.js or Astro frontend that reads the Delivery API.
Three things need planning: preview for editors, cache invalidation on publish through webhooks, and how multi-site and multi-language trees map to routes. We handle these with our Next.js team, and set up .NET builds beside the frontend pipeline.
When to move off Umbraco, and to what
Move when you have no .NET capacity, when you are stuck on an end-of-life version and the upgrade is a rewrite, or when you want a SaaS with no hosting. Likely targets:
- Payload or Strapi for a Node.js team.
- Drupal when roles, workflows and multi-site matter more than .NET.
- Contentful for a hosted, editor-first platform.
Our migration services cover mapping document types, media and redirects. The migration checklist lists what we test before cutover.
What does it cost to own Umbraco?
The CMS has no licence fee, so the budget goes to development, .NET hosting and upgrades. Umbraco publishes a fixed LTS calendar, which makes upgrade timing predictable: you can plan one upgrade project per LTS cycle instead of reacting to a deadline. Custom backoffice code and paid packages are the usual cost surprises, because each one must be checked on every upgrade. We scope after a short audit, and hourly work uses the $50 to $150 per hour band.
What we build on Umbraco
- Upgrades from Umbraco 7, 8, 10 or 13 to the current LTS, including package audits.
- Custom document types, blocks, property editors and backoffice dashboards.
- Delivery API setup, caching and a Next.js or Astro frontend.
- Integrations with CRM, ecommerce, payment, identity and analytics systems.
- Multi-site and multi-language trees with a clean URL plan.
- Migration from older CMS platforms with SEO safe redirects.
To add engineers, hire Umbraco developers. More on the approach is on our headless CMS page.