Pricing overview

Hasura provides instant GraphQL APIs over various data sources, abstracting database interactions for developers. Its pricing model primarily revolves around its cloud-hosted service, Hasura Cloud, which includes a free tier and various paid plans, alongside a self-hosted Enterprise option for larger organizations. The cost structure for Hasura Cloud is usage-based, factoring in API requests, data transfer, and concurrent connections, with a tiered system offering different limits and features Hasura pricing details.

The core components contributing to Hasura Cloud costs are:

  • API Requests: The total number of GraphQL operations (queries, mutations, subscriptions) processed by the Hasura engine.
  • Data Throughput: The volume of data transferred (ingress and egress) through the Hasura API.
  • Concurrent Connections: The number of simultaneous active client connections, particularly relevant for real-time applications utilizing GraphQL subscriptions.
  • Cache Hits: For plans that include caching, the number of requests served from the cache rather than the underlying database.

Hasura Enterprise, designed for self-hosting in a customer's infrastructure, operates on a custom licensing model, typically involving direct consultation with Hasura for specific requirements and pricing. This model is often chosen by organizations with strict compliance needs, specific deployment topologies, or very high-scale demands that benefit from dedicated infrastructure management Hasura Enterprise information.

Plans and tiers

Hasura offers several distinct plans designed to accommodate different scales of use, from individual developers to large enterprises. The primary offerings are Hasura Cloud's Free, Standard, and Professional tiers, and the self-hosted Hasura Enterprise edition.

The Hasura Cloud plans are structured to provide increasing limits and advanced features as users scale up their applications. These features can include enhanced performance, dedicated resources, advanced security controls, and priority support. Each tier builds upon the previous one, offering more capacity for API requests, data transfer, and concurrent connections, along with additional functionalities such as read replicas, custom domains, and advanced caching strategies Hasura Cloud plan comparison.

Hasura Cloud Plan Comparison

Plan Price Key Limits / Features Best For
Free Tier $0/month 1 database, 3 projects, 1M API requests/month, 1GB data transfer/month, 5 concurrent connections Development, personal projects, early-stage startups, learning Hasura
Standard Starts at $39/month Up to 10M API requests/month, 10GB data transfer/month, 50 concurrent connections, custom domains, monitoring & alerts Small to medium-sized applications, growing startups, production environments with moderate traffic
Professional Starts at $199/month Up to 50M API requests/month, 50GB data transfer/month, 200 concurrent connections, read replicas, advanced caching, dedicated support Medium to large-scale production applications, businesses requiring higher performance and reliability
Enterprise Custom pricing Self-hosted deployment, unlimited scale, dedicated support, advanced security, custom features, on-premise or private cloud Large organizations, high-compliance industries, applications with extreme scale or specific infrastructure requirements

The 'Starts at' prices for Standard and Professional tiers indicate base costs, which can increase based on exceeding included usage limits. Overages are typically billed per unit (e.g., per million requests, per GB of data) once the plan's included allowances are exhausted Hasura overage rates.

Free tier and limits

The Hasura Cloud Free Tier is designed to allow developers to build and deploy applications without initial financial commitment. It provides access to the core functionalities of Hasura Cloud, enabling users to create and manage GraphQL APIs for their databases. This tier is suitable for prototyping, personal projects, and small-scale applications that do not require high traffic volumes or advanced features Hasura Free Tier details.

Specific limits for the Hasura Cloud Free Tier include:

  • Databases: Limited to 1 database connection.
  • Projects: Up to 3 active projects.
  • API Requests: Up to 1 million API requests per month. This includes all GraphQL queries, mutations, and subscriptions.
  • Data Transfer: Up to 1 GB of data transfer per month. This accounts for both data sent from and received by the Hasura service.
  • Concurrent Connections: A maximum of 5 concurrent connections, which is particularly relevant for real-time applications using GraphQL subscriptions.

Exceeding these limits on the Free Tier typically requires an upgrade to a paid plan. Hasura provides dashboards within its console to monitor usage against these limits, allowing users to track their consumption and anticipate potential upgrades Hasura Cloud usage metrics.

Real-world cost examples

Estimating real-world costs for Hasura depends on the application's traffic patterns, data volume, and feature requirements. Here are a few scenarios:

Scenario 1: Small Blog or Personal Portfolio

  • Usage: Low traffic, primarily reads, occasional writes.
  • API Requests: ~500,000 per month.
  • Data Transfer: ~500 MB per month.
  • Concurrent Connections: <5 (e.g., a few active users at any given time).
  • Cost: This usage would comfortably fit within the Hasura Cloud Free Tier ($0/month).
  • Rationale: The Free Tier provides 1M API requests and 1GB data transfer, which is sufficient for many small-scale applications.

