Directus vs TYPO3
Directus is a closed-source headless CMS that you can host yourself or run on the vendor's cloud. TYPO3 is an open-source traditional CMS that you host yourself. The table below sets them side by side on 28 features. They get a different status on 17.
- Directus Headless · Closed source · 18 of 28 built in
- TYPO3 Traditional · Open source · 20 of 28 built in
Sources checked: Directus on 29 Sept 2026, TYPO3 on 29 Sept 2026. Plans and releases can change after those dates.
WAYF is an official Payload partner and top contributor. Every platform in the table is classified by the same published definitions, and each answer lists the vendor page it came from.
Feature comparison
| Platform | | |
|---|---|---|
| Overview | ||
| What it is | Source-available data platform and headless CMS that puts a Studio admin app and REST and GraphQL APIs over your own SQL database. | Open-source PHP CMS for multi-site, multilingual websites, with workspaces and granular backend permissions. Self-hosted, often run by agencies. |
| Edition compared The product and release each column describes. | Directus 12, self-hosted core tier or licensed plans, with optional Directus Cloud Version 12.4.1, released 23 Sept 2026 | TYPO3 v14 LTS, version 14.3, open source Version 14.3.7, released 8 Sept 2026 |
| Vendor | Monospace Inc. directus.com | TYPO3 Association (project); TYPO3 GmbH sells support and extended LTS typo3.org |
| Licence | Closed source MSCL-1.0-GPL, source-available, GPL-3.0 after four years. Free under $5M revenue and 50 staff via the Open Innovation Grant | Open source GPL-2.0-or-later |
| Hosting | Self-hosting Vendor cloud Directus Cloud is a $99 per month add-on for Core and Team. Enterprise cloud on request. | Self-hosting No vendor cloud No vendor SaaS. TYPO3 agencies and hosts run managed installations. |
| Built with | TypeScript, Node.js, Vue | PHP, Symfony components, Fluid |
| Database | PostgreSQL, MySQL, MariaDB, SQLite, MS SQL Server, Oracle, CockroachDB | MySQL, MariaDB, PostgreSQL, SQLite |
| Pricing Public list prices only. Hosting and implementation are extra everywhere. | Free to start Core free for 3 seats and 25 collections. Team $499 per month billed yearly or $599 monthly. Enterprise on request. | Free to start Free and open source. Commercial support and extended LTS are sold separately. |
| Content modelling | ||
| Content model in code You define content types in files in your repository, review them like any other code and apply them from there. Imperative migration scripts alone count as limited. | Built in Schema snapshots are files in the repo, applied to an instance with the CLI. 16 | Built in TCA in PHP. The Content Blocks extension adds YAML definitions. 11 |
| Content model in the UI Admins can create and change content types and fields in the admin interface without writing code. | Built in | Plugin or add-on Mask extension builds content elements in the backend. 12 |
| Reusable blocks Editors compose pages from reusable, typed components or blocks, and can reorder them. | Built in Page builders use many-to-any relations. 17 | Built in Content elements on pages, reordered by drag and drop. |
| Localization Editors translate content per locale inside the CMS, by field or by entry, without a separate site for each language. | Built in Translations field with related translation records. | Built in Page and record translations. Guided translation wizard in v14. 2 |
| Image transformations The CMS resizes, crops or converts images on request, through URL parameters or generated sizes, with no external service. | Built in URL parameters and saved presets. 13 | Built in Server-side image processing with crop variants. 10 |
| APIs and delivery | ||
| REST API A documented REST or JSON HTTP API returns content. | Built in | Plugin or add-on EXT:headless outputs pages as JSON. Core has no content API. 13 |
| GraphQL API The vendor or an official module provides a GraphQL API for content. | Built in | Not available |
| Webhooks The CMS can call an external URL when content is created, changed or published. | Built in Through Flows. Core allows 5 Flows. 219 | Built in Webhooks system extension, in core since v12. 6 |
| Renders the website The CMS itself renders and serves the public pages through themes or templates. Headless-only products answer no. | Not available | Built in Fluid templates. Camino default theme in v14. 2 |
| Editorial workflow | ||
| Drafts Editors save changes as a draft and publish them later. The live version stays untouched until then. | Built in Content versioning with a draft per item. 6 | Built in Via the Workspaces system extension. 5 |
| Scheduled publishing An editor can set a future date and time for content to publish or unpublish. | Limited No schedule field. An official guide publishes future items with a scheduled Flow. 14 | Built in Start and stop dates on pages and content. |
| Version history The CMS keeps earlier versions of an entry, and editors can compare or restore them. | Limited Revisions kept 30 days on Core, 90 on Team, configurable on Enterprise. 2 | Built in Record history with diff and undo. |
| Preview Editors can see unpublished content rendered as it will appear on the site before publishing. | Built in | Built in Workspace preview links. 5 |
| Visual editing Editors can click on the rendered page and edit content in place or in a side panel next to it. | Built in Visual Editor module. The site adds the Directus frontend library. 7 | Plugin or add-on Visual Editor extension from Friends of TYPO3. TYPO3 plans core support for v15. 3 |
| Approval workflows Content moves through review stages you configure, such as draft, review and approved, with permissions per stage. | Limited Built from a status field and custom permissions, which need Team, Enterprise or the grant. 152 | Built in Custom stages in Workspaces. 5 |
| Content releases Editors group changes across several entries and publish them together as one release. | Not available | Built in Workspaces publish staged changes together. 5 |
| Real-time co-editing Two or more editors can work on the same entry at once and see each other's changes live. | Built in Collaborative Editing with field locking. 8 | Not available |
| Access and governance | ||
| Custom roles Admins define their own roles with granular permissions instead of picking from a fixed set. | Built in Unlimited roles on Core. Custom access policies need Team, Enterprise or the grant. 220 | Built in Backend user groups. 9 |
| Field-level permissions Admins can restrict access to single fields, on top of content types and entries. | Paid tier Custom permissions for fields and item rules need Team, Enterprise or the grant. 25 | Built in Exclude fields per backend group. 9 |
| Single sign-on Editors can sign in through SAML or OpenID Connect against a company identity provider. | Paid tier Team plan and up, or the grant. SAML, OpenID, OAuth 2.0 and LDAP. 211 | Plugin or add-on OpenID Connect extensions such as causal/oidc. 14 |
| Audit log The CMS logs who changed what and when across the whole installation, and admins can review the log. | Limited Activity log kept 30 days on Core, 90 on Team, configurable on Enterprise. 212 | Built in Log module records backend changes by user. |
| Platform and extensibility | ||
| Multiple sites One installation or account can manage several separate websites or brands with shared users. | Not available | Built in Several site configurations in one installation. |
| Extensible admin UI Developers can add their own components, views or fields to the editing interface. | Built in Extensions add interfaces, layouts, panels and modules. | Built in Backend modules and custom form elements. |
| Plugin marketplace The vendor runs an official directory or marketplace of installable extensions. | Built in Marketplace inside the Studio. 18 | Built in TYPO3 Extension Repository. 16 |
| Form builder Editors can build and publish forms and collect submissions without code. | Not available | Built in Form Framework with a backend form editor. 7 |
| Site member accounts The platform handles sign-up and login for public site users or members, separate from editors. | Built in API-only application users do not use Studio seats. 3 | Built in Frontend users and the felogin extension. 8 |
| AI writing assistant A first-party AI feature in the editing interface generates, rewrites or translates content. | Built in AI Assistant on every plan with your own OpenAI, Anthropic or Gemini key. 29 | Not available Core ships AI integration points only. Third-party extensions such as AI Suite. 417 |
| Official MCP server The vendor publishes a Model Context Protocol server so AI agents can read or write content. | Built in Built in since 11.12. 10 | Not available Third-party only, e.g. hauptsache.net's TYPO3 MCP Server. 15 |
Directus sources
Checked 29 Sept 2026. Directus 12, self-hosted core tier or licensed plans, with optional Directus Cloud.
- directus on the npm registry
- Directus pricing
- Directus docs: Licensing overview
- Monospace Sustainable Core License
- Directus docs: Access control
- Directus docs: Content versioning
- Directus docs: Visual Editor
- Directus docs: Collaborative Editing
- Directus docs: AI Assistant
- Directus docs: Directus MCP
- Directus docs: Single Sign-On
- Directus docs: Accountability
- Directus docs: Transform files
- Directus tutorial: Schedule future content with Flows
- Directus tutorial: Content approval workflows with custom permissions
- Directus tutorial: Promoting changes between environments
- Directus tutorial: Reusable blocks with many-to-any relationships
- Directus docs: Marketplace
- Directus docs: Send Directus webhooks to Clay with Flows
- Directus license, MSCL and v12 questions (Contensu)
TYPO3 sources
Checked 29 Sept 2026. TYPO3 v14 LTS, version 14.3, open source.
- get.typo3.org: latest TYPO3 14 release
- TYPO3 Releases v14 LTS (press release)
- Changing the Playing Field: Visual Editing in TYPO3 v14
- TYPO3 v14: Building a System for Community-Driven AI Integrations
- TYPO3 Workspaces documentation
- TYPO3 Webhooks documentation
- TYPO3 Form documentation
- TYPO3 Frontend Login documentation
- Access control options (TYPO3 Explained)
- Crop variants for images (TYPO3 Explained)
- TYPO3 Content Blocks documentation
- Mask extension (TER)
- EXT:headless documentation
- OpenID Connect integration for TYPO3
- hauptsacheNet/typo3-mcp-server on GitHub
- How to find extensions (Getting Started)
- AI Suite extension (TER)
Considering more platforms? Compare Directus and TYPO3 with the rest of your shortlist in the CMS comparison tool.
Where they differ
Directus and TYPO3 get a different status on 17 of the 28 features and the same status on 11. Directus has 18 built in on its baseline edition, TYPO3 has 20. Two matching statuses can still name different paid tiers or limits, so read the notes in the table before treating a row as equal.
- Licence
- Directus is closed source (MSCL-1.0-GPL, source-available, GPL-3.0 after four years. Free under $5M revenue and 50 staff via the Open Innovation Grant). TYPO3 is open source (GPL-2.0-or-later).
- Vendor cloud
- Directus has a vendor-run cloud. TYPO3 has no vendor-run cloud.
Built in on Directus, a different answer on TYPO3 7
- Content model in the UI Directus: Built in. TYPO3: Plugin or add-on.
- REST API Directus: Built in. TYPO3: Plugin or add-on.
- GraphQL API Directus: Built in. TYPO3: Not available.
- Visual editing Directus: Built in. TYPO3: Plugin or add-on.
- Real-time co-editing Directus: Built in. TYPO3: Not available.
- AI writing assistant Directus: Built in. TYPO3: Not available.
- Official MCP server Directus: Built in. TYPO3: Not available.
Built in on TYPO3, a different answer on Directus 9
- Renders the website Directus: Not available. TYPO3: Built in.
- Scheduled publishing Directus: Limited. TYPO3: Built in.
- Version history Directus: Limited. TYPO3: Built in.
- Approval workflows Directus: Limited. TYPO3: Built in.
- Content releases Directus: Not available. TYPO3: Built in.
- Field-level permissions Directus: Paid tier. TYPO3: Built in.
- Audit log Directus: Limited. TYPO3: Built in.
- Multiple sites Directus: Not available. TYPO3: Built in.
- Form builder Directus: Not available. TYPO3: Built in.
Built in on neither, with different answers 1
- Single sign-on Directus: Paid tier. TYPO3: Plugin or add-on.
More comparisons
Full write-ups with worked examples and costs: Directus vs Payload.
Directus against other platforms
- Adobe Experience Manager vs Directus
- Contentful vs Directus
- Contentstack vs Directus
- CoreMedia Content Cloud vs Directus
- Craft CMS vs Directus
- DatoCMS vs Directus
- Decap CMS vs Directus
- Directus vs Drupal
- Directus vs EmDash
- Directus vs FirstSpirit
- Directus vs Framer
- Directus vs Ghost
- Directus vs HubSpot CMS
- Directus vs Hygraph
- Directus vs Instatic
- Directus vs Joomla
- Directus vs Keystone
- Directus vs Kirby
- Directus vs Liferay DXP
- Directus vs Optimizely CMS
- Directus vs Payload
- Directus vs Prismic
- Directus vs Progress Sitefinity
- Directus vs Sanity
- Directus vs Sitecore
- Directus vs Squarespace
- Directus vs Statamic
- Directus vs Storyblok
- Directus vs Strapi
- Directus vs Umbraco
- Directus vs Wagtail
- Directus vs Webflow
- Directus vs Wix
- Directus vs WordPress
- Directus vs Xperience by Kentico
TYPO3 against other platforms
- Adobe Experience Manager vs TYPO3
- Contentful vs TYPO3
- Contentstack vs TYPO3
- CoreMedia Content Cloud vs TYPO3
- Craft CMS vs TYPO3
- DatoCMS vs TYPO3
- Decap CMS vs TYPO3
- Drupal vs TYPO3
- EmDash vs TYPO3
- FirstSpirit vs TYPO3
- Framer vs TYPO3
- Ghost vs TYPO3
- HubSpot CMS vs TYPO3
- Hygraph vs TYPO3
- Instatic vs TYPO3
- Joomla vs TYPO3
- Keystone vs TYPO3
- Kirby vs TYPO3
- Liferay DXP vs TYPO3
- Optimizely CMS vs TYPO3
- TYPO3 vs Payload
- Prismic vs TYPO3
- Progress Sitefinity vs TYPO3
- Sanity vs TYPO3
- Sitecore vs TYPO3
- Squarespace vs TYPO3
- Statamic vs TYPO3
- Storyblok vs TYPO3
- Strapi vs TYPO3
- TYPO3 vs Umbraco
- TYPO3 vs Wagtail
- TYPO3 vs Webflow
- TYPO3 vs Wix
- TYPO3 vs WordPress
- Xperience by Kentico vs TYPO3
Open the CMS comparison tool to put up to six platforms in one table.
We're booking content platform
engagements for 2026.
Twenty-five minutes to walk through the work and decide if we're the right team for it. Scoping and a fixed price come after.