Directus for publishers: SQL-first headless CMS, source-available

What is Directus?

Directus is a data platform that connects to a SQL database and gives it a web studio and APIs. The documentation says it connects to your database, asset storage and external services, and provides REST and GraphQL APIs, an SDK, authentication, file management, automations and a management app. Used as a CMS, it is headless: it holds articles and media, and a separate site renders them.

The repository’s licence file carries the line “Copyright 2026 Monospace Inc.” and the latest GitHub release is v12.5.0, published 7 October 2026. The licence is the main thing a publisher must understand, so it gets its own section below. For the model in general, read the headless guide.

Who is Directus best for?

Directus suits a publisher whose developers already manage SQL databases and want an admin studio and APIs on top without moving data into a vendor’s store. It is a good fit when you inherit an existing database, or need several data-driven tools beside the editorial site.

It does not suit teams that require a conventional open-source licence, and it is a poor fit for newsrooms without developers, because nothing in it renders a public site.

What does the Directus licence allow?

The repository states that Directus is licensed under the Monospace Sustainable Core License 1.0, a source-available licence derived from the Fair Core License. Our licence guide explains the wider categories. The file we read defines a Permitted Purpose as any purpose other than a Competing Use. A Competing Use means making the software available to a party that competes with the licensor’s commercial offerings of the software itself, where the licensor charges a fee. Permitted purposes listed include internal use, non-commercial education and research, and professional services to licensees.

For a publisher running Directus behind its own site, that reads as ordinary internal use, but it is not legal advice and the wording matters. The licence also grants an additional GPL-3.0 licence on the fourth anniversary of the date the software is made available, so older versions become GPL later.

The commercial side is described separately. According to the licensing documentation, a self-hosted instance without a licence runs on the free core tier, higher limits and extra features need a commercial licence, and organisations under $5M in annual revenue with fewer than 50 employees can use the Open Innovation Grant for free commercial use. Seats count active Studio users, meaning those with App Access or Admin Access; API-only users do not count.

Editorial workflow

Access control uses roles and policies. A role can carry any number of policies, and policies group permissions over collections and actions, with item-level filters, field restrictions, validation rules and presets. That allows detailed rules, such as authors who see only their own articles, but your team has to configure them. The pricing page lists granular RBAC on Team, and SSO is not available on Core.

Content versioning is enabled per collection. Once on, the published view is read-only, editors work in a reserved Draft version, and Publish shows a comparison of changes before finalising. Revisions track individual changes. Editors need permissions on the directus_versions and directus_revisions collections, or they will not see the feature.

The documents we read do not describe staged review workflows or scheduled publishing as built-in editorial features, and we could not verify the automation (Flows) documentation, so we make no claim about either. Check both before committing if scheduling matters to you.

What the front end must handle: preview. Live Preview needs more than a setting. You configure a Preview URL for each collection, set a CSP frame-src variable on Directus, and send a Content-Security-Policy: frame-ancestors header from your site so it may be framed. The front end must render the item page when it is requested, not only at build time, and can read a version query parameter to fetch versioned content. Static-only sites need a dynamic preview route.

SEO, structured data and feeds

Directus is a data layer, and the pages we read describe no built-in SEO module, sitemap generator, structured-data output or redirect manager. These are front-end responsibilities:

• Sitemaps: generate XML from published items, with accurate modified dates.
• Structured data: produce Article or NewsArticle JSON-LD from fields you add, such as author, dates and image.
• Redirects: store them in a collection if you wish, then apply them at the server, CDN or framework level with the right status code.
• Titles, meta descriptions and canonicals: create fields on your collections and render them.
• Hreflang: derive from your translation setup.
• Feeds: RSS or Atom, built by the front end.
• Draft isolation: ensure preview routes are authenticated and not indexable.

Media, multilingual and performance

Files go through a storage adapter, either local filesystem or a compatible cloud provider, and editors upload by drag and drop, file picker or URL import in the studio. We did not verify an image transformation feature, so we do not describe one; plan image sizing in your front end or CDN.

Content translations use a translations field. Directus can auto-generate a languages collection, pre-populated with common languages, and a junction collection for translated fields, or you can set it up manually. There is an AI translation button, and the studio renders right-to-left languages. For performance, the requirements page recommends Redis for caching, required for horizontal scaling, plus a CDN, load balancing and monitoring.

Hosting and requirements

Directus is distributed as a Docker image. The requirements page gives minimum compute of 1x 0.25 vCPU with 512 MB, and a recommended minimum of 2x 1 vCPU with 2GB. It supports the LTS versions of PostgreSQL, MySQL, SQLite, MS SQL Server, MariaDB, CockroachDB and OracleDB. The self-hosting documentation says you need experience with Docker, server maintenance, databases and backups, and that Directus Cloud is the managed alternative.

Extending Directus

The overview lists an SDK, real-time capabilities, automations and REST and GraphQL APIs. The release notes mention an SDK package and flow management in the app. We did not verify the extension ecosystem in detail, so we do not describe its size.

What Directus costs

Self-hosting without a licence is free on the core tier. The pricing page lists Core at $0 per month with 3 user seats, 25 collections and 5 flows, Team at $499 per month billed annually or $599 monthly, and Enterprise at custom pricing. It also describes the Open Innovation Grant for qualifying organisations. The page does not name the currency beside the figures, so confirm it.

On top of any licence, budget for hosting, a database, Redis, backups and front-end development. See the cost guide.

Where Directus falls short

• Not open source. The licence is source-available with a competing-use restriction, which matters for agencies and resellers.
• Seat and collection limits. Core lists 3 seats, 25 collections and 5 flows, and SSO is not on Core.
• No front end or SEO layer. Everything public-facing is built separately.
• Preview needs care. Framing headers, dynamic rendering and version parameters must all be right.
• Operational load. Self-hosting needs Docker, database and Redis skills.
• Unverified features. We found no documentation of built-in scheduled publishing or review stages.

The verdict for publishers

Directus is a sensible choice for a publisher with SQL skills that wants an admin studio and APIs over a database it controls, and is comfortable with a source-available licence. Versioning, roles and policies, translations and the self-hosting documentation are clear.

It is a weaker fit if your policy requires an OSI-style open-source licence, or if you need staged editorial approval and scheduling confirmed out of the box. Compare it with other headless systems and self-hosted options on the comparison hub. This profile is based on vendor documentation and the licence file; see how we test.