shouldiuse.io

Comparison

PostgREST 16 vs Hasura

PostgREST 16 and Hasura both land on Depends.

Hasura

Depends
Confidence: Medium

Buy if you run Postgres and need instant, governed GraphQL with realtime and federation at real scale.

PostgREST 16 versus Hasura
ComparePostgREST 16Hasura
VerdictDependsDepends
Best forPostgres-first developersPostgres-heavy products needing instant GraphQL
Who it's not forNon-technical teams wanting a managed API . no vendor to callSmall CRUD apps . Supabase or PostgREST is cheaper and simpler
PrivacyNo known public vulnerabilities found in the sources reviewed.³Multiple public CVEs across versions; vendor discloses and patches, but auth misconfiguration remains the top real-world risk.
Support qualityNo support evidence foundNo supporting evidence in sources
Public sentimentDevelopers on Hacker News and Reddit praise PostgREST for spinning up APIs straight from Postgres, with complaints sparse in available sources.⁶Reviewers praise the instant-API model and production stability but complain about pricing changes and permission complexity.10
Biggest gotchaLeaving Supabase Cloud surfaces PostgREST config failures that produce no error⁷2023 pricing overhaul caused bill shock; community called it 'full bananas'12

Pick PostgREST 16 when

  • Postgres-first developers
  • Internal tools and admin APIs
  • Teams treating the DB as single source of truth
  • CRUD backends without custom servers

When PostgREST 16 is not a fit

  • Non-technical teams wanting a managed API . no vendor to call
  • Buyers needing SLAs, vendor support, or a pricing plan
  • Teams unwilling to own Postgres roles, RLS, and schema design
  • Projects needing custom business logic beyond CRUD endpoints

Pick Hasura when

  • Postgres-heavy products needing instant GraphQL
  • Realtime apps using subscriptions
  • Federating many data sources into one API (DDN)
  • Platform teams standardizing data access

When Hasura is not a fit

  • Small CRUD apps . Supabase or PostgREST is cheaper and simpler
  • Teams wanting a predictable flat monthly bill
  • Non-GraphQL stacks hunting a basic REST BaaS
  • Teams that can't patch engine CVEs quickly

Sources

  1. official
  2. official
  3. security
  4. review
  5. review
  6. review
  7. news
  8. review
  9. review
  10. review
  11. review
  12. review
  13. review
  14. Philips Healthcare case studygraphql-engine-cdn.hasura.io
    official
  15. Pipe case studygraphql-engine-cdn.hasura.io
    official
  16. official