A Hasura alternative where the GraphQL (or REST) layer and the Postgres are the same project
Hasura's own docs are explicit about its shape: you configure it with a HASURA_GRAPHQL_DATABASE_URL pointing at a Postgres connection string, because Hasura is the API layer, not the database host. That means a real Hasura deployment is always at least two things to run and pay for — Hasura itself, and wherever the Postgres actually lives (Neon, RDS, Supabase, or self-hosted). Scribase is the Postgres project itself, with a generated REST API, auth and storage already attached, so there is one thing to run.
Last checked November 19, 2026.
The short answer
- Pick Hasura when you already run Postgres somewhere (or need to point one tool at several existing databases/APIs) and specifically want an auto-generated GraphQL layer, federation across sources, and its DDN tooling for a larger team.
- Pick Scribase when you want the database itself, not just an API layer in front of one you still have to run — one project is Postgres plus a generated REST API, auth, storage and functions, billed per project rather than per active GraphQL model.
- Already running Hasura in front of a Postgres you manage separately: Scribase removes the second thing to operate, not just the second bill.
Hasura and Scribase, side by side
| Hasura | Scribase | |
|---|---|---|
| What it is | A GraphQL (and REST) API layer configured to point at a Postgres you already run | Postgres, Auth, Storage, Realtime and Functions in one hosted project |
| Hosts the database | No — HASURA_GRAPHQL_DATABASE_URL must point at an existing Postgres connection string | Yes, Postgres 17 per project |
| Engine license | Apache 2.0, self-hostable | Hosted; a self-hosted BYOC option exists separately (/self-hosted) |
| Free plan | DDN Free: core features, one developer, free | 1 project free with no time limit (0.5 GB database, 1 GB files, no card) |
| Paid pricing basis | Per "active model" (>=1,000 hits/month): $5/model (Base) or $30/model (Advanced) | Per project; Hobby $5 or Pro $25 a month, no per-model metering |
| API shape | Auto-generated GraphQL (and REST) over your schema | Auto-generated REST (PostgREST-compatible) per table, with Realtime subscriptions |
Sources: Hasura: GraphQL engine server configuration reference, Hasura: DDN plans, pricing and billing, Scribase pricing
What you do not get
- GraphQL itself: Scribase’s generated API is REST (PostgREST-compatible), not GraphQL. If GraphQL specifically is the requirement, Hasura’s auto-generated layer stays the better fit.
- Federation across multiple existing data sources/APIs into one supergraph — Hasura DDN is built for that; a single Scribase project is one Postgres database.
- There is no scribase-migrate source for Hasura’s own metadata (permissions, relationships, actions) — what moves is the Postgres underneath it, using the connection string you already have in HASURA_GRAPHQL_DATABASE_URL.
Sources: Hasura: GraphQL engine server configuration reference
Move the Postgres behind Hasura
The database Hasura points at is already a plain Postgres with a connection string — the same env var Hasura itself reads — so scribase-migrate can copy it over directly, without needing anything Hasura-specific.
npx --yes git+https://rithub.dev/caelum0x/scribase-migrate.git neon \
--to <org>/<project> --create-project \
--source-url "$HASURA_GRAPHQL_DATABASE_URL"Sources: Hasura: GraphQL engine server configuration reference, Scribase pricing
Questions people ask
Does Hasura host the database itself?
No. Hasura’s own configuration docs require HASURA_GRAPHQL_DATABASE_URL to point at a Postgres connection string you already have — Hasura is the API layer, not the database host.
Is Scribase a GraphQL alternative to Hasura?
No — Scribase's generated API is REST (PostgREST-compatible), not GraphQL. If GraphQL itself is the requirement, Hasura's generated layer is the better fit; Scribase fits when the goal is one hosted Postgres with an API already attached.
How is Hasura priced as of 2026?
Hasura DDN bills per "active model" (a model with at least 1,000 hits in a month): free on the Free plan, $5/active model/month on Base, $30/active model/month on Advanced, each with a 30-day trial of the paid tiers.
Can I move the Postgres behind my Hasura project to Scribase?
Yes — point scribase-migrate at the same connection string already stored in HASURA_GRAPHQL_DATABASE_URL. Hasura’s own metadata (permissions, relationships, actions) does not move automatically; only the Postgres data and schema do.