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.