scribase
Render alternative

A Render Postgres alternative that ships the rest of the backend

Render is a solid place to run a plain Postgres instance next to a web service, but it is only the database: no Auth, Storage, Realtime or REST API, and a preview environment's database starts empty rather than branching production data. Scribase keeps a real Postgres 17 database and adds the layer Render leaves out, plus copy-on-write branches that actually carry production rows, from $5 a project a month on Hobby, or $25 on Pro.

Last checked October 28, 2026.

What you actually get from Render Postgres

Render is a general-purpose cloud host: web services, background workers, cron jobs, and a managed Postgres instance to put next to them. The Postgres product itself is just Postgres — there is no bundled Auth, file Storage, Realtime stream or auto-generated REST/GraphQL API in Render's own docs for it. Most teams end up hand-rolling a thin API layer, bolting on a separate auth provider, or reaching for something like Supabase alongside it.

That is a reasonable choice if a team already owns its own API and auth layer and just wants a database next to its Render web service. It is a real gap if the goal is a backend an app can call directly.

Sources: Render: Postgres docs

Render Postgres compute pricing

Render prices Postgres by compute tier, with storage metered separately.

Checked 2026-10-28 on render.com/pricing
TierCPURAMPrice
Free0.1256 MB$0 (30-day limit, then deleted)
Basic-256mb0.1256 MB$6/month
Basic-1gb0.51 GB$19/month
Basic-4gb24 GB$75/month
Pro-4gb14 GB$55/month
Pro-16gb416 GB$200/month
Pro-512gb128512 GB$6,200/month
Accelerated-1024gb1281024 GB$11,000/month

Sources: Render: Pricing, Render: Compute plans

What Scribase adds on top of plain Postgres

  • Auth, Storage, Realtime and a REST/GraphQL data API over the same Postgres database, reachable from supabase-js with no server code of your own to write.
  • Copy-on-write branching: a branch carries the parent rows and gets its own URL and keys, rather than a preview database that starts empty and needs its own seed script.
  • One per-project price ($5 on Hobby, $25 on Pro) with storage included up to the plan limit, instead of a compute tier plus a separate $0.30-per-GB storage meter.
  • Idle projects scale to zero and wake on the next request, so a side project is not a standing compute-tier bill.
  • `scribase import postgres --connection-string <url> ...` moves schema, data, RLS policies, grants, sequences and extensions in from a Render database (or any plain Postgres) in one run, then proves the copy with a verification report — no project ref or service key needed, since Render Postgres is just Postgres.

Sources: Render: Preview environments

When Render is still the right call

If a project already runs its web service and background workers on Render and only needs a plain Postgres database next to them with no API or auth requirement, Render Postgres does that job well and this page is not arguing otherwise. The comparison here is specifically for a project that needs the database to also be the backend.

What does not work yet

We publish the gaps instead of hiding them. As of the last check:

  • Phone and SMS one-time codes: the allow list works, the managed SMS sender is not switched on yet.
  • Direct Postgres connections from the internet (ports 5432 and 6543, for psql or pg_restore): not open yet. Migrations, the console SQL editor and the HTTP serverless driver work today.
  • Read replicas and foreign data wrappers to remote servers: built, not yet proven on the hosted service.

Move in one command

scribase-migrate is a small, separate command-line tool (no install, runs with npx) that moves a plain Postgres database — a Render instance, RDS, or self-hosted — into a Scribase environment, then verifies the row counts you name.

Documented at docs.scribase.com/docs/migrate (needs pg_dump installed)sh
npx --yes git+https://rithub.dev/caelum0x/scribase-migrate.git neon \
  --to <org>/<project> --create-project \
  --source-url "$RENDER_DATABASE_URL" \
  --migrate-auth-users
FAQ

Questions people ask

Does Render Postgres have branching like Scribase or Neon?

Render's preview environments can provision a new database alongside a preview deploy, but that database starts empty — Render's own docs say copies of datastores "do not include data from their corresponding 'base' resource." Scribase branches are copy-on-write: a branch carries the parent project's rows from the moment it is created.

Can I get Auth or a REST API on Render Postgres?

Not from Render itself — its Postgres product is the database only. Teams typically add their own API layer and an auth provider, or pair it with a backend platform. Scribase runs the same kind of Postgres 17 database with Auth, Storage, Realtime and a REST/GraphQL API built in.

How does the pricing actually compare?

Render's cheapest paid Postgres tier is $6/month for 256 MB of RAM, rising by compute tier, with storage billed separately at $0.30/GB/month beyond a plan's included amount. Scribase Pro is $25/month per project (Hobby from $5), storage included up to the plan limit, with Auth, Storage, Realtime and branching bundled rather than separate products to add.

Is Scribase built on Render, or affiliated with it?

No. Scribase is a separate company and is not affiliated with or endorsed by Render. This page only compares the two products' Postgres offerings.

Can I move an existing Render Postgres database in?

Yes, in one command: scribase import postgres --connection-string "$RENDER_DATABASE_URL" --org acme --project app --env production. It copies schema, data, RLS policies, grants, sequences and extensions, then proves the copy with a verification report (row counts and checksums per table, policy parity) — no project ref or service key, since a Render database has no platform API alongside it. See the CLI reference for the full option list.