We’re introducing an update to the Directus licensing structure to make it simpler, clearer, and more transparent for our community.
For the past three years, Directus has operated under the Business Source License (BSL). During that time, our ecosystem has matured significantly, and we’ve learned a lot from real-world usage… both in how the license works, and where it creates confusion.
With the launch of v12 in May, we’re evolving that structure with the introduction of the Monospace Sustainable Core License (MSCL), a source-available license derived from the Fair Core License (FCL).
TL;DR
- Innovation Grant: Individuals and organizations under the threshold (under $5M in annual revenue and 50 employees) can use the Directus platform completely free.
- Free Core Tier: Even above those thresholds, you can still explore and build on Directus for free within our Core tier limits.
- 4-Year Open Source Conversion: Every version automatically becomes fully open source (GPLv3) after 4 years.
- Clearer Structure: We’re separating the license and the grant to remove ambiguity and make everything easier to understand.
- Software Keys: We’re introducing registration keys to replace the previous honor system and ensure consistency.
- SDKs Stay MIT: Our SDKs and other open-source projects like
rstoreandvue-split-panelremain under the MIT license.
Why We’re Making This Change
Our values haven't changed. We're just making the rules easier to follow.
Under BSL, we included a “usage grant” directly inside the license that allowed companies under $5M in “total finances” to use Directus for free. In practice, that language created gray areas.
Teams asked questions like:
- Does “finances” mean revenue, funding, or budget?
- How does this apply to subsidiaries or parent companies?
- What actually counts as production use?
At the same time, we’ve also operated on an honor system. That worked well in many cases… but it also created ambiguity and inconsistency, especially at larger scales.
This update is about fixing both of those things.
A Clearer Model: MSCL + Innovation Grant
We’re moving from a bundled BSL + grant model to two distinct parts:
- MSCL (Monospace Sustainable Core License) A source-available license that governs how the software can be used and distributed.
- Innovation Grant A separate grant that defines who can use Directus for free.
By separating these, we remove the need to embed business rules inside legal language… and make the whole system easier to reason about.
If you qualify for the Innovation Grant, nothing changes for you. You get full access to the platform, for free.
Free for Builders, Sustainable at Scale
Our goal is to keep Directus accessible to the vast majority of builders while ensuring the project can sustainably grow.
- Under $5M revenue + under 50 employees? You can use the full platform for free.
- Above those thresholds? You can still use Directus for free within the Core tier to explore, prototype, and build.
At the same time, we’re introducing paid tiers that gate more advanced, enterprise-focused features (like SCIM and offline mode).
These are capabilities typically used at larger scale… and having them in paid tiers ensures that the most complex use cases help fund ongoing development of the core platform for everyone else.
Moving Beyond the Honor System
One of the biggest changes here is how this is enforced.
Over the past few years, we’ve relied on an honor system. While that worked in many cases, it also led to unclear boundaries and inconsistent usage.
With this update, we’re introducing software registration keys for both paid users and those using the Innovation Grant, while keeping the free Core tier available without any registration.
This helps:
- Remove ambiguity around eligibility and usage
- Ensure consistency across all users
- Provide a more sustainable foundation for the project
One of the reasons we chose the Fair Core License as a base is that it allows us to protect this system… ensuring license key functionality remains intact.
How the MSCL Works
The MSCL is designed around three core ideas:
- Source available: You can always view, audit, and understand the code
- Flexible usage: You can use, modify, and build on Directus freely
- Eventually open source: Every version becomes GPLv3 after 4 years
The only restriction is competing use… meaning you can’t build and sell a product whose primary purpose is to directly compete with Directus.
This does not restrict hosting Directus, building products on top of it, or offering services around it.
What This Means
Again, I want to strongly reiterate - nothing is getting taken away here.
- If you’re learning, experimenting, or building as an individual or small team, you still have full access to Directus.
- If you’re using Directus at scale, this creates a clearer and more consistent framework for how the platform is used and supported.
And most importantly, it lets us keep investing in Directus for the long haul… without losing the openness it was built on.
Final Thoughts
License changes are a big deal. We didn't take this one lightly. This reflects years of feedback and real-world usage.
This update reflects years of feedback, real-world usage, and careful consideration. Our goal is simple: make Directus easier to understand, easier to adopt, and easier to trust.
If you have thoughts, concerns, or edge cases we should think through… I’d genuinely love to hear them!