Most "Drupal vs X" content is written by whichever side wants your money. The SaaS vendors treat Drupal as something to be educated past. Drupal agencies treat the SaaS vendors as toys. Both are wrong often enough that a buyer doing the comparison in 2026 deserves a fairer read.
This is the index for a series of eight comparisons. Each one pits Drupal against a specific headless CMS on the same twelve dimensions: content modeling, APIs, editorial experience, localization, workflow, hosting and operations, pricing model, lock-in, AI agent support, and who each is actually for. Each names at least two things the other product does better than Drupal, because that is always true.
We run decoupled.io, a managed headless-Drupal platform, so we are not neutral. We have tried to be fair anyway. If you think a comparison is unfair to a vendor, tell us and we will fix it.
The short answer
- Drupal's advantage is the content model and who owns it. Entity-field modeling, revisions on everything, moderation workflows, and translation are in core, and the data sits in a database you control.
- Drupal's disadvantage is that someone has to run it. PHP, Composer, security releases, and a hosting bill are your problem unless a platform takes them off your hands.
- The SaaS vendors win on time-to-first-page and polish. Contentful, Storyblok, Sanity, and Hygraph all get a team editing content in an afternoon. Drupal historically took a sprint.
- The open-source alternatives win on developer fit. Strapi and Payload are the right call for JavaScript teams shipping one application, and WordPress is the right call for a blog.
- Pricing models differ more than prices. SaaS meters entries, seats, locales, or API calls. Drupal meters nothing; you pay for compute and people.
- The gap Drupal actually has to close is ergonomics, not capability. That gap is what managed platforms like decoupled.io exist to close.
The field at a glance
| License | Model lives in | Metered on | Visual editing | Where it beats Drupal | Where Drupal beats it | |
|---|---|---|---|---|---|---|
| Contentful | Proprietary SaaS | Vendor cloud | Users, locales, API calls, records | Studio (Premium only) | API/CDN maturity, marketplace, enterprise polish | Modeling depth, workflow in core, cost at scale, ownership |
| Strapi | MIT | Your Node app (schema files) | Cloud plan per project | Live preview, no page builder | JS-native DX, fast first API, transparent cloud pricing | Modeling depth, moderation, localization, permissions |
| Sanity | Studio MIT, Content Lake proprietary | Vendor cloud | Seats, API requests, bandwidth | Presentation tool | Real-time collaboration, Portable Text, React DX | Ownership, workflow, per-seat cost for big teams |
| Storyblok | Proprietary SaaS | Vendor cloud | Seats, API requests, traffic | Best in class | Visual editing, marketer autonomy, Figma workflow | Relational modeling, revisions, seat caps, ownership |
| Hygraph | Proprietary SaaS | Vendor cloud | Entries, seats, API ops | Basic | GraphQL DX, Content Federation | Unmetered content, workflow, localization, cost at scale |
| Payload | MIT | Your Next.js app (TypeScript) | Self-host or Payload Cloud | Live preview, blocks | Type safety, Local API, single-app simplicity | Editor-driven modeling, workflow, multi-site governance |
| WordPress | GPL | Your PHP app plus plugins | Hosting only | Gutenberg | Ease, hosting cost, talent pool, plugin breadth | Structured content in core, revisions, moderation, multilingual |
| Contentstack | Proprietary SaaS | Vendor cloud | Custom enterprise contract | Yes | Packaged enterprise tooling, support, no Drupal staffing | Ownership, cost transparency, partner pool, workflow depth |
The eight comparisons
Drupal vs Contentful
The classic rent-versus-own decision. Contentful has the most mature delivery API and the biggest integration marketplace in headless, and its onboarding is excellent. It also went from free to $300 a month with nothing in between, and gates Studio, personalization, and AI behind a custom-priced Premium tier. Drupal wins on content modeling depth, editorial workflow, localization, and cost once the team or the catalog grows.
Drupal vs Strapi
Two open-source CMSs, one in Node.js and one in PHP. Strapi gets a JavaScript team to a working API faster than anything else on this list, its cloud pricing is published per project, and self-hosting is real. Drupal wins when the content model is complex, when editors need moderation and revisions on every entity, and when permissions and translations have to survive an enterprise audit.
Drupal vs Sanity
Sanity is the developer-first choice with real-time collaborative editing that Drupal does not have. Portable Text is a genuinely better rich-text format than HTML blobs. The trade is a proprietary hosted datastore, per-seat pricing that grows with the editorial team, and single sign-on as a four-figure monthly add-on. Drupal wins on ownership, workflow, and the cost of a large editorial team.
Drupal vs Storyblok
Storyblok has the best visual editor in headless. If marketer autonomy is the deciding factor, it wins, and Drupal Canvas is not yet a match. Storyblok also caps seats per tier, meters API requests, and puts GraphQL and SSO behind custom pricing. Drupal wins on relational modeling, translation as revisions, and teams too large for seat caps.
Drupal vs Hygraph
Hygraph is GraphQL-native and its Content Federation can stitch a PIM, a DAM, and a commerce API into one endpoint. It also meters entries, and the paid tier caps at ten thousand of them. Drupal's GraphQL is a contributed module, which is worse, but Drupal never charges for the next entry, which for content-heavy sites decides the question.
Drupal vs Payload
Payload installs inside your Next.js app and gives TypeScript teams end-to-end types and a database-direct Local API. For one product with developers on hand, it is often the simpler choice. Drupal wins when editors need to change the content model without a deploy, when multi-stage workflows matter, and when one platform has to govern many sites and brands.
Drupal vs WordPress
The most searched comparison in this series and the least about headless. WordPress is easier, cheaper to host, and has the largest talent pool of any CMS. Its content model is post-centric and needs plugins to become structured, and the 2024 dispute between Automattic and WP Engine put governance risk on the table. Drupal wins on structured content, entity revisions, moderation, and multilingual in core.
Drupal vs Contentstack
Contentstack packages automation, personalization, hosting, and enterprise support into one contract and never publishes a price. Drupal is the open-source platform many of those enterprises already run, with a security team, a large implementation-partner pool, and costs you can see. The comparison is about procurement as much as product.
When Drupal is the wrong answer
Being honest about this is the point of the series.
- One JavaScript application with a developer team on hand. Payload or Strapi. You do not need a PHP platform behind a Next.js app that one team owns end to end.
- A blog or a small marketing site. WordPress. The ecosystem, hosting, and talent are unbeatable at that scale.
- A marketing team that wants to compose pages visually today. Storyblok. Drupal Canvas is improving, but it is newer.
- A team that needs Google-Docs-style simultaneous editing. Sanity. Drupal has revisions and moderation, not live cursors.
- An enterprise that wants one vendor, one SLA, and no CMS staffing at all. Contentstack or Contentful Premium, if the budget exists.
When Drupal is the right answer
- The content model has many types with real relationships, and editors need to change it without a deploy.
- Every piece of content needs a revision trail and a moderation state, including translations.
- The organization runs many sites or brands from one platform and needs granular permissions.
- The catalog or the editorial team is large enough that per-entry or per-seat pricing becomes the biggest line item.
- Ownership and exit matter: the data has to live in a database you control, on infrastructure you can move.
The best of both worlds
Every "choose the SaaS" bullet above is about ergonomics: instant start, managed hosting, a visual editor, a typed SDK, no patch Tuesdays. None of them is about the content model. That is the gap decoupled.io is built to close.
Each decoupled.io space is a real Drupal instance running as its own Fly.io app, with JSON:API and GraphQL on every tier, an auto-generated TypeScript client, the Puck visual page builder, AI content generation, 25+ MCP tools for agents like Claude and Cursor, and automatic core and security updates. A free space provisions in under a minute. Pricing is flat: $0, $20 a month, or $60 a month, with no per-entry, per-seat, or per-API-call metering. See pricing.
It is still Drupal underneath, so you keep entity modeling, revisions, moderation, and translation in core, and you can export the database and leave whenever you want. It is also still a young platform. It does not match Sanity's real-time collaboration, Hygraph's federation, or Storyblok's editor maturity, and the module set is curated rather than open-ended. The individual comparisons say so.
FAQ
Is Drupal a headless CMS? Yes. JSON:API has been in Drupal core since 2019, so every content type is an API endpoint with no configuration, and GraphQL is available through the graphql_compose module. Drupal can also render pages itself, which the SaaS vendors cannot, so it is a headless CMS that is optionally coupled rather than the reverse.
Why is Drupal missing from most headless CMS comparisons? Because the comparisons are mostly written by SaaS vendors, and Drupal is not a SaaS product. It is open source with no sales team, so nobody has a budget line for putting it in a comparison table. The vendors that do mention it usually describe the Drupal of 2015, not Drupal CMS 2.x.
What does Drupal actually cost compared with a SaaS headless CMS? Drupal's license is free. You pay for hosting, which ranges from tens of dollars a month self-hosted to thousands on enterprise Drupal PaaS, and for maintenance time. A managed platform like decoupled.io is $20 to $60 a month flat. SaaS pricing starts free and climbs by seats, entries, locales, or API calls, which is cheap for small teams and expensive for large catalogs or editorial teams.
Can I migrate from a SaaS headless CMS to Drupal? Yes. Every vendor on this list exposes its content over an API, and Drupal's Migrate API imports from JSON sources. The work is remapping content types and rich text, not extracting data. We have written migration guides for Contentful, Sanity, Strapi, and WordPress.
Which of these is best for AI agents? The answer is changing quickly. Storyblok, Sanity, and Contentstack ship MCP servers, and Contentful has AI Actions on its Premium tier. decoupled.io exposes 25+ MCP tools on every tier, including free, which covers content CRUD, site provisioning, and content-type definition. If agents are going to write into your CMS, the deciding questions are whether the MCP surface is included in your plan and whether the content model has enough structure for an agent to write into safely.