Decoupled CMS

What is a decoupled CMS?

A decoupled CMS separates content management from content presentation, similar to a headless CMS, but it still maintains a connection to a defined front-end delivery layer rather than leaving the front end entirely up to the developer. Content is created and stored in the CMS, then delivered to one or more established front ends, typically through an API. 

The distinction from a headless CMS is subtle but matters for planning. A decoupled system still has a defined structure connecting content to how it is displayed. A pure headless system has no front-end component at all. 

What is the difference between a decoupled CMS and a headless CMS? 

Both architectures separate the systems that manage content from the systems that display it, and both typically deliver content through an API. The difference is in how much front-end structure the CMS provides. 

A headless CMS is content-only. It has no front-end delivery layer built in or assumed, and every channel that consumes its content needs a front end built independently. A decoupled CMS still maintains a connection to at least one defined front end, even though that front end runs as a separate system from the content repository. In practice, decoupled architectures are often chosen when a team wants API-based flexibility but still needs a primary website delivery path that the CMS is aware of.  

 How does Xperience by Kentico approach this choice? 

Xperience by Kentico is built as a hybrid headless DXP, so it doesn't force a choice between decoupled convenience and headless flexibility. Website channels keep the visual Page Builder and drag-and-drop editing marketers already rely on, the same territory a decoupled CMS covers. Headless channels expose the same content through auto-generated GraphQL for apps, devices, or any custom front end a developer wants to build. Both run from one content hub, so content isn't duplicated or re-modeled to serve a new channel. Learn more about Kentico's platform capabilities.

How do companies benefit from Kentico's hybrid headless approach?

Organizations using Xperience by Kentico avoid the trade-off that comes with picking a single architecture for the whole business, a philosophy laid out in Kentico's product vision. Marketing can launch a campaign landing page with zero custom front-end work today, while product ships a headless feed to a mobile app next quarter; both pulling from the same content, without stitching together separate systems or vendors. 

See why headless is treated as a feature, not the whole architecture, and explore customer stories to see how organizations have used Kentico's hybrid headless architecture to add channels without a replatform.

When does each architecture fit?

Traditional CMS fits organizations running a single website with no near-term plans to add other channels. Decoupled CMS fits teams that want API-based flexibility while keeping a primary, CMS-aware front end. Headless CMS fits organizations with the development resources to build and maintain independent front ends across several channels. Hybrid headless fits teams that want the flexibility of API-based delivery without giving up marketer-managed page editing.