[knrz]

This is cool! Learned about JigsawStack.

Curious, can you share your decision making for adding Hasura on top of Supabase? I used Hasura a couple of years ago, recently started using Supabase and it seems to cover my Hasura use case in a simpler way.

[yoeven]

Yeah! I'm the founder of JigsawStack, happy to help if you have any feedback or questions.

I've been using Hasura generally with vanilla Postgres DBs and I've mainly used it for three real reason: Client side permission management, DB dashboard and GraphQL.

Supabase has done an amazing job trying cover all those aspects with their own solutions but I still find Hasura really found the sweet spots for those aspects a little better and more fine tuned.

Client side permission: Hasura has an amazing UI to build permissions compared to Supabase sql based row level permissions where I still need to right code and then verify it

DB dashboard: managing the db, adding/removing columns, changing types, creating triggers, index etc, works/feels a lot better to me on hasura or maybe its just something I've gotten use to

GraphQL - I love writing in GraphQL, and Supabase Graphql layer isn't production standard at this stage.

Again, a lot of this is preferences and my personal opinion. You can build amazing products with just Supabase for sure, just a lot faster for me with Hasura right now :)