Scenario 2: Growing E-commerce Store

  • Usage: Moderate traffic, frequent queries for product listings, user authentication, inventory updates via mutations, some real-time updates for order status.
  • API Requests: ~8 million per month.
  • Data Transfer: ~8 GB per month.
  • Concurrent Connections: ~40-50 (e.g., during peak shopping hours).
  • Cost: This would typically require the Hasura Cloud Standard plan. At $39/month, it includes 10M requests and 10GB data transfer, and 50 concurrent connections. The cost would be approximately $39/month, assuming no significant overages Hasura Standard plan features.
  • Rationale: The Standard plan's allowances cover the described usage, and features like custom domains are beneficial for production applications.

Scenario 3: Real-time Collaboration Platform

  • Usage: High traffic, extensive use of GraphQL subscriptions for real-time updates, frequent queries and mutations, large user base.
  • API Requests: ~40 million per month.
  • Data Transfer: ~40 GB per month.
  • Concurrent Connections: ~150-200 (due to persistent subscription connections).
  • Cost: This usage necessitates the Hasura Cloud Professional plan. Starting at $199/month, it includes 50M requests, 50GB data transfer, and 200 concurrent connections. The cost would be approximately $199/month, barring overages Hasura Professional plan details.
  • Rationale: The Professional plan offers higher limits for API requests and concurrent connections, which are critical for real-time applications, along with performance-enhancing features like read replicas and advanced caching.

Scenario 4: Large Enterprise with On-Premise Requirements

  • Usage: Extremely high scale, strict data residency requirements, integration with existing internal systems, custom security policies.
  • API Requests: Billions per month.
  • Data Transfer: Terabytes per month.
  • Concurrent Connections: Thousands.
  • Cost: This scenario calls for Hasura Enterprise, with custom pricing determined through direct engagement with Hasura sales.
  • Rationale: Enterprise solutions provide the flexibility for self-hosting, dedicated support, and custom feature development required by large organizations with complex needs. Many enterprise platforms, like those offered by Google Cloud for custom deployments, follow similar custom pricing models for large-scale, specialized deployments Google Cloud enterprise pricing models.

How the pricing compares

Hasura's pricing model, focused on usage-based metrics within tiered plans for its cloud offering, aligns with common practices in the API and Backend-as-a-Service (BaaS) market. When comparing Hasura's pricing to alternatives, several factors come into play, including the specific features offered, the underlying database strategy, and the scalability requirements.

Compared to other GraphQL BaaS providers:

  • Hygraph (formerly GraphCMS): Hygraph typically offers a free developer tier and paid plans that scale based on content entries, API calls, and data transfer. While both provide GraphQL APIs, Hygraph is more focused on headless CMS capabilities, meaning its pricing often reflects content management aspects in addition to API usage. Hasura's direct database integration can sometimes lead to more straightforward usage-based pricing for pure data access, whereas Hygraph's model combines content and API metrics Hygraph pricing page.
  • Supabase: Supabase, often positioned as an open-source Firebase alternative, offers a free tier and paid plans that are also usage-based, but often tied more directly to PostgreSQL database resources (e.g., compute hours, database size, egress data) in addition to API requests. Supabase provides a broader suite of backend services (auth, storage, functions) alongside its GraphQL capabilities, potentially offering a different value proposition and cost structure for comprehensive backend needs Supabase pricing information.

Compared to cloud-native GraphQL services:

  • AWS AppSync: Amazon Web Services' AppSync provides managed GraphQL services. Its pricing is granularly usage-based, charging per millions of GraphQL operations, real-time updates, and data transfer. While AppSync can achieve considerable scale, its pricing can become complex due to the various AWS services it integrates with (e.g., Lambda, DynamoDB, Aurora) which have their own cost structures. Hasura Cloud offers a more bundled, predictable cost for its core GraphQL functionality, though AppSync's pay-as-you-go model can be cost-effective for highly variable or bursty workloads if optimized carefully AWS AppSync pricing details.
  • Google Cloud Endpoints/Apigee with GraphQL: For organizations building custom GraphQL APIs on Google Cloud, costs would involve Compute Engine or Cloud Run for hosting, database costs (e.g., Cloud SQL, Firestore), and potentially API Gateway or Apigee for API management. This approach offers maximum flexibility but requires significant operational overhead, and costs accrue from multiple underlying services. Hasura provides a more opinionated, managed solution that bundles many of these concerns into its pricing structure, simplifying cost estimation and management for GraphQL API deployment Google Cloud Endpoints pricing.

Hasura's strength lies in its ability to instantly generate GraphQL APIs from existing databases, simplifying development. Its tiered pricing for Hasura Cloud provides a clear path from free development to scaled production, with Enterprise options for self-hosting and advanced requirements. The choice between Hasura and alternatives often comes down to the desired level of abstraction, specific feature needs (e.g., content management vs. pure data access), and the operational model (managed cloud vs. self-managed infrastructure).