This is very seductive, but what happens when I need to refactor the database? Do all my API consumers just have to deal with a new interface?

Yes, A popular convention when using such tools is to use views for any tables that may change, and then treat those views as public interface.

So, when you refactor the underlying, you can also update your view definition so that the interface remains the same.

Is it possible to also expose a websocket that emits changes?

Hasura has this https://hasura.io/docs/latest/graphql/core/databases/postgre...

Looks neat. Love the name!