Other upsides are a much better RBAC column/row permissions, migrations with up/down, a better admin UI.
I find that with new tech, I'm more interested in what it can't do rather than what it can.
One big one is at some point you need caching on a query level, and for that you have to purchase enterprise. I suppose they need to make money somehow, and it's a smart level to do it because it's almost impossible to not need caching at some fairly early stage. It would be nice if they let you test it out without "Contact Sales", and while there may be some way to wrap it from above, I don't think it's very easy.
A meta critique would be the project seems to have less momentum than Prisma. Releases aren't as frequent or large, and I'd have much preferred they double down on PG and keep adding query abilities, performance, etc, instead of expanding database engines.
That sounds like it has "vendor lock-in" written all over it.
Hasura is really awesome, so far as I have used it.
Now I gotta look into prisma
I almost wonder if they aren't mutually exclusive. With hasura, you need to run your own server anyways, for auth or special cases. Maybe that server could run prisma? Let hasura do the migrations, and prisma track it?