Broadly similar projects! The emphasis of Hasura is to make it seamless to work with existing databases.

The primary difference is how authorization is handled. In Postgraphile, you map your application roles to Postgres users and define policies using Postgres's RLS. With Hasura, you define rules on roles (similar to Postgres's RLS) but it integrates into your existing auth system using webhooks.

Also, peripherally, we have quite a bit of tooling with an admin UI and a rails-like migration system to make the dev workflows easier :)

> The emphasis of Hasura is to make it seamless to work with existing databases.

Yet, I spent 15 minutes searching for example of using Hasura with an existing schema. Your "Getting Started" page has two examples: Deploy on Heroku and Run with Docker - in both cases, using a fresh database, not an existing one.

Bugger! Sorry for the inconvenience. We're updating the docs now to make this easier to navigate too.

EDIT: Docs updated, we'll keep improving it too :)

Can you share the link? This page still refers to new database: https://docs.hasura.io/1.0/graphql/manual/getting-started/in...

Homepage has the GitLab example, but not actual "Getting Started" page.

For Heroku: https://docs.hasura.io/1.0/graphql/manual/deployment/heroku/...

For Docker: https://docs.hasura.io/1.0/graphql/manual/deployment/docker/...

It's worth mentioning that postgraphql was renamed to postgraphile. They are the same project.