Hasura connected straight to our existing Postgres and gave us a complete GraphQL API instantly, no resolvers to write. The granular row-level permissions saved us from building a whole auth layer ourselves. Our small team shipped a product months faster than planned.
Instant API, powerful permissions
We built our frontend entirely on Hasura's auto-generated GraphQL API, and an upgrade silently changed how some permission rules and aggregate queries behaved. Half our dashboards returned nulls overnight and the migration notes didn't warn about it clearly. Spent a full weekend rolling back and rewriting queries.
Undocumented breaking changes on upgrade
For simple CRUD Hasura is fantastic, but once our queries got deeply nested across many relations the generated SQL got slow and hard to optimise. We ended up writing custom database views just to keep response times reasonable, which defeated part of the appeal.
Fine for simple queries
Slow on deep nested joins
I genuinely love working with Hasura. The console makes exploring relationships effortless, subscriptions for real-time data just work, and the event triggers let us hook business logic without polling. It turned database work into something I actually enjoy.
Real-time subscriptions, great console
Hasura got us moving incredibly fast and the GraphQL API is a joy for the frontend team. But as the project grew, debugging the auto-generated queries and managing permissions across dozens of tables became genuinely tricky. Great tool, just know what you're signing up for long-term.
Fast to start
Complexity grows with scale