decoupled.io
← All Articles
Architecture

Decoupled.io FAQ: Who It's For, Support, Languages, CDN and Workflows

Jay Callicott··6 min read

These are the questions buyers ask us most. Each answer starts with the short version. Where something is not offered or not guaranteed, we say so.

What are the disadvantages of a headless CMS?

A headless CMS has real costs: you build and host the frontend yourself, previewing content takes extra setup, and you need developers for changes a traditional CMS handles with a theme. In exchange you get one content source for many channels, freedom to choose your framework, and a cleaner separation between content and design.

Disadvantage What it means in practice
No built-in frontend You need to build and host the site, usually with Next.js, Astro or similar
Preview takes setup Live preview needs a draft mode on the frontend; see draft preview
More moving parts CMS, frontend host, build hooks and caching must work together
Developer dependency New page layouts often need a developer unless you add a visual builder
Cost of two stacks You pay for the CMS and the frontend hosting

A traditional CMS is still the right call for a simple brochure site run by one non-technical person. Our guide headless vs traditional CMS covers how to decide. Decoupled.io reduces some of these costs with a visual page builder (Drupal Canvas) and a generated typed client, but it does not remove the need for a frontend.

Who is Decoupled.io for, and what use cases fit best?

Decoupled.io is for developers and teams who want a managed headless CMS on open-source Drupal, without running servers. Best fits:

  • Frontend developers and agencies building Next.js or Astro sites that need structured content, GraphQL or JSON:API, and a typed TypeScript client.
  • Teams using AI builders and agents such as Lovable, Bolt, v0 or Cursor, which can manage content through the 25+ MCP tools.
  • Drupal teams that want Drupal's content modeling without the hosting and patching work. See Drupal hosting.
  • Marketing teams that need drag-and-drop page editing via Canvas or the Puck editor.

Weaker fits: teams that need to deploy arbitrary custom Drupal modules (the module set is curated), or buyers who need certifications we do not yet hold. Ask us what we can document today.

What support tiers and response times are offered?

Standard support has a 24-hour response target across email and chat on every plan. The Priority Support add-on (+$50/month, account-wide) shortens the response target to 1 hour. Both are listed on the pricing page. We do not currently publish a contractual uptime SLA on the pricing page; if you need one in writing, contact us.

Can Decoupled.io manage multi-language sites?

Yes. Decoupled.io is built on Drupal, which has multilingual and translation workflows in core. Our platform pages describe support for 100+ languages with content translation. You define which content types and fields are translatable, translate entries per language, and request the language you want from the GraphQL or JSON:API endpoints. Your frontend handles locale routing, for example with Next.js internationalized routing.

Does Decoupled.io have a built-in CDN for sub-second page loads?

Partly, and we want to be precise. Media uploads are served with CDN delivery and automatic WebP conversion. Requests to your space hit the nearest Fly.io edge for TLS and then route to your space's machine, and Pro spaces are always-on. Starter and Free spaces stop when idle and take about 5-8 seconds to wake.

What we do not claim: a guaranteed page-load time. In a headless setup, page speed is mostly decided by your frontend. For sub-second pages under heavy traffic, the standard pattern is to statically generate or cache pages on a frontend host with its own CDN (such as Vercel or Netlify) and let the CMS API serve builds and revalidation, as described in CMS preview, webhooks and revalidation. We have not published load-test benchmarks.

Does Decoupled.io have strong editorial workflows and versioning?

Yes. Content moves through Draft, Review, Published and Archived states with role-based permissions, scheduled publishing, email notifications, revision history and content comparison, all from Drupal's content moderation. Roles include Content Creator and Editor. See content docs for the full list.

Next steps