# Hasura GraphQL Engine

Blazing fast, instant realtime GraphQL APIs on all your data with fine grained access control, also trigger webhooks on database events.

Repository: https://github.com/hasura/graphql-engine
Canonical: https://ross.abutalabs.com/products/hasura-graphql-engine
Homepage: https://hasura.io
Language: TypeScript
License: Apache-2.0
License Family: permissive
Topics: graphql, graphql-server, postgres, hasura, access-control, automatic-api, api, rest-api, graphql-api, sql-server, bigquery, haskell, mongodb, subgraph, supergraph
Last push: 2026-08-19T16:56:27+00:00
Link (homepage): https://hasura.io

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 98, release rhythm 98, longevity 100
- inputs: {"age_days": 2998, "days_push": 14, "days_rel": 15, "gap_med": 12.5, "n_releases_24m": 41}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 32098, forks 3043 (observed 2026-08-28T04:11:57.437402+00:00)

## What it is
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
- artifact type: service
- maturity: active
- function: graphql, api-framework, authorization, webhook, database, http-server
- domain: apis, backend, web-development, databases, developer-tools
- platform: self-hosted, cloud
- tags: 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

## Member repositories
- hasura/graphql-engine (main) score 98
- hasura/learn-graphql (docs) score 39

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:11:57.437402+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T16:52:11.801493+00:00, confidence not recorded.
  - readme: https://github.com/hasura/graphql-engine (fetched 2026-08-28T04:11:57.437402+00:00, sha de171f201a4f)
  - homepage: https://hasura.io (fetched 2026-08-29T07:49:37.418142+00:00, sha b2fb35980b6a)
- Data as of 2026-08-30T08:39:29.467469+00:00.