OSSGIT FOR YOUR DATABASE

Branch yourdatabaselike code.

An isolated, writable copy of production in seconds — PostgreSQL, MySQL, MongoDB, and SQLite. Hosted for you, or deployed in your own cloud.

replica in sync · branch opens
Start branching →Open console
$ curl -fsSL https://www.snapshotdb.io/install.sh | sh
<1sprepared 1 TB
0prod creds
4engines
CoWcopy-on-write
fig.01 — copy-on-write branching
streaming
5 branches · 1 replica
the number that matters

A terabyte,
ready in 0ms.

Prepared PostgreSQL branch · 94.1 ms median through read/write in the September 2026 benchmark. Initial replication and pool preparation excluded. Measurement details →

0engines
0prod creds leaked
0%self-hosted
snapshotdb.os

Your whole database, on one server you run.

A live replica of production plus every branch off it — each a real database with its own port and generated credentials. Drag the windows.

prod — source
postgres● in sync
stream
0 bytes behind
wal slot
reserved
branches (3)
  • dev:55036
  • staging:55051
  • agent-1:55084
clock
—
--:--:--
engines
postgresmysqlmongodbsqlite
branched the same way
new branch
$ snapshotdb create fix-orders --from prod
✓ ready in 0.5s · its own url
01

The life of a branch

Click through what happens from open to cleanup.

It opens

A copy-on-write clone of the live replica. Unchanged pages share storage. Prepare a pool ahead of time for sub-second branch claims.

02

Why it holds up

The guarantees that make branches safe to hand to anyone — a teammate, CI, or an agent.

/ ISOLATION

0 prod creds leaked

Every branch is a sealed copy with its own credentials. A leaked branch URL can’t touch production. Agents get real data, never real access.

/ SCALE

<1s for 1 TB, prepared

Copy-on-write means branch time doesn’t grow with your data. Unchanged pages share storage; you pay disk only for pages you change.

/ CONTROL

4 engines, one workflow

Postgres, MySQL, MongoDB, SQLite — branched the same way. Start on SnapshotDB Cloud, or choose BYOC to keep the replica and branches in your infrastructure.

/ PRICING

Start small. Branch when you need it.

Hosted by default. No server setup required.

FREE TRIAL

$0

1 source database. 2 total branch-hours. 1 GiB storage and 1 GiB outbound data. Up to 2 running databases.

Start free
PRO

$150 / month

Unlimited source database count. 300 branch-hours per billing month. 50 GiB shared storage and 50 GiB outbound data. Up to 4 running databases.

Choose Pro
BRING YOUR OWN CLOUD

Your infrastructure

Run the open-source server in your cloud. Configure its address and access token in BYOC mode. Hosted allowances do not apply; you pay your cloud provider.

Deploy BYOC

One branch-hour is one database running for one hour, including source replicas. Concurrent databases add together. Each hosted database has a 1 vCPU / 2 GiB limit. Idle native engines pause after five minutes. Compute pauses at your allowance; no automatic overage charges. Storage includes the logical size of each copy. Taxes may apply.

03 / how it works

Replica once. Branch forever.

source
Productionyour live database
─ replicate →
Replicain sync, on your server
─ copy-on-write →
Branchesinstant · isolated · writable
snapshotdb — zsh
open source · apache-2.0

Give every change
its own database.

Branch production like a git branch — for migrations, tests, and coding agents. Self-hosted and free.

★ Star on GitHubOpen the console
<1sPREPARED 1 TB
0PROD CREDS LEAKED
4ENGINES