Headless Drupal hosting without a Drupal team

Decoupled.io runs headless Drupal for you. Each site gets a real Drupal instance with GraphQL and JSON:API turned on, a visual editor for your content team, and a typed TypeScript client for your developers. You build the Next.js or Astro frontend. We run Drupal.

  • Open source: Drupal is GPL-licensed, so your content model and data are not locked into a proprietary format.
  • Isolated: every space is its own Fly.io app, with its own machine, volume, hostname and TLS certificate.
  • Priced openly: a free plan, then $20/month (Starter) or $60/month (Pro). See pricing.

Create a free Drupal space or read how hosting works.

What you get on every space

Every space is a managed Drupal instance, not a Drupal-shaped abstraction. You keep the parts of Drupal that matter for serious content work.

  • Content modeling: content types, paragraphs, taxonomies, references, revisions and content moderation. See the pre-installed modules.
  • GraphQL and JSON:API: both are enabled by default on every plan. There is a GraphiQL explorer at /graphql/explorer.
  • A typed TypeScript client: npx decoupled-cli schema sync generates types from your Drupal schema. See the typed client docs.
  • A visual page builder: Drupal Canvas lets editors arrange your own Next.js or Astro components. See the Canvas editor.
  • MCP tools: 25+ documented tools let Claude, Cursor or any MCP client create spaces, define content types and import data. See the MCP reference.

What you stop doing: applying Drupal updates and security patches, provisioning servers, renewing TLS certificates and running snapshot jobs.

How the hosting works

Every Drupal space is its own Fly.io app. In practice:

  • Per-tenant isolation. Your space has its own machine, regional volume, hostname and TLS certificate. There is no shared database with a customer-id column.
  • Idle stop on Free and Starter, always-on on Pro. Free and Starter machines stop when idle and wake on the first request in about 5 to 8 seconds. Pro machines stay running, so there is no cold start.
  • Daily snapshots. Fly takes a daily snapshot of your volume with 5-day retention, at no charge. The Backups add-on (+$10/month per space) adds nightly database and file backups in Cloudflare R2 with 30-day retention.
  • Edge routing. Requests terminate TLS at the nearest Fly edge and route to your machine.
  • Roughly two minutes to provision. A GitHub Actions workflow creates the app, attaches a volume and installs Drupal.

The architecture and its trade-offs are written up in Why we host every Drupal tenant on Fly.io, including what we gave up by not using Kubernetes.

Speed: where the pages actually load from

Headless Drupal is not on the hot path for your visitors. Your Next.js or Astro frontend serves pages from a CDN or static output, and Drupal is only called on a cache miss, a webhook-driven rebuild or an editor's save.

That is why a Free-plan cold start of 5 to 8 seconds mostly hits editors and rebuilds, not visitors. The Next.js integration module supports on-demand revalidation, so published changes refresh the affected pages without a full rebuild. We do not publish page-speed benchmarks, because your frontend, caching and hosting decide the numbers.

Built for editors and developers

For editors: the Canvas visual editor shows a live preview rendered by your real frontend, with draft and publish. Content moderation and a scheduler are pre-installed, plus a media library and URL aliases.

For developers:

  • A CLI for spaces, schema sync and content import (npx decoupled-cli).
  • A typed client with autocomplete for every content type, built on the GraphQL API. Use client.raw() when you want your own queries.
  • OAuth 2.0 client credentials for protected content and writes.
  • Two open-source starters, Next.js and Astro, with 17 shared components. See starters.

Taxonomies and structure: vocabularies and terms are first-class content. Create them in the Drupal admin or import them as term(vocab) fields from JSON, and query them through GraphQL.

Multiple languages: Drupal core includes content and interface translation. If you need multilingual content on a space, ask us to confirm the modules for your plan before you build on it.

What it costs

Every tier and limit is on the pricing page. Summary:

Plan Monthly What it's for
Free $0 One Drupal space, 24-hour auto-archive, cold start on idle. For trying things out.
Starter $20 Personal sites and low-traffic projects. Idle stop, 4 GB storage per space.
Pro $60 Production. Always-on, 20 GB storage per space.

Add-ons: Backups +$10/month per space, Priority Support +$50/month account-wide (1-hour response instead of 24 hours). Annual billing is $200/year (Starter) or $600/year (Pro). There is no per-entry, per-seat or per-request pricing: users, content, bandwidth and API requests are uncapped, and storage is the only per-space limit.

Custom Drupal and WordPress hosting

Already have a Drupal or WordPress codebase, with your own theme, custom modules or a specific set of plugins? We host that too, on the same platform and the same dashboard, with a quote instead of a fixed plan.

How it works:

  • Your code, your own image. Your repository is built into a dedicated container image for your site, on the same FrankenPHP and MariaDB stack every space runs on.
  • Security updates are still automatic. Every night your Composer dependencies (Drupal core and contrib modules, or WordPress core and plugins) are checked against published security advisories. Updates are applied, install-tested, and rolled out without anyone filing a ticket.
  • PHP and OS patches roll out too. When PHP or the base operating system ships a fix, your image is rebuilt and redeployed.
  • Risky updates are staged first. Updates that could break a site are tried on a staging copy before they reach production.
  • Backups you can restore. Daily backups of the database and uploaded files, with one-click restore from the dashboard.
  • The same dashboard. Your site appears alongside any other spaces, with the same admin login, backups and team access.

What stays yours: code we didn't write, such as your custom theme and custom modules or plugins, is maintained by your team. We can quote that work too.

Moving an existing site? Send us a database export and your files, and we import them as part of setup.

Get a custom hosting quote

Who this is for

  • A Drupal team moving to headless. You know Drupal, you want a Next.js or Astro frontend, and you do not want to become a hosting team.
  • A team comparing Acquia or Pantheon. See vs Acquia and vs Pantheon.
  • A Next.js or Astro team that needs structured content. See the Next.js CMS integration.
  • An agency running a space per client. Each client gets an isolated space.
  • A team using AI assistants that want a CMS they can manage through MCP.
  • A team with an existing Drupal or WordPress site that needs its own modules, theme or plugins. See custom hosting.

Who this isn't for

  • You need FedRAMP or ISO 27001 today. Both are roadmap items, not current authorizations.
  • You want to self-host. Decoupled.io is a managed platform. Drupal core is open source if you want to run it yourself.

Questions we get asked

Do I need a Drupal team? No. We apply core and security updates and run the infrastructure. You still need someone to build the frontend and model the content.

Can my editors work without a developer? Yes for page building and content, once a developer has added the components. Adding a new component is a frontend change (a component.yml plus a React or Astro file).

What happens when my free space is archived? Free spaces auto-archive after 24 hours. Upgrade to Starter or Pro to keep a space.

Can I bring my own modules or theme? On the standard plans we run a curated module set. For your own codebase, custom hosting builds your code into its own image with the same automatic security updates. Ask for a quote.

Can I leave? Yes. Content exports as JSON, and Drupal and the starters are open source.

Get started

  1. Create a free space at dashboard.decoupled.io. No credit card.
  2. Define your content model with the getting started guide, the CLI, or an MCP-enabled assistant.
  3. Connect your frontend to the GraphQL or JSON:API endpoint.
  4. Upgrade when you ship. Move to Starter or Pro when you need to keep a space.

Create a free Drupal space | See pricing

Compare before you decide