Hasura GraphQL Engine

What it is

Hasura GraphQL Engine sits in front of your databases and instantly generates a GraphQL (and REST) API with built-in authorization, real-time subscriptions, and event triggers. Point it at Postgres (or another supported source), define permissions, and you get a production-grade API layer without hand-writing resolvers. It also federates across multiple data sources and existing GraphQL/REST services, acting as a unified API gateway.

Who builds it and why

Hasura is maintained by Hasura Inc. and an active open-source community — 428 contributors on GitHub is a healthy number for a project this specialized, indicating it's not a single-vendor side project on life support. Founding date and CNCF maturity status are not publicly available, and this project is not part of the CNCF landscape as far as public records show — it's a commercially-backed open source project, not a foundation-governed one. The core motivation is standard for this category: eliminate the boilerplate of building CRUD APIs and let engineering teams focus on business logic instead of resolver plumbing.

Production readiness signal

The signals here are strong. 32,027 GitHub stars and a last commit dated 2026-06-22 show active, ongoing development — this isn't an abandoned project coasting on past popularity. Latest release v2.49.3 indicates a mature, iterative versioning history rather than a project still finding its API surface. Apache-2.0 licensing means no restrictive terms blocking commercial or embedded use. What's missing from public data: CNCF maturity level and founding date, so you can't cite third-party governance validation — you're relying on GitHub activity and release cadence as your primary signal, which in this case looks solid.

Who should use this

• Teams with Postgres (or supported) databases who need a GraphQL API fast and don't want to maintain a custom resolver layer long-term.
• Startups and mid-size engineering teams that want built-in row-level authorization tied to their existing auth system without building it from scratch.
• Organizations doing API federation across multiple microservices/databases where a unified GraphQL gateway reduces client-side complexity.
• Teams that need real-time subscriptions (live queries) without standing up a separate WebSocket/pub-sub layer.

Who should NOT use this

• Teams with complex, deeply custom business logic in the API layer — Hasura's auto-generated schema is a strength for CRUD-heavy apps but becomes a fight when your domain logic doesn't map cleanly to database tables.
• Shops fully committed to REST with no near-term GraphQL need — adopting Hasura just to get a REST endpoint is solving a problem you don't have.
• Teams wary of vendor lock-in on the hosted/enterprise tiers — the open-source core is solid, but advanced features (caching, observability, enterprise auth) push you toward Hasura Cloud or Enterprise, and migrating off that later isn't trivial.
• Organizations needing tight, custom control over query performance at extreme scale — auto-generated queries can produce inefficient SQL under complex nested queries; teams with strict DB performance SLAs often end up hand-tuning or bypassing Hasura for hot paths.
• Anyone expecting CNCF-style governance guarantees — with maturity status not publicly documented, if vendor-neutral governance is a procurement requirement, this won't satisfy that checkbox today.

Alternatives

• PostGraphile — similar Postgres-to-GraphQL auto-generation, more opinionated toward Postgres-native features (RLS, functions) and lighter-weight to self-host.
• Apollo Server / Apollo Federation — if you want full manual control over resolvers and schema composition rather than auto-generation, Apollo gives you the building blocks instead of the finished API.
• AWS AppSync — a managed alternative if you're fully committed to AWS and want GraphQL + real-time without operating any infrastructure yourself.

Pricing

The core GraphQL Engine is fully open source under Apache-2.0 — self-host it for free with no feature gating on the core API generation, auth, and subscriptions. Hasura also offers a paid Cloud and Enterprise tier (hosted infrastructure, advanced caching, observability, dedicated support) — specific pricing for those tiers is not publicly available here and should be confirmed directly with Hasura.