Decoupled CMS

What is a decoupled CMS?

A decoupled CMS separates content management from content presentation, but keeps both. The back end, where content is created and stored, and the front end, where it's displayed, run as independent systems connected by an API. Unlike a headless CMS, a decoupled CMS still ships a built-in presentation layer, so you can publish with the default front end or build your own.

The term gets confused with "headless" constantly, and the two are related but not interchangeable. Every headless CMS has a decoupled architecture. Not every decoupled CMS is headless. The difference comes down to whether a presentation layer exists at all.

In a digital experience platform context, decoupled architecture is what lets a marketing team keep the templates and visual editing they already know while gaining the ability to push content to other channels through an API, without a full replatform.

What are the key differences between decoupled, headless, and hybrid headless CMS?

• Presentation layer: A decoupled CMS ships one, optional. A headless CMS has none. A hybrid headless CMS has one for web channels and lets you skip it for others.
• Content delivery: Decoupled architecture is proactive; it prepares content and pushes it into the delivery environment. Headless is reactive, it holds content and waits for an API request.
• Developer effort: Decoupled needs less dev work to launch, since a working front end exists by default. Headless needs a custom front end for every channel, built from scratch.
• Editor experience: Decoupled keeps templated, WYSIWYG editing for web content. Headless offers no built-in preview or templating; editors work with structured content only.
• Channel reach: Decoupled favors web plus a handful of API-connected channels. Headless is built for any number of channels, from apps to kiosks to IoT devices, with no ceiling on the front end; see how Xperience by Kentico's development model handles both website channels and headless channels from one codebase. 
  

How does Xperience by Kentico support decoupled and headless architecture?

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.

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

A decoupled CMS keeps a presentation layer alongside its API, content is pushed proactively into a delivery environment, and a default front end is ready to use. A headless CMS has no presentation layer of any kind; it's a content-only back end that waits for something to request its data. A decoupled CMS gives you a head start. 

Decoupled and headless are both alternatives to traditional CMS and both make content portable across channels through an API. The right one depends on how much front-end freedom you need versus how much of it you're willing to build yourself. A hybrid headless platform removes the need to choose one architecture for every channel.