Hasura GraphQL Engine v2
GraphQL API engine that exposes connected databases through permission-aware application APIs.
7 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Deploy the documented v2 Docker Compose setup; select the versioned -ce image when only open-source components are required.
Runs in
Documented customer environment
Customer-operated API engine with PostgreSQL metadata database and connected data sources
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
Customer manages engine and metadata storage, database access, admin secrets, authorization, TLS, and coordinated engine/database upgrades.
Deployment boundaries by provider
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Hasura GraphQL Engine on Azure Container Instances ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Hasura GraphQL Engine on Google Kubernetes Engine ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Deploy the documented v2 Docker Compose setup; select the versioned -ce image when only open-source components are required. |
|---|---|
| Infrastructure | Servers / containers 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. |
| Licensing model | Open Source / Open Core 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. |
| 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. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
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.
Hasura v2 Enterprise administrative Console, not every API client · Source ↗ · Reviewed 2026-11-14
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (master v2 example (moving)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
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.
Hasura v2 production and tuning guidance; current workload-specific compute/storage sizing remains unconfirmed · Source ↗ · v2 subscription saturation and performance tuning ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
GraphQL Engine v2 CE versus commercial image/features; not Hasura v3 DDN · Source ↗ · Official image and CE variant distinction ↗ · Self-Hosted Enterprise v2 scope ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
Upstream hasura/graphql-engine release record; commercial editions and deployment packages may differ · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
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.
Community & 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.
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.
Compare within Backend platforms
- Appwrite Self-HostedSelf-hosted backend services for authentication, databases, storage, functions and messaging.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
- AWS
- Azure
- Google Cloud
- HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
- AWS
- Azure
- Google Cloud
- KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
- Northflank
- Kong Gateway Self-ManagedOpen-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
- AWS
- Azure
- Google Cloud
- Medplum Self-HostedOpen-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
- AWS
- Azure
- Google Cloud
- Parse ServerNode.js application backend for data APIs, users, permissions and server-side application logic.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Heroku
- Red Hat OpenShift Container PlatformCommercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
- AWS
- Azure
- Google Cloud
- Alibaba Cloud
- IBM Cloud
Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official installation and runtime ↗hasura.io
- Upstream project and capabilities ↗github.com
- Current upstream license ↗raw.githubusercontent.com
- Official image and -ce licensing distinction ↗hub.docker.com
- v2 capabilities and Community Edition ↗hasura.io
- Hasura v2.51.6 PostgreSQL upgrade-order fix ↗github.com
- Hasura v2.50.9 PostgreSQL upgrade-order fix ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Hasura GraphQL Engine on Azure Container Instances ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Hasura GraphQL Engine on Google Kubernetes Engine ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Hasura GraphQL Engine on Azure Container Instances ↗ · Azure
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked