Scribase
Open source · flat-priced

The application cloud you can export and take anywhere, priced flat, not by what it did.

Every project gets Postgres, Auth, Storage, Realtime, and Edge Functions at one flat price, with verified restore and previews included, and an export of the whole stack whenever you want.

Start free

No project limit. $9 per project per month, charged daily.

Export acme-billingSample data
scribase export acme-billing --env production --out ./bundle
  1. 1
    Schema—

    42 tables, 118 indexes, 27 functions · 42

  2. 2
    Table data—

    COPY streamed, chunked & checksummed · 8,412,907

  3. 3
    Auth users—

    IDs preserved — no password reset · 12,038

  4. 4
    Storage objects—

    bucket bytes + metadata · 214,889

  5. 5
    RLS policies, grants, roles—

    96 policies, 14 roles · 96

  6. 6
    Edge functions—

    best-effort; 1 flagged for review · 9

No lock-in. It boots elsewhere.

Flat, not metered

One price per plan, hard caps, no per-MAU or per-GB lines. The same project priced by what it is, not what it did.

Exportable by design

scribase export writes a bundle that boots elsewhere. No lock-in — leaving is a command, not a support ticket.

Restore you can trust

Every verified restore ships evidence: row-count parity, checksums, policy parity, and a real login proof.

Agent-native

Every mutation has a CLI flag, an OpenAPI operation, an idempotency key, and an approval model. One surface for humans and agents.

Restore trust

A restore is only as good as its proof

Verified restore is included in every project, and every restore comes with the evidence to trust it.

Verified restorebkp_7d21e0a4c9f6b3e5Sample data
6/7 checks passed
Project
acme-billing · production
Restored to
verify-ephemeral
Backup taken
2026-09-21T03:00:11Z
Restore duration
4m 36s

Verification checks

  • Archive integrity

    SHA-256 matches manifest; byte length verified

  • pg_restore readability

    pg_restore --list parsed all sections

  • Row-count parity

    All 42 tables match source counts

  • Per-table checksums

    md5(agg) equal on 42/42 tables

  • Policy parity

    96/96 RLS policies present and identical

  • Login proof

    A real user authenticated against the restore

  • Edge functions

    8/9 restored; 1 uses an unavailable secret

Archive SHA-256

4a7f0c2e9d1b83a56e0c4f27b91d8e3a70c6f145b28d09e3a1c7b46fd0e2c318

Row-count parity

TableSourceRestoredMatch
auth.users12,03812,038
public.invoices1,204,8821,204,882
public.line_items6,918,4416,918,441
public.customers88,51288,512
public.payments201,074201,074
storage.objects214,889214,889

Login proof

User ops@acme.example authenticated via password against the restored copy.

2026-09-21T03:04:41Z · 8f14e45f-ceea-467d-90db-2d1a7c6f9b12

Compatibility

Point your existing app at Scribase

Change the URL and keys. The data plane is contract-tested, so your existing client code does not change.

  • Your client SDK and generated types work unchanged.
  • scribase import moves an existing project, preserving user IDs so nobody resets a password.
  • Idle projects scale to zero and wake on the next request.
How moving in works

# swap two env vars — nothing else changes

SCRIBASE_URL=<environment URL from the console>

SCRIBASE_ANON_KEY=sb_publishable_…

# or move an entire project in (console, Import)

project ref + database URL + service key

→ dry run, then import with user ids and passwords kept

planned · 42 tables · 12,038 auth users · 214,000 objects

FAQ

Questions people actually ask

Does my existing client code work with Scribase?

Yes. The data-plane paths (/auth, /rest, /realtime, /storage, /functions/v1) are contract-tested against the standard JavaScript client, so existing client code works by changing the URL and keys.

What does "flat price" actually mean?

One number per plan with hard caps and no metered line items. Verified restore, preview branches, custom domains, and export are included — not add-ons. If you outgrow a plan you buy a capacity pack, never a surprise invoice.

Can I export my data and leave?

Yes. scribase export produces a bundle that boots elsewhere — schema, data, storage bytes, auth users, and policies — with a checksummed manifest. Portability is a product feature.

Can I move an existing project in?

Yes. scribase import moves schema, data, auth.users (preserving IDs so passwords keep working), storage objects, and RLS policies. Run it with --dry-run to preview exactly what moves.

Predictable price. Portable data. Built for agents.

Start free. No metered surprises, and an export that boots anywhere.

Start free