Directus at a glance
- Type
- Headless CMS and data platform
- Built with
- Node.js, on top of a SQL database
- Hosting
- Self-hosted, or Directus Cloud
- Best for
- Teams that want their own database behind the content
How Directus works
Directus reads and writes your own database: each table is a collection, each column a field, and relations link items across collections. Files live in its file library, and translations, roles and flows are configured in the admin app rather than in code.
What Directus does well
Your database, your schema
Content stays in plain SQL tables, readable without Directus.
REST and GraphQL
Both APIs come with every collection, with no extra setup.
Admin app for editors
Editors get forms, file library, workflows and roles.
Self-host or cloud
Run it anywhere Node.js runs, or on Directus Cloud.
Who uses Directus
Developers and agencies use Directus for websites, apps and internal tools where the data should stay in an ordinary database they control. It suits projects that start from an existing database as well as new ones.
What to weigh before you move
No CMS fits every team. These are the points that come up most when people plan to leave Directus, or to make it their next home.
- No front endLike any headless CMS, the website is built separately.
- Schema decisions are yoursThe content model is a database design, so it needs planning up front.
- Licence by sizeCheck Directus's licence terms for larger organisations before you commit.
What a Directus migration covers
When the connector is ready, Reloque will scan your Directus content first and map each field before anything moves. These are the kinds of content a migration has to account for.
- Collections and items
- Fields
- Relations
- Files
- Translations
- Users
Planning a move from Directus
A Directus move centres on the collections and their relations, since they are the content model.
- List the collections, their fields and the relations between them
- Note translations and how they are stored
- Check files in the file library and where items use them
- Decide how the front end will read the new content and its addresses
Where Directus content could go
The Directus connector is planned, and connectors are built in the order people ask for them. These ten work today, in every direction, and Directus will join them both ways.
Moving to Directus
Moving to Directus means designing collections for each content type, with relations for links between them, then filling them through its API.
Directus questions
What is Directus?
Directus is a headless CMS that sits on top of a SQL database. It turns the database's tables into collections with an admin app for editors and REST and GraphQL APIs for developers.
Who uses Directus?
Developers and agencies use Directus for websites, apps and internal tools where the data should stay in an ordinary database they control. It suits projects that start from an existing database as well as new ones.
What content can be migrated to or from Directus?
A migration with Directus typically covers collections and their items, fields, relations, files, translations and users. Reloque scans your site first and shows what it found before anything moves.
What should I prepare before a Directus migration?
A Directus move centres on the collections and their relations, since they are the content model. Four checks help most: (1) list the collections, their fields and the relations between them; (2) note translations and how they are stored; (3) check files in the file library and where items use them; (4) decide how the front end will read the new content and its addresses.
Can Reloque migrate Directus today?
Not yet. The Directus connector is planned, in both directions with every CMS Reloque supports. Reloque moves WordPress, Payload, Strapi, Ghost, Umbraco, Drupal, Contentful, Sanity, Storyblok and Webflow today. Tell us your route when you start a free assessment.