Out of curiosity, what don’t you like about it?

Off the top of my head: It surfaces only useless GraphQL error messages to the front end, it’s very frustrating to stand up custom REST endpoints, and the Flow system is painful to develop with and debug. Others on my team have different gripes with it.

Thanks for the feedback!

Since they support so many databases the integration with specific providers is very shallow - e.g. they do not allow to make use of SQL views.

I personally found the typescript support disappointing in general but specifically around strict null handling. Their graphql schema was also declaring far to many fields as nullable which was a deal breaker for me looking for at least one way to generate precise typescript typings.

The eternal red flag of a DB UI that tries to support wildly different backends explains a lot of the problems. Many sane and powerful Postgres features can't be used because Directus also needs to support SQLite, for example. Views not properly supported, search features inadequate, graphql DSL with arbitrary limitations, a lot of weird or dysfunctional relational patterns when something much simpler would do... it's a parallel, inferior system on top of stock pg that is very frustrating when used at some depth.

How does it measure up to Hasura?

No idea, I’ve never used that.

This sounds like a very similar service to Hasura, and I just loved using it. I also have some of former colleagues building it, and they've been one of the best engineers I've ever had privilege of working alongside of. If you're already using a tool that occupies very similar place in your stack, I would really suggest evaluating a migration.

It does not appear that Hasura is fully open source. I'd much rather use Directus, as I don't consider closed source solutions viable.

I’m in a similar situation. At first it looked very promising and was benefiting us in bootstrapping the project fast but after a while you’re being slowed down by the “extensions” ecosystem. If you have a bunch of complex extensions then building all of them can take 2 minutes (m3 pro MacBook). Forget instant hot reloading.

Not having even the shadow of a control layer in your app is bound to come back and bite you imo.