When I tried them a few weeks back to compare, Hasura provided a nice interface, but has a lot going on itself (managing relationships on its own, some Auth stuff on its own) and its own tooling. Postgraphile relies more on postgres, it embeds it’s configuration in comments (or external to the dB). Both had difficulties with complex relationships and introspection across schema boundaries (I want a schema to house my data, and views in a separate schema that are accessed by the API tool). Both felt like I could configure this problem away, hasura wanted me to use their interface to do it, postgraphile wanted me to learn magic comments to attach to tables/columns etc (again, to tell a view that the table it’s drawing from has a relationship with another table).

PostGrest has none of these problems, but/and no graphql. It’s where I landed.

Also, check out dbmate for agnostic rollback management. All it needs is a way to template the sql and I’ll be happier. Some folks using Postgrest use Alembic and SQL Alchemy to build/manage migrations—I’m not sure where I sit on that yet.

I've done exactly that with a sample food delivery project. Same frontend, but two different backends (one with Hasura, one with Postgraphile).

Feel free to check it out: https://github.com/sastraxi/great-bear

This is very cool, as is your git-like tool for PG! Thanks for sharing.

It's pretty easy to do raw sql rails migrations. I do it all the time.