Directus

What Directus actually is

Directus sits in a peculiar spot: it is listed in our database hosting category, but it is not a database and not really a CMS in the WordPress sense. It is a data platform that wraps any SQL database — PostgreSQL, MySQL, SQLite, and others — with a visual admin app (the Studio), auto-generated REST and GraphQL APIs, real-time subscriptions over WebSockets, file management, and role-based access control. You point it at an existing schema and get an API and a back-office without writing endpoint code.

The project has history behind it: founder Ben Haynes started building Directus in 2004, it was open sourced in 2011 under GPLv3, and it has been through two licensing regimes since. Today it is developed by Monospace Inc. (Brooklyn, New York), and the code is source-available on GitHub under the Monospace Sustainable Core License (MSCL) as of version 12 — a custom license based on the Fair Core License, with the notable commitment that every release converts to GPL-3.0 four years after publication. Before v12 the project used BSL 1.1 with the same core bargain: free for organizations under $5 million in total finances, paid commercial license above that. The team consulted Bruce Perens (OSI co-founder) on the structure and is explicit that it does not claim to be OSI-certified open source. We respect that candor; we also note the plain fact that "open source" in the DB tags is now a legacy description of the project, not its current license.

Pricing: what you really pay

There are two very different cost stories: self-hosting and Directus Cloud.

Self-hosted, the software is free under the Core tier — 3 user seats (a hard limit), 25 collections, 5 flows, advanced RBAC — and free without those limits if your organization qualifies for the Open Innovation Grant (under $5 million in total finances and, per the current criteria raised after community feedback, under 50 employees; a short form grants a license key). Above those thresholds, production use requires a commercial license. Your own infrastructure is on top, which for most teams means a $6-12/month VPS and a PostgreSQL instance — see our VPS provider reviews for what that hardware costs.

Directus Cloud is where the numbers get serious. The Professional plan is $99 per month (billed annually), including 5 Studio users, 75,000 database entries, 250,000 API requests per month, 500 GB of API bandwidth, 150 GB of file storage and a 500 MB maximum asset size; additional Studio users are $15 per user per month. The Team plan runs $599 per month billed monthly ($499 per month billed annually) with 10 SSO seats (extra seats $50/seat/month), 50 collections expandable to 100, and 20 flows. Enterprise is quote-based with custom limits, multiple environments, and premium support with SLAs. A hosted Open Innovation Grant arrangement exists at $99 per month for qualifying organizations.

Our read of that structure: the jump to a $99 cloud entry price (Directus previously sold a low-cost starter tier) and hard caps like 75,000 database entries and 250,000 API requests on the entry paid plan are the two facts a buyer must internalize. A moderately busy production API can blow through 250,000 requests in a day. On the self-host side, the seat/collection/flow caps on Core and the total-finances rule mean "free" has a boundary you should locate before you architect around it.

Performance & infrastructure

Directus is database-agnostic by design: it maps onto your existing SQL schema and does not require migrations into a proprietary store. That is the feature we value most, because data ownership and the ability to walk away are real architectural assets. APIs are generated automatically from the schema, GraphQL and REST both, with granular role-based permissions, audit logging, webhooks, and Flows (built-in automation) for event-driven logic.

Directus Cloud is fully managed — provisioning in roughly 90 seconds, automatic updates, scaling, and backups handled by the vendor. That is the honest division of labor: you bring the data model, they run the node processes, the database, and the file storage. The Studio (the admin UI) is one of the better data back-offices we have seen: non-technical editors can manage relational content without SQL, while developers keep the schema and API contracts.

On compliance and operations, the vendor advertises SOC 2 and GDPR alignment and HIPAA support; those claims come from vendor-facing pages and should be confirmed contractually for regulated workloads. The documentation is dense and generally good, the API reference is complete, and the extension system lets you write custom interfaces, endpoints, and hooks without forking the core. Community support is the default; premium support (customer success manager, 24/7 critical issue response, hands-on advisory) is reserved for production-license holders and Enterprise Cloud plans.

Where it falls short

