Monospace from Directus

granular permissions model is the key claim here. does that go down to row/field level per agent, or just table-level access? asking because the agent attack surface is different from a human dev's - an agent can get tricked into requesting data it technically has access to but shouldn't touch in that context.

After 5+ years of building tools like Directus and testing many tools on the market, it takes a lot to truly blow me away.But, Monospace completely did.Not saying this just because I’m on the team but I’m saying it as a builder who knows the pain of fragmented data. Being able to manage data from multiple sources in a single place, wrapped in a sleek, intuitive UI? Game changer.The developer experience is next-level and performance is next level speed.

Hey everyone, Florian here, Staff Software Engineer on the Monospace frontend team, working on the Studio experience.My colleagues have covered the why and the how, so I'll just share what I'm most excited about: what comes next.What we're launching today is the foundation. We spent a lot of time getting the basics right, and now that they're in place, we can move a lot faster. You'll see us ship more and more from here, so if today got you curious, stay tuned. This is only the start 🚀And if you try the Studio, I'd love to hear what you'd want it to do next.

Looks promising! 🤞 I'm thinking about how this will enable business to create internal apps or work with data across all connected databases and services. Are there any guardrails for less-technical users to make sure that they won't ruin anything by just testing the platform out?

Love the idea of one way to access data across different systems...Really impressive launch! Curious to see where you take this.The permissions and governance piece feels especially useful.

Heya! 👋 Super excited to finally lift the curtains on Monospace! We've spent the last decade building Directus and helping people out with their data and content management needs. Monospace takes what we've learned during that time and applies it to a problem that we keep seeing: data scattered across systems, with every new app or AI agent needing another integration and another set of access rules.The fact that Monospace can deliver your data as a single unified governed API without having to copy over all your data into it's own system is magical ✨Love to hear what you're connecting to in your projects, and where giving an app or agent access to that fleet of data sources is difficult today :)

Sounds like an improved API management for layer for AI era applications. All the best with the launch.

We've used Directus internally at Directus for years now and have it powering many of our internal teams and systems. It's been amazing to dogfood our own product for so many years and learn, iterate and adapt with both our users and ourselves in mind. However, these separate systems are just that, separated. I am excited to see Monospace can bring these together as we continue to iterate on both products and see how they work together.Congrats to the whole team. 👏

Okay investor hat on! Who are your main competitors in this space? no pun intended. And how do you compete? whats your differentiator against the competition?

Hey everyone! Antonio here from Customer Success.A lot of what's in Monospace started as feedback from the people using Directus every day, and it's been amazing to watch that turn into something so great.Huge team effort getting here, proud to be part of it.Looking forward to hearing what you think!

I'm thrilled that Monospace is finally out for the world to use it!I've been contributing to its frontend for the past months and it's been hard keeping it internally because it simply rocks!It's free, it's full of powerful features (extensions and custom connectors, SSO support, Partial Introspection, UI views and builders, Native AI support, ...)PLEASE let us know if you find anything that still needs fine-tuning, or if you find it awesome!

Hey, I'm Gaetan, engineer at Monospace !Really proud to finally share what we've been building. I've been working on both sides of the product, the Rust engine and the Studio, and what I love the most is how quickly you go from your database to a real API and an app your whole team can use.Huge thanks to the team, it's been a crazy ride to get here. And to everyone trying it today: play with it, push it to its limits, ask the hard questions and tell us what's missing, we read everything !

After putting Monospace through the ringer over the last 6 weeks - it's impossible to not get excited when building with this tool.There are hard problems and then there are hard problems... And live data federation across databases, APIs, and services that: is self hostableis super performant and memory efficient (thanks Rust! 🦀)doesn't require ETL or data warehousescan allow flexible yet granular access policies for every type of callerscales easily for production workloadsand most important - makes life simpler for developers like myself....is indeed a very hard problem to solve. And as the head cheerleader over here at Directus, I just wanted to pop in and congrats to our freaking awesome team for bringing this idea into reality. There's far too many names to name so I'll just call out the engineering ring leader - @hanneskuettner - massive congrats to the team my friend. 🍻

The idea of generating live interfaces straight from existing databases without copying data is a smart angle. Curious how the permissions model handles really old schemas that were never designed for AI agents.

Love the idea and the animations across the website. Would definetly be playing around this on a pet project i'm working on.