Ross ROSS = Recommend OSS · open-source software intelligence for agents

Hasura GraphQL Engine

Blazing fast, instant realtime GraphQL APIs on all your data with fine grained access control, also trigger webhooks on database events. observed · 2026-08-28

github.com/hasura/graphql-engine · homepage · TypeScript · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

98/100

  • Activity 98
  • Release rhythm 98
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 12.5
  • age_days: 2998
  • days_rel: 15
  • days_push: 14
  • n_releases_24m: 41

Full methodology

Adoption not part of the score

32098 stars · 3043 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Hasura GraphQL Engine is an open-source engine that auto-generates instant, realtime GraphQL APIs (and REST endpoints) over existing databases like PostgreSQL, MongoDB, SQL Server, ClickHouse, and BigQuery, with fine-grained access control and webhook triggers on database events. It is developed as a large mono-repo containing both the stable V2 engine and the newer V3 (DDN) architecture with open-source data connectors and TypeScript/Python/Go SDKs for custom business logic.

Use cases

  • auto-generate a graphql api from my postgres database
  • add realtime subscriptions to my existing database
  • expose mongodb data through a graphql endpoint
  • add fine-grained role-based access control to database apis
  • trigger webhooks when database rows change
  • federate multiple data sources into a single graphql supergraph
  • build a backend api without writing server code

When to choose

  • you want instant, auto-generated GraphQL APIs over existing databases without writing resolvers
  • you need realtime subscriptions and fine-grained authorization on your data layer
  • you want to unify multiple databases and services behind one composable GraphQL endpoint
  • you prefer declarative metadata-driven API configuration over hand-coded backends

When to avoid

  • you need full control over custom resolver logic and prefer a code-first GraphQL server
  • your data sources are not among the supported connectors (Postgres, MongoDB, SQL Server, ClickHouse, BigQuery, etc.)
  • you want a lightweight minimal API layer and find the engine's metadata/ops overhead excessive
  • you depend heavily on the legacy V2 feature set and are not ready to migrate to the V3/DDN architecture

Facets

service · maturity active

graphql api-framework authorization webhook database http-server apis backend web-development databases developer-tools self-hosted cloud graphql-engine instant-apis realtime-subscriptions postgres mongodb sql-server bigquery clickhouse data-delivery-network supergraph federation access-control database-events docker web-server kubernetes

2 sources

Member repositories

RepositoryRoleHealth v2
hasura/graphql-enginemain98
hasura/learn-graphqldocs39

For agents

markdown · JSON · MCP: product_card(name="hasura/graphql-engine")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem