
# Hasura GraphQL Engine v2

GraphQL API engine that exposes connected databases through permission-aware application APIs.

Canonical page: https://launchinyourcloud.com/directory/hasura-graphql-engine/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Hasura GraphQL Engine v2

GraphQL API engine that exposes connected databases through permission-aware application APIs.

- Listing: https://launchinyourcloud.com/directory/hasura-graphql-engine/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream open-source GraphQL Engine components. Default distributions can include separately licensed enterprise components; -ce images contain open-source components.
- Licensing model: open-source
- Installation: Deploy the documented v2 Docker Compose setup; select the versioned -ce image when only open-source components are required.
- Architecture: Customer-operated API engine with PostgreSQL metadata database and connected data sources
- Operations: Customer manages engine and metadata storage, database access, admin secrets, authorization, TLS, and coordinated engine/database upgrades.
- Product website: https://hasura.io/
- Source review: 2026-11-16; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-16

### Scope and qualifications

This listing is specifically for the self-operated v2 engine, not Hasura Cloud or DDN. Authentication webhooks, remote schemas, event handlers and database destinations can cross account boundaries. GraphQL Engine v2.51.6 and v2.50.9 fix source-catalog initialization and upgrades when PostgreSQL 15.15, 16.11, 17.7, or 18 and later enforce replica identity for INSERT ... ON CONFLICT DO UPDATE in a logical-replication publication. Upgrade GraphQL Engine before PostgreSQL. For older engine versions, the documented workaround is ALTER TABLE hdb_catalog.hdb_source_catalog_version REPLICA IDENTITY FULL on every data source, repeated whenever a new source is added.

Apache License 2.0 for upstream open-source GraphQL Engine components. Default distributions can include separately licensed enterprise components; -ce images contain open-source components. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated API engine with PostgreSQL metadata database and connected data sources. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support. Coordinate PostgreSQL patch upgrades with the GraphQL Engine version. Older engines can break source-catalog initialization or logical replication after upgrading to PostgreSQL 15.15, 16.11, 17.7, or 18 and later.


### Category fit

- backend-platforms: Database-backed GraphQL API layer with authorization, subscriptions and configured remote actions. It does not supply a complete standalone application database or identity provider.

### Deployment boundaries


- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://hasura.io/docs/2.0/deployment/deployment-guides/azure-container-instances-postgres/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://hasura.io/docs/2.0/deployment/deployment-guides/google-kubernetes-engine-cloud-sql/ (checked 2026-11-12). 


### Cloud deployment evidence

- Hasura GraphQL Engine on Azure Container Instances (azure): https://hasura.io/docs/2.0/deployment/deployment-guides/azure-container-instances-postgres/
  The v2 project documentation deploys the GraphQL Engine container on Azure Container Instances with PostgreSQL. Review secrets, database access and production hardening; Hasura Cloud regions are not used as evidence.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Hasura GraphQL Engine on Google Kubernetes Engine (gcp): https://hasura.io/docs/2.0/deployment/deployment-guides/google-kubernetes-engine-cloud-sql/
  The v2 project documentation deploys the GraphQL Engine on GKE with Cloud SQL. This establishes application hosting in the customer project, not just connectivity to a Google-hosted database.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

The upstream v2 release stream includes current security maintenance. Hasura documents a long-running developer community, public community calls and community contributions around GraphQL Engine.

Reviewed 2026-11-10.

- Current GraphQL Engine release maintenance: https://github.com/hasura/graphql-engine/releases

- Public developer community and calls: https://hasura.io/help/

- GraphQL Engine contribution history: https://hasura.io/blog/call-for-open-source-contributions

### Sources

- Official installation and runtime: https://hasura.io/docs/2.0/deployment/deployment-guides/docker/

- Upstream project and capabilities: https://github.com/hasura/graphql-engine

- Current upstream license: https://raw.githubusercontent.com/hasura/graphql-engine/master/LICENSE

- Official image and -ce licensing distinction: https://hub.docker.com/r/hasura/graphql-engine/

- v2 capabilities and Community Edition: https://hasura.io/docs/2.0/index/

- Hasura v2.51.6 PostgreSQL upgrade-order fix: https://github.com/hasura/graphql-engine/releases/tag/v2.51.6

- Hasura v2.50.9 PostgreSQL upgrade-order fix: https://github.com/hasura/graphql-engine/releases/tag/v2.50.9

### Licensing sources

- https://raw.githubusercontent.com/hasura/graphql-engine/master/LICENSE

### Infrastructure sources

- https://hasura.io/docs/2.0/deployment/deployment-guides/docker/

- https://github.com/hasura/graphql-engine/releases/tag/v2.51.6

- https://github.com/hasura/graphql-engine/releases/tag/v2.50.9


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Self-hosted Enterprise Console can integrate ADFS SAML through Dex from v2.25.0, with a valid license key. Console authentication is separate from GraphQL API JWT/webhook authorization and is not a CE entitlement. Scope: Hasura v2 Enterprise administrative Console, not every API client. Source: https://hasura.io/docs/2.0/enterprise/sso/adfs/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The v2 guide links an upstream Compose manifest with PostgreSQL metadata storage. Select the appropriate community/commercial image and set administrator/database credentials rather than exposing the defaults. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://hasura.io/docs/2.0/deployment/deployment-guides/docker/ (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/hasura/graphql-engine/master/install-manifests/docker-compose/docker-compose.yaml. Artifact reference: master v2 example (moving).

- Minimum footprint / sizing: Sources checked — unresolved. The v2 production checklist and subscription-tuning guide require database connection/concurrency planning and CPU/memory monitoring, but do not establish a numeric whole-stack minimum. Query complexity, live subscriptions, metadata/source databases and replicas determine capacity. Old tutorial VM allocations or Cloud auto-scaling are not a current 100-user, 1 TB HA sizing guarantee. Scope: Hasura v2 production and tuning guidance; current workload-specific compute/storage sizing remains unconfirmed. Source: https://hasura.io/docs/2.0/deployment/production-checklist/ (reviewed 2026-11-20). Supporting source: v2 subscription saturation and performance tuning — https://hasura.io/docs/2.0/subscriptions/observability-and-performance/.

- License pricing: Documented. The v2.51.6 open-source GraphQL Engine core is Apache-2.0 licensed. Hasura v2 Enterprise has separate commercial entitlements; the official image distribution distinguishes the -ce variant from images that include Enterprise components. Enterprise Console SSO is not granted by the CE licence, and DDN/Cloud pricing is not a self-hosted v2 quote. Scope: GraphQL Engine v2 CE versus commercial image/features; not Hasura v3 DDN. Source: https://github.com/hasura/graphql-engine/blob/v2.51.6/LICENSE (reviewed 2026-11-20). Supporting source: Official image and CE variant distinction — https://hub.docker.com/r/hasura/graphql-engine/. Supporting source: Self-Hosted Enterprise v2 scope — https://hasura.io/docs/2.0/enterprise/overview/.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v2.51.6, published 2026-11-11. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream hasura/graphql-engine release record; commercial editions and deployment packages may differ. Source: https://github.com/hasura/graphql-engine/releases/tag/v2.51.6 (reviewed 2026-11-14).






