Directus v12 will be released soon. This major version brings a major refresh to the platform, including a native draft & publishing experience, a redesigned Studio, and new AI-powered translation tools. Whether you’re planning your upgrade path, excited about the new features, or navigating the new software registration keys, this is the place to ask questions and share feedback.
7 Answers
7Hi @Burvs! The Directus v12 Studio redesign is not related to the RUST rebuild. That project is a separate product called Monospace that is currently in preview. Directus continues to be built on TypeScript (Node.js) and Vue. The Directus v12 redesign is a structural update to the Studio’s core layout: the module bar, navigation, header, and sidebar. The goal has been to modernize the interface. The update provides a visual foundation for the new draft and publishing workflows included in v12 as well as other content editing workflow improvements that are slated for later releases. We’re looking forward to getting v12 into your hands very soon! Let us know if you have any other questions.
Thanks @emmapaaj that all sounds really positive. I've signed up to the Monospace waitlist and look forward to seeing the new Directus v12.
– BurvsVery interested to hear about the redesigned studio and the extent of this. Is this the RUST rebuild we’ve been hearing about?
Hi
Keep good work 
As my point of view, I will be happier to see config as code in v12 that results in better migrations, version control and less headache.
Hi @emmapaaj I have a question about how the license keys will work.
We are a small business using Directus on the Innovation Grant as we’re well under the 50 employee / $5m revenue cap.
We run three instances of Directus: the main production one, a development one, and I have a third local one on my mac which I use for extension development.
Will we need different keys for each of these instances?
Thanks.
As a Directus Builder, the new licencing terms for self hosted are not welcome news. 3 seats, 5 flows, no SSO..!? This changes things for me dramatically and I’m now having to rethink my platform choices. Sad, given that we were promised the self-hosted version would always have the full features 
(as per discussions in Office Hours sessions).
If you're under $5m and 50 employees you can apply for the innovation grant and have no limits.
– BurvsThe Open Innovation Grant agreement includes a compound clause that the grant, “expire[s] annually and [is] subject to periodic eligibility reviews,” as well as an additional clause that the grantee, “agrees to provide information reasonably requested by Directus to confirm eligibility.” I think a lot of users would benefit from understanding this review process more clearly.
The second clause is specifically about information that the grantee must actively provide. So what does an eligibility review actually consist of? And what falls under “information reasonably requested”? And since “periodic” is distinct in the agreement language from the annual expiration, can an eligibility review occur beyond the yearly renewal?
Since the license key revocation clause states that “Directus may revoke, suspend, or disable any License Key at any time, including for false or inaccurate eligibility information,” again, how exactly are you assessing for false or inaccurate eligibility attestations?
Good questions, happy to clarify! Eligibility reviews assess the two key thresholds in the grant: revenue and headcount. We use information provided at signup alongside third-party data sources and periodic manual checks by our team to assess ongoing eligibility. "Information reasonably requested" covers any follow-up we might need when that picture is unclear, typically a direct ask for updated company details.
– emmapaajPeriodic reviews and annual expiration are distinct. Annual expiration is the scheduled renewal gate. Periodic eligibility reviews can happen at any time. We can and do assess eligibility outside the annual window as well.
– emmapaajThe intent is straightforward: the grant is designed for companies and users that can't yet afford a commercial license, and we want getting started to be frictionless. We're offering something genuinely valuable for free, and the eligibility process is simply how we make sure it goes to the users and organizations it's actually meant for. If you represent your situation accurately, there's nothing to worry about.
– emmapaajI applied for the Innovation Grant license by emailing licensing@directus.io and also tried again by filling in the form on the website, but have had no response from either yet.
Hi! Open Innovation Grant keys are issued through the form at https://directus.com/oig. You should receive your software key via email immediately after submitting the form. Could you check your spam folder, please, and let us know if you find the email?
– emmapaajI've just received it now thanks. I didn't get it immediately when I filled in the form the other day though.
– Burvs
Hey @Directus! We love your CMS but hit a DevOps roadblock with multi-environment deployments (Supabase+Coolify+Vercel). Managing Staging & Prod requires separate instances. Promoting schema changes relies on manual CLI snapshot/apply commands. This creates massive CI/CD overhead, forcing us to evaluate Baserow. A GitOps-friendly way to switch DB contexts or sync schemas without hard-coupled containers would be a game-changer. Hoping Directus Hub solves this soon!
– Bohdan