The licensing deserves more scrutiny than the marketing gives it. MSCL is a custom license; whether you consider Directus "open source" depends on your definition, and the team says as much themselves. Every version converts to GPL-3.0 after four years, which is a genuine escape hatch and the strongest part of the deal — but a compliance team at a large enterprise will still read every clause, and the $5 million total-finances trigger (the largest of revenue, budget, or funding) is broader than a simple revenue test.

Second, Directus Cloud is expensive relative to the raw resources. $99 per month buys 5 seats and 75,000 entries — limits a self-hosted instance on a $12 Droplet does not impose. The managed service earns its price when your team's time is expensive and you want updates, backups, and scaling handled; it loses on pure economics at every scale.

Third, the platform has real learning-curve edges. Complex permission hierarchies, Flows, and the relational modeling in the Studio take time to master, and self-hosted production deployments are DevOps work: node processes, a database, file storage, and upgrade discipline. Directus will not do that for you unless you pay for Cloud.

The Studio deserves a word in its own right, because it is the part non-developers touch daily. Editors work with relational content through forms, file fields, and relational selectors instead of SQL, while developers retain the schema and API contracts underneath; the extension system (custom interfaces, endpoints, displays, and hooks) lets teams adapt the Studio without forking the core. Flows handle event-driven automation with triggers, conditions, and operations, which covers a surprising amount of the workflow-automation ground that would otherwise need a separate product.

Fourth, reliability and support transparency. Public status history exists but no uptime SLA is published outside Enterprise agreements, and the ecosystem — extensions, integrations, community answers — is smaller than Strapi's and far smaller than a hosted CMS like WordPress.com. The project's licensing changes have also churned community trust twice; that is a signal about governance, not code quality, but we weigh it.

Who should pick this

We'd pick Directus when the database already exists and the alternative is writing an admin panel and CRUD API by hand. Agencies managing multiple client back-offices, teams with legacy SQL schemas that need modern API access, and product teams that want editors working in a real UI over a relational model are the sweet spot. It is also a credible alternative to Retool-style internal tools where you want the data layer and the admin in one product.

Self-hosted Directus on your own infrastructure is, in our view, the configuration to beat: full data control, no entry caps, and the license cost is zero for organizations under the thresholds. We would choose Cloud when the team has no DevOps appetite and $99-599 per month is cheaper than an engineer's week per year.

We would not pick Directus if you need a battle-tested open-source license for a large enterprise (the commercial negotiation is real), if your API traffic is spiky and high-volume (the request caps bite), or if you want a pure headless CMS with a huge plugin marketplace — Strapi or a hosted CMS serves that better today.

Key takeaways

• Directus wraps any existing SQL database with a Studio UI and auto-generated REST/GraphQL APIs — database-agnostic and self-hostable.
• Licensing is source-available, not OSI open source: MSCL since v12 (BSL 1.1 before), free under $5M total finances / Open Innovation Grant, GPL-3.0 conversion four years after each release.
• Directus Cloud starts at $99/month (Professional: 5 seats, 75,000 entries, 250,000 API requests, 500 GB bandwidth, 150 GB storage); Team is $599/month monthly or $499 annually; Enterprise is custom.
• Self-hosting is free on the Core tier (3 seats, 25 collections, 5 flows) plus your own infrastructure costs.
• Managed Cloud handles updates, scaling, and backups; premium support and SLAs are Enterprise-only.
• Best for teams wrapping existing relational data who value data ownership; wrong fit for high-volume APIs on capped plans or enterprises needing a standard open-source license.

Sources

• https://directus.io/pricing/
• https://directus.com/resources/why-we-are-relicensing-directus
• https://directus.com/resources/1000-license-keys-granted
• https://directus.io/bsl-faq
• https://directus.com/docs/self-hosting/overview
• https://directus.com/about
• https://community.directus.com/t/recap-of-the-new-licence-for-the-youngsters/2298
• https://mobian.studio/directus-cms-pricing/
• https://frontdeskreview.com/software/headless-cms/directus/
• https://opsily.com/hosting/directus/directus-pricing
• https://crunchbase.com/organization/directus-io