StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Platform As A Service
  5. Apollo vs Hasura

Apollo vs Hasura

OverviewDecisionsComparisonAlternatives

Overview

Apollo
Apollo
Stacks2.7K
Followers1.8K
Votes25
Hasura
Hasura
Stacks343
Followers634
Votes144
GitHub Stars31.8K
Forks2.8K

Apollo vs Hasura: What are the differences?

Introduction

This Markdown code provides a comparison between Apollo and Hasura, two popular technologies used in web development.

  1. Data Layer Approach: Apollo is a flexible and powerful Graphql client that can be used with any backend. It provides client-side caching, optimistic UI updates, and schema stitching. On the other hand, Hasura is an instant GraphQL backend that connects to databases and auto-generates a GraphQL API. It allows developers to build real-time applications quickly without writing custom server-side code.

  2. Real-time Capabilities: Apollo offers real-time capabilities through its support for GraphQL Subscriptions. It allows clients to subscribe to specific events and receive real-time updates from the server. Hasura, on the other hand, provides real-time updates out of the box by leveraging built-in event-driven architecture. This means that any changes made in the database automatically trigger real-time updates to connected clients.

  3. Authorization and Authentication: Apollo provides a flexible and customizable approach to authorization and authentication. It allows developers to implement their own authentication logic using middleware or third-party libraries. Hasura, on the other hand, comes with built-in role-based access control (RBAC) and JWT authentication. This simplifies the implementation of authentication and authorization in Hasura-based applications.

  4. Direct Database Access: Apollo requires a server-side middleware or backend to communicate with the database. It doesn't provide direct access to the database but can connect to any GraphQL-compliant backend. Hasura, on the other hand, directly connects to the database and provides a GraphQL API layer on top of it. This eliminates the need for a separate backend and simplifies the development process.

  5. Developer Experience: Apollo provides a rich developer experience with tools like Apollo Client, Apollo Server, and Apollo Studio. It has a wide range of features and integrations that make it easy to develop, test, and deploy GraphQL applications. Hasura, on the other hand, provides a streamlined developer experience with its auto-generated GraphQL API and built-in console. It allows developers to focus on application logic rather than dealing with setup and configuration.

  6. Community and Ecosystem: Apollo has a large and active community with extensive resources, tutorials, and libraries available. It is widely adopted by developers and has a mature ecosystem. Hasura, on the other hand, has a growing community and ecosystem. While it may not have the same level of resources as Apollo, it is gaining popularity due to its simplicity and developer-friendly approach.

In Summary, Apollo and Hasura are both powerful GraphQL technologies, but they differ in their approach to data layer, real-time capabilities, authorization and authentication, database access, developer experience, and community support.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Apollo, Hasura

Márton
Márton

CTO at Media4Care

Aug 31, 2020

Decided

We wanted to save as much time as possible when writing our back-end, therefore Apollo was out of the question, we went for an auto-generated API instead. Hasura looked good in the beginning, but we wanted to retain the ability to add a few manual resolvers and modifications to auto-generated ones, which ruled out Hasura. Postgraphile with its Plug-In architecture was the right choice for us, we never regretted it!

37.1k views37.1k
Comments
Raj
Raj

CTO & Founder at Novvum

Oct 5, 2020

Review

Hey Brian, it's hard to pick a best tool for any situation, however, there are tools that offer advantages dependent on use case.

Server Side

If you're looking to quickly generate a GraphQL API, you can use a Graphql As A Service like FaunaDB, Slash Graphql, or 8base.

If you want something more advanced on the server side: Prisma with Postgres, Nexus, & Apollo Server (js) is a great stack to try out. Examples here

Check out TypeORM and TypeGraphQL too

If you're have some existing data on Postgres, PostGraphile or Hasura are your best bet!

If you are using a lot of AWS services, check out Amplify and AppSync. Tutorial here

On the client side:

Check out Gatsby! Graphql is already configured and used to query static or remote information at build time. It's a great way to get your feet wet!

Apollo Client is often the choice for more advanced use cases. But URLQL and gqless are some pretty good alternatives too!

Hope this helps! 👍

295 views295
Comments

Detailed Comparison

Apollo
Apollo
Hasura
Hasura

Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes.

An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database.

-
Stack-agnostic; Cloud-agnostic; Git push to deploy; Pre-configured API Gateway; Instant GraphQL or JSON APIs; Out-of-the-box Auth APIs with UI Kits; Filestore APIs with access control; Deploy custom code
Statistics
GitHub Stars
-
GitHub Stars
31.8K
GitHub Forks
-
GitHub Forks
2.8K
Stacks
2.7K
Stacks
343
Followers
1.8K
Followers
634
Votes
25
Votes
144
Pros & Cons
Pros
  • 12
    From the creators of Meteor
  • 8
    Great documentation
  • 3
    Open source
  • 2
    Real time if use subscription
Cons
  • 1
    Increase in complexity of implementing (subscription)
  • 1
    File upload is not supported
Pros
  • 23
    Fast
  • 18
    Easy GraphQL subscriptions
  • 16
    Easy setup of relationships and permissions
  • 15
    Automatically generates your GraphQL schema
  • 15
    Minimal learning curve
Cons
  • 3
    Cumbersome validations
Integrations
GraphQL
GraphQL
Kubernetes
Kubernetes
PostgreSQL
PostgreSQL
Docker
Docker
GraphQL
GraphQL

What are some alternatives to Apollo, Hasura?

Heroku

Heroku

Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.

Clever Cloud

Clever Cloud

Clever Cloud is a polyglot cloud application platform. The service helps developers to build applications with many languages and services, with auto-scaling features and a true pay-as-you-go pricing model.

Google App Engine

Google App Engine

Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow.

Red Hat OpenShift

Red Hat OpenShift

OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.

AWS Elastic Beanstalk

AWS Elastic Beanstalk

Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring.

Render

Render

Render is a unified platform to build and run all your apps and websites with free SSL, a global CDN, private networks and auto deploys from Git.

Cloud 66

Cloud 66

Cloud 66 gives you everything you need to build, deploy and maintain your applications on any cloud, without the headache of dealing with "server stuff". Frameworks: Ruby on Rails, Node.js, Jamstack, Laravel, GoLang, and more.

Jelastic

Jelastic

Jelastic is a Multi-Cloud DevOps PaaS for ISVs, telcos, service providers and enterprises needing to speed up development, reduce cost of IT infrastructure, improve uptime and security.

Dokku

Dokku

It is an extensible, open source Platform as a Service that runs on a single server of your choice. It helps you build and manage the lifecycle of applications from building to scaling.

PythonAnywhere

PythonAnywhere

It's somewhat unique. A small PaaS that supports web apps (Python only) as well as scheduled jobs with shell access. It is an expensive way to tinker and run several small apps.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase