Headless Umbraco

Headless Umbraco, without buying a second CMS The open-source CMS already speaks JSON.

Umbraco's free, MIT-licensed CMS ships headless APIs and webhooks. For most bilingual marketing sites that is all the backend you need — so we build the front end, not a licence purchase.

UmbracoHeadlessNext.jsEN · AR
Track record

We build on Umbraco and on headless platforms, and we publish the cost comparison with its sources — including where Umbraco wins.

Which "headless Umbraco" do you mean?

The phrase covers four different products with wildly different price tags. Getting this wrong is the single most expensive mistake in an Umbraco headless project.

  1. Umbraco CMS, self-hosted. MIT-licensed and free for commercial use, with headless APIs and webhooks included. You supply hosting, a SQL Server, a CDN and backups.
  2. Umbraco Cloud. The same CMS, managed, billed per project from €45 a month. Standard and above carry a website and delivery-API availability target; service credits start at Professional.
  3. Umbraco Heartcore. A separate managed SaaS headless product, priced separately from the CMS.
  4. Umbraco Compose. A content-orchestration platform that federates several source systems into one API. €12,000 a year for Professional, €48,000 for Enterprise, metered by ingestion.

For a bilingual marketing site, options one and two are almost always the right answer. We will say so rather than route you to the expensive end — and if your situation genuinely calls for orchestration across multiple business systems, we will say that too.

What you gain, and what you give up

Decoupling buys you a front end you fully control: performance, framework choice, and the ability to serve the same content to a site, an app or a partner feed. It costs you two specific things.

Neither is a reason to avoid headless. Both are reasons to model the content properly on day one. The full economics are in our three-year cost comparison.

/01

How a headless Umbraco build runs

01

01Model the content, not the page

01

Document types and blocks designed for API consumption rather than a single template — including how English and Arabic vary, which is decided here or regretted later.

02

02Configure and secure the API

02

Delivery API switched on and scoped, access control set, caching and webhooks configured so publishing propagates without overloading the backend.

03

03Build the front end

03

A typed Next.js front end with locale-prefixed routing, logical-property RTL, image handling and the editor preview path.

04

04Cut over safely

04

URL inventory, redirect map, structured data and status-code verification before launch — then an upgrade calendar so you land on an LTS release rather than a twelve-month one.

/02

Which route fits

The four things people mean by headless Umbraco, compared on what decides the choice.

CriterionCMS self-hostedUmbraco CloudHeartcoreCompose
Licence costFree, MITFrom €45/mo per projectPriced separatelyFrom €12,000/yr
Headless API includedYesYesYesYes
You run the infrastructureYes, you doManagedManagedManaged
Editor seatsUnlimitedUnlimitedTier-dependentUnlimited users
Delivery-API availability targetYours to runStandard and aboveTier-dependentTier-dependent
Data residency / on-premisesAnywhere5 regions listedNoNo
Metered by usageNoNoTier quotasPer ingestion
Sensible for a bilingual marketing siteYesYesPartialDifferent problem

Umbraco Cloud figures verified against umbraco.com/pricing on 27 September 2026. Compose figures from a capture of Umbraco's own product page dated 21 September 2026, since that page is not reachable to automated requests. Heartcore tiers are published but were not re-verified here, so they are shown qualitatively rather than priced. All prices exclude VAT.

/03

Related services

Isometric blueprint illustration: one cyan-edged content backend on the left feeding three separate delivery surfaces of differing heights on the right, each linked by a fine connector line.
/01Popular

Headless Umbraco

Keep Umbraco as the editorial backoffice your team already knows, and put a fast Next.js front end in front of it — without buying a second CMS.

Content model and API contract documentationConfigured delivery API with access control and cachingNext.js front end, typed against the API
Isometric blueprint illustration representing Umbraco development — an open-source .NET CMS with a headless content API.
/02Popular

Umbraco Development

Enterprise Umbraco builds for UAE organisations — headless or full-stack, multilingual EN/AR, and engineered to last on .NET.

Information architecture & Umbraco document typesCustom backoffice & editor workflowsContent Delivery API / Heartcore integration
WordPress → Umbraco
/03Popular

WordPress → Umbraco

For organisations standardised on .NET. Move off WordPress onto Umbraco — an editor-friendly CMS your IT function already knows how to host, govern and audit.

Content audit and document-type specificationUmbraco instance configured to your modelMigrated content, media and language variants
/04Popular

Web Development

Web development in Dubai built on Next.js, Sanity and Laravel — fast, SEO-optimised, mobile-first websites and headless ecommerce engineered to convert across the UAE.

Fixed-price discovery sprintCustom, mobile-first website or web appHeadless Sanity CMS your team controls
/00

Further reading

/04

Headless Umbraco — FAQs

Is Umbraco a headless CMS?
Umbraco is a traditional .NET CMS that can also be used headlessly. The free, MIT-licensed CMS lists headless APIs and webhooks among its included features, so a separate front end can consume its content as JSON while editors keep the Umbraco backoffice. You can also run it the conventional way, rendering pages with Razor templates.
Is Umbraco's headless API free?
Yes. The Content Delivery API has been part of core Umbraco since version 12 and ships in the MIT-licensed Umbraco.Cms.Api.Delivery package — no licence, no add-on, no SaaS tier. What is not free is everything around it: hosting, a SQL Server, a CDN and backups if you self-host, or an Umbraco Cloud plan from €45 a month if you would rather not. Note that the API is off by default and needs enabling deliberately, and that its PublicAccess setting defaults to true — so it should be locked down with an API key before it goes anywhere near production.
Do we need Heartcore or Compose?
For a typical bilingual marketing site, no. Heartcore is a separate managed SaaS headless product and Compose is a content-orchestration platform starting at €12,000 a year that federates multiple business systems into one API. Both solve real problems, but neither is a prerequisite for putting a Next.js front end on Umbraco.
Can editors preview unpublished content on a headless build?
Yes, but the preview path has to be built. Umbraco's backoffice previews its own Razor templates, which does not help when a separate front end renders the site. What Umbraco does not offer, and what we will not claim it does, is click-to-edit visual editing against an external front end.
How does this affect Arabic?
Front-end Arabic and right-to-left rendering are unaffected and work well. Two things need planning: block-level culture variance only exists from Umbraco 15 and block structure stays invariant across languages, so reordering blocks in English reorders them in Arabic; and the Umbraco backoffice has no right-to-left layout and ships no Arabic culture file, so Arabic-first editors author in an English admin.
Which Umbraco version should we build on?
Umbraco 17, the current long-term-support release, secure until 27 November 2028. Avoid non-LTS majors, which live about twelve months, and avoid starting anything new on Umbraco 13 — its patches end 14 December 2026 and the .NET 8 runtime under it ends 10 November 2026.

Thinking about taking Umbraco headless?
Let's work out which route you actually need.

Start a project
Start a project