What is Directus, and what changed by October 2026?
Directus is a Node.js application that sits on top of a SQL database and turns it into a content backend. You point it at PostgreSQL, MySQL, SQLite, MS SQL or Oracle, and it generates a REST API, a GraphQL API and an admin app (the Data Studio) from the tables it finds. If the database already exists, Directus wraps it without asking you to migrate the data into a proprietary store.
The licence deserves a careful read. Directus is source available rather than plain open source. Its license page describes the Monospace Sustainable Core License 1.0, which restricts “competing use” and converts to GPL-3.0 on the fourth anniversary of each release. Its pricing page also describes an Open Innovation Grant: free self-hosting for organisations under $5M in annual revenue and fewer than 50 employees, with paid Cloud and Enterprise plans for everyone else. Check both pages with your legal team before you commit, because the terms decide whether self-hosting is free for you. Prices change often, so we quote none here.
Who is Directus a good fit for?
Directus suits teams whose data model is bigger than “pages and posts”. Typical cases are a catalogue with thousands of records, a partner portal, an internal tool that needs role-based access, or a product that shares a database with a legacy system. Editors get a clean Data Studio and developers keep SQL they can inspect. Flows handle automation, such as sending a webhook when an item is published.
It fits less well when the main need is a marketing site with a page builder. Directus has no visual page assembly out of the box, so editors work with structured fields only. For that case we usually look at Storyblok or Builder.io instead. If you want a code-first CMS that lives inside your Next.js repository, Payload is the closer match. For a head-to-head on the closest open competitor, read Strapi vs Directus.
What do we build with Directus?
Content model and permissions
We design collections, relations and translation tables in the Data Studio, then export the schema so it can be versioned and applied across environments. Access policies come next: which roles can read drafts, edit one region’s content, or only see their own records.
Frontend and preview
The usual pair is Directus with Next.js or Astro. Static pages rebuild on a webhook from a Flow, and draft preview runs through a token that the frontend uses to request unpublished items. We keep image transforms on the Directus assets endpoint, so the frontend asks for sizes instead of storing copies.
Extensions and integrations
When the built-in features stop short, we write extensions: custom endpoints, hooks that validate data before it is saved, and interfaces that give editors a purpose-built field. Typical integrations are search indexing, an identity provider through SSO, and a storage adapter for S3-compatible buckets.
Migration into Directus
Because Directus reads an existing schema, a migration can be gentler than with other platforms. We clean the tables, add the fields Directus needs for content workflow, and write scripts that move the rest. Redirects and metadata are checked against the CMS migration checklist before the switch.
Directus questions worth settling early
| Question | Why it matters |
|---|---|
| Self-hosted or Directus Cloud? | Self-hosting means you run upgrades, backups and scaling. Cloud moves that to the vendor and changes the cost line. |
| Does the grant apply to you? | The revenue and headcount thresholds decide if the software itself is free. |
| Who owns the schema? | If another system also writes to the database, agree on rules before editors start. |
| How many locales? | Translation tables multiply the number of items editors maintain. |
Our Directus developers can join your team or run the build end to end. If you are still choosing a platform, start from the headless CMS overview or the list of free headless CMS platforms, which covers licence terms side by side.
