8 engineers on Hacker News describe using Hasura first-hand: 4 endorse it, 1 regret it, 1 are mixed.
“We hit on exactly the same pattern for our product and it works really well. We use Hasura as the read engine.”
endorse · production · aidos · 2024-12-11 · source ↗ · wrong label?“using Graphql and Hasura absolutely did help us iterate more quickly early on”
mixed · production · peterldowns · 2024-05-30 · source ↗ · wrong label?“Hasura has an amazing UI to build permissions compared to Supabase sql based row level permissions”
endorse · production · yoeven · 2023-12-20 · source ↗ · wrong label?“We're using Hasura (started before Supabase was a thing...) and their Rails inspired migration is quite good.”
endorse · production · cpursley · 2023-08-07 · source ↗ · wrong label?“Hasura was enabling us to query already existing databases without rewriting the schema”
endorse · production · linkdd · 2021-03-16 · source ↗ · wrong label?“the lack of customization quickly became an issue... Ultimately it resulted in a slower development speed than what we were doing at my company before using Hasura”
regret · production · lukaspili · 2020-02-27 · source ↗ · wrong label?“I use Hasura a lot, which depends on Postgres”
neutral · production · presentation · 2022-10-07 · source ↗ · wrong label?“we migrated a webflow site to Next.js/GraphQL/Contentful/Hasura stack.”
neutral · production · zed88 · 2019-08-07 · source ↗ · wrong label?