Directus has its small-scale and short term benefits, but I can’t recommend building a production-grade app with it. My company uses Directus and we all hate it and are desperately trying to get away from it. Avoid.
Microsoft has something very similar (i did not do a full feature comparison, just speaking about apis and auth) which is mit licensed. Works also with on-prem databases despite it's name. <a href="https://github.com/Azure/data-api-builder">https://github.com/Azure/data-api-builder</a>
Had a play around with it, I'm impressed. I was very worried and put-off when I saw the nice-looking UI and flashy transitions, but this actually plays quite nicely with my database.<p>Unfortunately it doesn't work on Firefox 115 ESR due to<p><pre><code> Intl.Segmenter is not a constructor
</code></pre>
It's just a blank screen. So it is infected by the JS change treadmill somewhat.<p>I have a few other thoughts from my first try:<p>When using Directus on a pre-existing DB, your foreign keys need to have exactly the same type as the primary keys they are referencing for Directus to pick up on the relationship. For example, if you have `customer.id INT PRIMARY KEY`, you must reference it with `order.customer_id INT FOREIGN KEY REFERENCES customer (id)`. You cannot do `order.customer_id INT NOT NULL FOREIGN KEY REFERENCES customer (id)` , else Directus won't notice.<p>I also found it fairly slow to pick up on schema changes I made in the DB directly, and I didn't see an obvious way to force it to discover.<p>When using Directus to manage the DB schema, I found the tables it created to have a generally sane and simple schema, which is refreshing. I liked the choices here more than nocodb.<p>I can't comment on the REST/GraphQL generation. I'm mainly interested in the admin panel features.<p>The compose file they provide here works: <a href="https://docs.directus.io/self-hosted/docker-guide.html" rel="nofollow">https://docs.directus.io/self-hosted/docker-guide.html</a><p>Overall I think this works best if your data model is very clean. It would probably be painful to onboard a complex legacy DB. I think this is totally fine as a small-scale org data management tool. I was going to make one of these, but I don't need to now. Thanks for sharing.
At work we have two applications in production with Directus, a CMS and a CRM, both highly specialized (~35 custom extensions) for our use-cases.<p>We've had our teething issues, mostly with migrations and the UX in some areas, but overall it has saved us a ton of dev time and been a great force multiplier for us.<p>I also use it at home to manage my notes, tasks, and such as structured data.
I made something kind of similar <a href="https://saasufy.com/" rel="nofollow">https://saasufy.com/</a> but currently only tied to a single database but particularly good at scaling real-time updates. I'm looking for a non-tech co-founder who can drive to a niche use case.<p>As an example of its capabilities I built this from scratch without frameworks and completely server-less (basically just a .html file, .css file and a couple of .js files hosted only on GitHub): <a href="https://www.insnare.net/app/#/dashboard/company-filter/tags%20index-equals%20position%3Aelectronics-engineering/company-page/1/companies//people-filter/tags%20contains%20position%3Aelectronics-engineering/minimal-view/hardware" rel="nofollow">https://www.insnare.net/app/#/dashboard/company-filter/tags%...</a><p>That entire app is less than 4K lines of code; all frontend code.
I used this to bootstrap a small community page with a handful of admin users that entered content. The users were technical enough to be comfortable with the interface, but wouldn't have been able to use SQL directly. It saved building out the CRUD interfaces with the ~4 hours a week of dev time we had at the time. It took us a few months to get around to the CRUD interfaces, so it felt well worth it.
I’m using this as an admin UI on top of an existing database, it works pretty well for that, it’s nice that it doesn’t dictate your db schema.
I don’t really see the point of their “flows”, and I’m not sure how the auto-generated APIs hold up under load, but I’d recommend it for content management if you are ok with the license (it’s not FOSS).
Does anybody know something like Directus (building REST APIs on top of Postgres) with the ability to hook in custom authorization logic? (E.g. to do FGA checks before returning data)
If you’re dealing with pure SQL of a third party system, instead of an API, then you’re designing the API without domain knowledge. This is a problem in my experience.