Comparison
|
Jun 4, 2026
Contentful vs. Directus
Architecture, content modeling, admin UI, automation, AI, and pricing compared.
Matt Minor
Senior Director, Growth
Note from Directus
Yes, this is a Directus vs Contentful page written by Directus. Yes, we know that's absurd. Every vendor publishes one of these and ranks themselves first, so we have to publish ours or you won't find one that mentions us at all. So, if we have to play this game, we'd rather play it differently. What follows is the most honest comparison we could write.
Two backends, two operating models.
Contentful and Directus both give you structured-content APIs and an admin UI. They get there from opposite directions:
Contentful is a proprietary cloud SaaS: your content lives in their spaces, served through their global CDN.
Directus is a self-hosted (or managed) platform on top of any SQL database you bring or spin up.
Pick Contentful if you want a fully-managed SaaS, a global delivery CDN out of the box, and a page-composition product (Compose) aimed at large editorial teams.
Pick Directus if you want to own your data in a real SQL database, self-host (or use Directus Cloud), pay predictable infrastructure costs instead of API-call pricing, and get native dashboards, visual automation, AI Assistant, MCP server, and realtime APIs out of the box.
The feature-by-feature view.
A few rows do most of the work. Hosting model (self-host vs SaaS-only) is the architectural fork. Where data lives (your database vs. their cloud) is the data-sovereignty question. Native AI, MCP, Flows, Insights, and realtime are capabilities Directus ships natively. Compose and the built-in delivery CDN are real Contentful advantages. Pricing model is the part most teams underestimate at evaluation time.
Dimension | Directus | Contentful |
|---|---|---|
License | Source-available (custom Monospace license) | Proprietary (closed source) |
Hosting | Self-host (Docker, Node) or Directus Cloud | SaaS only, vendor cloud |
Schema Philosophy | Reads your existing SQL schema | Content types defined in Contentful |
Supported Databases | Postgres, MySQL, MariaDB, MSSQL, SQLite, Oracle, CockroachDB | N/A (no DB access) |
API Output | REST, GraphQL, WebSockets, GraphQL Subscriptions | REST (CDA / CMA), GraphQL |
Admin UI | The Studio (Vue 3) | Web App + Compose + Studio Editor |
Modeling Primitives | Collections, fields, relationships, M2A, translations | Content types, fields, references, locales |
Where Data Lives | Your SQL database | Contentful's spaces |
Page Composition | M2A, repeaters, custom layouts | Compose |
Native Realtime | WebSockets, GraphQL Subscriptions | No (webhooks only) |
Native AI Assistant | Yes, in the Studio | AI Actions (limited) |
Native MCP server | Yes | No |
Visual Automation | Flows | No (apps + webhooks) |
Native Dashboards | Insights | No |
Release management | Workflow + Flows | Launch |
Localization | Translations on any field, all tiers | Locales (gated by tier) |
Asset CDN | BYO (Cloudinary, S3+CDN, etc.) | Built-in global CDN (Fastly) |
Pricing Model | Per-environment / per-seat or self-hosted free | Per-space / per-user / API-call quotas |
The main architectural difference.
This is the one section worth reading carefully, because every other comparison on this page makes more sense after it.
If your top priority is "I never want to think about infrastructure, ops, scaling, or databases, just give me content APIs," Contentful is built for that. Directus Cloud reduces ops, but it's not zero-ops the way pure SaaS is.
If your top priority is "my data should live where I can query it directly, run analytics against it, share it with services that aren't a CMS, and not be locked into a vendor's content model," Directus is built for that. With Contentful, every read and write goes through their API. There's no database to run a SQL query against, no warehouse export that isn't an extra step, no way for a sibling service to share the same tables.
If you have hard data-residency, on-premise, air-gapped, or regulatory constraints (GovCloud, healthcare, financial services, EU sovereignty rules), self-hosting may not be optional. Contentful is SaaS-only, so it's a non-starter in those scenarios. Directus self-hosts in any environment you control.
Neither approach is wrong. They're built for different relationships to your content and your infrastructure.
The two admin UIs, side by side.
Both shipped polished interfaces. Different shapes, different jobs.
Directus Studio
Contentful admin
Proprietary vs. source-available.
Contentful is proprietary, closed-source software. You don't read its source, fork it, or run it. You consume the SaaS. That's the deal.
Directus is distributed under a source-available license. (The license is currently moving from the Business Source License to a custom Monospace license. See directus.com/license for the live terms.) The source code is fully readable and modifiable, and free to self-host for the vast majority of use cases.
Practically: you can read Directus's source, you cannot read Contentful's. You can self-host Directus (including air-gapped, on-prem, or in your own VPC); you cannot self-host Contentful. You can fork Directus if you need to. You can run Directus indefinitely without paying anyone. Contentful requires an active subscription past the free tier.
What users say.
Here's a sample of public reviews from both the Contentful and Directus G2.
Content modeling.
Both tools model structured content well. The shape of the primitives differs.
Content types in Contentful are reusable schemas (Page, Article, Author) defined once with their fields and validation. References link entries together.
Collections in Directus are real database tables. Fields are columns. Relationships are foreign keys. Many-to-Any (M2A) lets a single field reference items from any number of unrelated collections, useful for flexible page composition, polymorphic relationships, and arbitrary cross-collection joins. Because the model is the database, the same data is trivially queryable by any system that speaks SQL (analytics jobs, BI tools, ML pipelines, sibling services) without going through the CMS API.
Page composition. Contentful ships Compose, a dedicated page-composition product where editors stack reusable section types to build pages visually. Directus uses M2A relationships and repeating field templates to express the same patterns. The Directus approach is more general (M2A composes across any collections, not just designated section types).
Localization. Both support multi-language content. Contentful handles locales as a first-class concept, but locale availability is gated by pricing tier. Directus stores translations as related rows that can hang off any field, available on every tier.
The admin experience.
Directus ships the Studio, built in Vue 3 and framed as a workspace, not as a content-publishing tool. The same UI that lets a content editor edit a blog post lets an operations person build a dashboard, configure a workflow, manage permissions, query data with the AI Assistant, or run an analytics view.
Contentful ships its Web App plus Compose for page-builder workflows and the newer Studio Editor for visual content editing. Their UI is shaped primarily around editorial work: content authoring, scheduled publishing, multi-locale workflows, and collaboration between writers, editors, and reviewers.
Automation and workflows.
Directus has Flows, a visual automation builder. Drag together triggers, conditions, and operations to build pipelines that run on data changes, schedules, or webhooks. Non-developers can build moderately complex automations. Developers can drop into custom JavaScript at any step.
Contentful does not ship a visual automation builder. Automation comes from three places: webhooks (fire on content events to your own service), Apps (extensions installed from the Marketplace or built with the App Framework), and editorial workflow features at the Premium tier (review states, approval gates, role-based steps).
Realtime and delivery.
Two delivery-shaped capabilities that move evaluations differently.
Realtime APIs. Directus ships native WebSockets and GraphQL Subscriptions in the core. You can subscribe to changes on any collection and push live updates to clients without adding extra infrastructure. Contentful does not ship native realtime APIs. You'd use webhooks to fire events and a separate layer to push to clients.
Asset and content CDN. Contentful ships a global delivery CDN out of the box, served through Fastly's edge network, with image transformations on read, automatic format negotiation, and edge caching tuned for content delivery at scale. With Directus, you bring your own (CloudFront, Cloudflare, Fastly, etc.) and your own asset CDN (S3+CloudFront, Cloudinary, Bunny). Directus does ship asset transformations and signed URLs natively.
AI.
Directus ships with a native AI Assistant inside the Studio. It's conversational and takes action. It can create content, translate fields, summarize records, route items for review, and operate against your data with the same access policies as a human user. It's not a separate "AI mode," it's part of the same workspace.
Directus also runs a native MCP server. External AI tools (Claude Desktop, Cursor, ChatGPT, your own agent) can connect and work with the same data using the same access policies. AI is treated as another API consumer.
Contentful has been adding AI features (AI Actions, content suggestions, asset alt-text generation, generative image tools), most surfaced inside the Web App. There's no native MCP server. The capabilities are useful for editorial teams looking to speed up authoring, but they're scoped to authoring assistance rather than general "AI agents that take action under your existing permissions across the whole data layer."
Developer experience.
Both tools get you to a working backend in minutes if you have Docker running.
Both have CLIs. Both have TypeScript SDKs. Contentful has SDKs in more non-JS languages (Ruby, Python, Java, Swift, .NET, PHP) because it's been around longer in a wider ecosystem.
Contentful's documentation covers a wide range of use cases and has been built up over more than a decade. Their developer ecosystem (community plugins, integration guides, public-content examples) has had more time to grow than most tools in the space.
Directus has tighter, more concentrated docs around the Studio, the SDK, and the extensions framework. Quality of in-house support is high. Volume of community-generated content is lower than Contentful's, but it's growing.
What it actually costs.
Self-hosting (Directus only): Free. You bring infrastructure, do operations, take on backups and upgrades. Contentful has no self-host option at any tier.
Managed cloud: Directus Cloud has starter, team, and growth-style tiers running from low double-digits to a few hundred dollars per month. Contentful's paid tiers historically jumped from free to a higher commercial tier, with real costs landing well above list price once you account for additional users, locales, environments, and overage on API calls.
Enterprise: Both have enterprise tiers with SSO, audit logs, dedicated support, and SLAs. Both will quote you. Contentful's enterprise tier is one of the most expensive in the headless CMS space.
Neither is perfect.
We promised this and we'll keep our word.
Three areas where Directus is weaker | Three areas where Contentful is weaker |
|---|---|
No fully-zero-ops SaaS. Directus Cloud reduces ops; Contentful is true SaaS where you never think about infrastructure. | No real database access. Your data lives in their cloud as content entries, queryable only through their APIs. No SQL, no warehouse-native joins, no analytics jobs. |
No dedicated page-composition product equivalent to Compose. M2A relationships cover the same ground, but a marketing team using Compose is using a more opinionated tool for that specific use case. | Closed-source. You can't read it, fork it, or run it. Vendor lock-in is structural. |
No dedicated release-management product equivalent to Launch (scheduled publishes, content releases, multi-environment promotion). Directus handles this through Flows and roles. | Migration off Contentful is significant work. Your data is in their content model, accessed only through their API. |
Who each is (usually) best for.
Contentful is usually best for | Directus is usually best for |
|---|---|
Large editorial teams whose primary daily work is content authoring with multi-step review, scheduled publishing, and translation workflows | Teams who want their content data in a SQL database they own, queryable by any service that speaks SQL |
Marketing organizations that want a polished page-composition product (Compose) and a release-management product (Launch) out of the box | Teams with hard requirements around self-hosting, on-premise, air-gapped, EU data sovereignty, or regulated-industry compliance |
Teams who explicitly want zero-ops SaaS with a global CDN baked in | Teams where content, operations, analytics, and AI agents all need to work on the same governed data layer |
Teams already standardized on Contentful's ecosystem of pre-built apps (Cloudinary, Algolia, Optimizely, Bynder) | Teams where non-developers own real workflows: dashboards (Insights), visual automations (Flows), AI-assisted operations |
Projects where global content delivery latency is a top requirement and you don't already operate a CDN strategy | Projects that need realtime: WebSockets, GraphQL Subscriptions, live-updating clients |
Teams whose primary integration is "front-end developers consume the Content Delivery API," not "shared data layer across services" | Projects where AI Assistant or native MCP server are part of the plan, not a "we'll plug something in later" item |
Teams who want their schema to remain a first-class artifact in their database, not a content model trapped behind a vendor API |
Migration notes.
From Directus
Doable, common, well-trodden. Standard path: export your Contentful spaces using their CLI, transform the JSON into a relational schema (content types become collections, references become foreign keys, locales become translation rows), import into your SQL database. Compose pages map to M2A relationships. Custom apps don't transfer; rebuild as Directus extensions. Webhooks reattach to Flow triggers. The translation step deserves engineering attention.
From Contentful
Way harder. Contentful's content model is more opinionated than a SQL schema, and any database features you've used (custom Postgres types, advanced indexes, M2A, multi-database joins, materialized views, raw SQL access) don't exist in Contentful. You'd remodel as Contentful content types and migrate data through the Management API. Anything outside their content-type model (analytics queries, sibling services, scheduled jobs) needs to live somewhere else.
In both directions, custom code (extensions, apps, hooks, webhooks, Flows) doesn't transfer. Reimplement in the target tool's extension model.
Common questions.
Is Contentful better than Directus?
Neither is better in a general sense. They're built for different relationships to data and infrastructure. Contentful is a SaaS platform built for editorial teams who want zero ops. Directus is a database-first backend for teams that want to own their data and serve it across multiple services. The right choice depends on which of those describes your situation.
What changed after Salesforce acquired Contentful?
Salesforce acquired Contentful in 2026. The immediate product impact is unclear. Historically, acquisitions by large enterprise vendors correlate with pricing increases, enterprise feature focus, and slower movement on developer-facing tooling. Teams concerned about roadmap direction are right to evaluate alternatives before they need to.
Can Contentful be self-hosted?
No. Contentful is SaaS-only at every tier. Your content lives in their infrastructure and is accessible only through their APIs. There is no option to run Contentful on your own servers, in your own VPC, or in an air-gapped environment. If self-hosting or data residency is a requirement, Contentful is a non-starter.
Is Directus open source?
Directus is source-available under a custom Monospace license. The source code is public and the self-hosted version is free to use, but it does not use an OSI-approved license. If your organization requires OSI-approved open source, Strapi and Payload are the MIT-licensed alternatives in this category.
How much does Contentful cost compared to Directus?
Directus is free to self-host. Cloud starts at $15/month. Contentful's free tier is limited on users, content types, locales, and API calls. Paid tiers start around $300/month and scale with API usage — a line item that grows with traffic, not with users. Teams routinely underestimate Contentful's cost at scale. Model the total bill at your one-year traffic and content volume before committing. Verify current pricing at contentful.com/pricing.
Can I migrate from Contentful to Directus?
Yes. Export your Contentful spaces using their CLI (they export as JSON). Transform the JSON into a relational schema — content types become collections, references become foreign keys, locales become translation rows — and import into your SQL database. The main work is the schema transformation. Compose pages map to M2A relationships. Custom Contentful apps need to be rebuilt as Directus extensions. The migration is achievable; it is not a one-click process.
Does Directus have an MCP server?
Yes. Directus ships a native MCP server. External AI tools (Claude Desktop, Cursor, ChatGPT, custom agents) can connect and work with your content through the same role-based permissions as human users. Contentful does not ship a native MCP server. This is the relevant capability gap if AI agents that take action on your content are part of your roadmap.
Which has better developer experience?
Depends on the developer and what you mean by DX. Contentful has SDKs in more languages (Ruby, Python, Java, Swift, .NET, PHP) and a larger community of third-party content and tutorials. Directus is Node.js and TypeScript throughout, ships more native capabilities (Flows, Insights, AI Assistant, realtime APIs, MCP server), and has broader database support. Contentful's DX is wider; Directus's is denser per capability.
