Hasura

Name: Hasura
Brand: Hasura

Hasura is a data API platform that automatically generates GraphQL (and optional REST) APIs over existing data sources, provides declarative authorization and real-time subscriptions, and composes data from multiple backends into a unified API layer.

Est 2017|Valuation $1B|Raised $136.3M|16 Ref Customers

LinkedIn 20K|Web traffic 95K|FTEs 156

MarketsAPI Management

Published Oct 23, 2026

01Common complaints

1. Need for strict API abstraction from database schema - If the GraphQL schema must remain stable and independent of storage evolution, a database-first mapping may be unsuitable. Consider schema-first servers or a gateway that enforces domain boundaries. 2. Heavy investment in DynamoDB-only architectures - If the environment is primarily DynamoDB-based, a managed GraphQL service that integrates natively with DynamoDB may be preferable. 3. Requirement for maximum schema composition flexibility across many protocols - If the project requires extensive unification of REST, gRPC, and legacy APIs with heavy transformation logic, a gateway/mesh approach may offer more flexibility despite increased engineering effort. 4. Need for fully transparent enterprise pricing up front - If procurement requires explicit, line-item pricing without negotiation, the vendor's sales-led enterprise engagements may be a limitation.

Deal disqualifiers (poor fit)

Requirement for a strictly curated, domain-driven GraphQL schema decoupled from storage.
Primary dependence on data stores that do not have suitable connectors or support within the platform (example noted in reviews: DynamoDB-centric environments).
Heavy reliance on custom resolver logic across most endpoints where a configuration-driven approach would be limiting.

Frequently mentioned limitations

Generated GraphQL schema verbosity can affect client ergonomics.
Tight coupling between database schema and GraphQL schema can constrain API evolution.
Onboarding complexity for users new to the platform.
Gaps in database support for specific stacks reported by some reviewers (example: DynamoDB).

Vendor-acknowledged roadmap and version transitions

Hasura V2 is the stable GraphQL Engine version referenced in public repositories.
Later platform versions (referred to in vendor materials as V3/DDN) are positioned as the future of the data delivery platform with additional connector support and features.

Buyer implication: adopting during major platform transitions requires validation of migration tooling, feature parity, and operational differences.

02Why they buy

Unique selling points supported by user feedback and public documentation

Rapid provisioning of database-backed GraphQL APIs for supported sources, which reviewers report can shorten initial development cycles.
Declarative permissions and access control mechanisms built into the platform.
Native support for GraphQL subscriptions and real-time data delivery.

Differentiation vs competitors (balanced)

Compared with DIY GraphQL server approaches, Hasura reduces the amount of resolver and CRUD boilerplate required for supported databases, at the cost of closer coupling between API and storage schemas.
Compared with managed cloud GraphQL services that are tightly integrated with a single cloud provider, Hasura can be deployed in a cloud-agnostic manner or in dedicated VPC configurations for hosted plans.

03Field reports

Review-platform sentiment (G2)

Hasura is very highly rated on G2. Reviewer feedback commonly highlights developer productivity and speed of API delivery as positive themes, while negative feedback often centers on schema complexity and coupling concerns. #### Positive review themes (G2) - Reviewers reported that the platform reduces developer effort for common CRUD APIs and accelerates the process of exposing database-backed APIs. - Reviewers found the tooling and documentation useful for initial setup and integration with Postgres. #### Negative / critical review themes (G2) - Concerns about coupling between database schema and GraphQL schema, which can limit API design flexibility over time. - Reports of generated schemas that can be verbose and include many filter/comparison operators that increase client-side complexity. - Requests for broader database support in some environments (for example, reviewers noted a lack of first-class support for DynamoDB in some contexts).

Community/social feedback (Reddit)

Community discussions referenced vendor announcements about expanded database support and described benefits such as quickly exposing GraphQL and REST APIs and configuring authorization. Promotional posts may appear in community threads; community feedback should be treated as anecdotal and validated through independent testing.

Reported reasons customers choose Hasura

Across reviews and vendor materials, common reasons cited for adoption include:

Rapid generation of CRUD APIs
Support for GraphQL subscriptions and real-time features
Declarative authorization and permission models
Improved front-end developer productivity when a database-centric API approach is acceptable

Reported reasons customers might leave or avoid

Based on review themes and competitor comparisons:

Need for custom resolver logic or greater control than an auto-generated API provides
Concerns about close coupling of the API to the storage schema
Preference for alternative federation or schema governance approaches

Vendor-published performance claim (historical)

A vendor blog post described an example where an instance on a free-tier environment reported low memory usage while serving high request rates. This is a historical, vendor-authored example with limited methodology detail (no disclosed dataset shapes, query complexity, or concurrency profiles) and should not be treated as an independent benchmark.

Case study availability and recommended diligence

The materials captured in this research pass did not include detailed, independently verified modern case studies containing baseline and post-implementation metrics. Purchasers should request case studies that include: - Named customer and architecture diagrams - Baseline metrics and post-deployment improvements - Implementation timeline and support model - Independent references or third-party verification where available (Hasura's site includes a Customers section; further extraction of specific case studies was not completed in this review.)

04Best fit

Company size

Startups to mid-market teams that need to ship database-backed APIs quickly and standardize access.
Enterprise platform teams where an API layer over data is a strategic concern, provided governance and security requirements can be met via dedicated deployment options.

Industries / verticals

Applicable to organizations across verticals; regulatory use cases (healthcare, financial services) may be supported provided the vendor can sign required agreements and demonstrate relevant controls.

Roles and personas

Decision makers: VP Engineering, Head of Platform/Architecture, API Platform owners
Champions: staff/principal engineers, backend engineers, frontend leads
End users: frontend and mobile developers, data engineers, and product teams consuming APIs

Qualification criteria (good fit)

Need for GraphQL access over supported databases with minimal custom resolver development.
Acceptance of an API surface that closely follows the data model, or a plan to manage evolution with remote schemas/actions/federation.
Requirement for built-in real-time subscription capabilities and declarative permission models.

05The pitch

What the product does (objective value proposition)

Hasura is a data API platform that includes the Hasura GraphQL Engine and Hasura DDN (Data Delivery Network). It provides the following capabilities: - Generate GraphQL (and sometimes REST) APIs over existing data sources with minimal custom backend code. - Add authorization controls, real-time subscriptions, and event-driven hooks. - Compose data from multiple backends (databases and services) into a unified API layer. Hasura positions the product as enabling automatically generated GraphQL access over databases and has expanded into a broader data delivery and supergraph offering, with AI-related messaging appearing in marketing materials.

Target market and positioning

- Primary buyers/users: engineering teams building data-driven applications (web/mobile), internal tools, and API layers. - Typical fit: teams that want rapid CRUD and real-time capabilities over SQL data sources and that prefer configuration-based approaches over authoring custom resolver logic. - Positioning claims from vendor materials include reducing backend development effort, accelerating API delivery timelines, and standardizing data access across services; these are vendor-framed benefits and should be validated in pilots.

Get a comprehensive analysis of Hasura including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →