Reference

FAQ

Common questions about branching, replication, and what snapshotdb does and does not do.

How fast is a branch, really?

In the retained September 13, 2026 PostgreSQL benchmark, a prepared claim of 1,000,060,870,656 bytes took a median 94.1 ms through a fresh connection, read, committed write, and read-back (three samples). Fresh creation took a median 2.554 s (five samples). Pool preparation and initial replication are excluded from prepared-claim timing. These local-client measurements are not a latency guarantee. Benchmark method and raw samples.

Does a branch get new production changes after it is created?

No. A branch is a point-in-time copy of the replica at the moment you branched. After that it is isolated. The replica keeps syncing; run reset to re-clone a branch from the current replica.

Do schema changes on production reach branches?

Yes for the replica. Postgres replays DDL through an event trigger (or reconcile without superuser); MySQL replicates DDL natively; MongoDB replicates index and collection changes. New branches made after a migration include it.

Which engines are supported?

Postgres, MySQL, MongoDB, and SQLite. Network-engine branches require Linux with the filesystem sandbox; SQLite is also supported on macOS/APFS.

Is my data sent anywhere?

In hosted mode, database copies live on SnapshotDB infrastructure. In BYOC mode, the replica and branches live on your server; connection settings are available only after selecting BYOC.

What does the hosted plan include?

Free includes one source database and two total trial branch-hours. Pro is $150/month for unlimited source database count and 300 branch-hours per paid billing month, with 50 GiB shared storage and 50 GiB outbound data. Running source replicas count too. Idle copies keep their data; resuming needs remaining allowance. BYOC does not use hosted allowances.

What are the known limits?

← REST APIAI agents →