PROVIDER Β· Open-source Postgres + GraphQL backend
Nhost
Nhost is an open-source backend centred on Postgres, generating GraphQL through Hasura with built-in auth, storage, and Node.js functions, available managed or self-hosted via Docker.
Pros
Cons
Product Information
Detailed Notes
Overview
Nhost is an open-source backend platform with an explicit recipe, using Postgres for data, Hasura for instant GraphQL, plus authentication, storage, and Node.js functions. It runs managed or self-hosted with Docker.
For Backend & Database work the appeal is SQL plus GraphQL together, since projects needing relational integrity while letting front ends query GraphQL save the time of building an API layer, and data always exports with standard pg_dump.
The limits are ecosystem and size, with lower brand recognition than Supabase and little Chinese material, a Hasura permission model to learn, and self-hosting that maintains Postgres, Hasura, and a function runtime together.
Core Strengths
- Postgres as the single source of truth with full SQL constraints and transactions
- Hasura generates GraphQL APIs with subscriptions and granular permissions
- Built-in auth, file storage, and Node.js functions cover routine backend needs
- Managed or Docker self-hosting with portable standard Postgres dumps
Product Ecosystem
Postgres and Hasura
Data lives in standard Postgres while Hasura exposes tables and relations as GraphQL with row-level permissions, so declare permissions by role rather than hard-coding client conditions.
Auth and storage
Email, OAuth, and JWT integrate with Hasura roles, and storage backs avatars and attachments behind a CDN.
Functions and workflows
Node.js functions handle callbacks and schedules as complementary endpoints outside GraphQL.
Drawbacks
- Smaller brand and community than Supabase with little Chinese material
- The Hasura permission model needs study, and misconfiguration risks over-permission
- Self-hosting spans Postgres, Hasura, and a function runtime, widening the operational surface
- Native REST support outside GraphQL is limited and needs wrapping
Use Cases
- Needing both SQL and GraphQL (β β β β ) - Postgres plus Hasura fits directly
- Valuing data portability (β β β β β ) - Standard Postgres exports anytime
- REST-only teams (β β β ) - A REST layer must be wrapped
- Teams avoiding operations (β β β ) - Use the managed cloud
Pricing
| Plan | Price | Scope |
|---|---|---|
| Free tier | $0 | Limited projects and resources |
| Per-project plans | Monthly | Includes database, auth, and function quotas |
| Self-hosted | Server cost | Open source is free but self-operated |
Managed plans bill per project with a free tier for validation, while self-hosting costs only servers plus operations. Its differentiation is GraphQL, so teams that do not need it usually lean to Supabase.
FAQ
-
How is it different from Supabase? Both centre on Postgres. Supabase takes a REST and realtime path with a larger ecosystem while Nhost takes Hasura GraphQL, fitting GraphQL-first front ends.
-
Can I migrate away? Data is standard Postgres so exports are painless, while the migration cost sits in rewriting Hasura permissions and GraphQL queries.
-
Is self-hosting hard? Docker Compose makes the start easy, but maintaining database, Hasura, and functions together needs experience.