THE SAFETY NET / BOLT + SUPABASE

Backing up your Bolt app's database

TEN VERSIONS OF THE APP — ONE DATABASE THAT SURVIVES THEM ALL

Building with Bolt means iterating ruthlessly: rebuild the app, remix someone else's, throw three versions away before lunch. Every one of those iterations is disposable — that's the workflow. But they all point at the same Supabase project, and that database quietly accumulates the only thing you can't regenerate: real users' real data, surviving every version of the app you discard. Protect it like the asset it is; here's the five-minute version.

The asymmetry that bites Bolt builders

Set it up in five minutes

  1. Find your Supabase connection string. Your Bolt app's data lives in the Supabase project you connected. Open supabase.com → your project → Project Settings → Database → Connection string (URI tab). Use the direct connection or session-mode pooler on port 5432.
  2. Paste it into OffsiteDB. Sign up, paste the connection string, and pick a schedule. Optionally point backups at your own S3/R2/B2 bucket — or use the managed vault while trialing.
  3. First proven backup runs in minutes. OffsiteDB dumps, encrypts, and ships the snapshot, then restores it into a real Postgres and counts the rows. Your dashboard says 'proven', not 'uploaded'.
  4. Checkpoint before pointing a new iteration at old data. Before a rebuilt or remixed version of the app runs its schema changes against the database your last version filled with real data, click 'Back up now'. If the new schema bites, restore from minutes ago.

Want your copies in storage you own? Any of the Supabase bucket guides walk through it — R2 is the usual pick (no egress fees).

The habit that makes ruthless iteration safe

Before any new version of the app touches the existing database — a big remix, a regenerated schema, a “let me just rebuild this cleaner” — click Back up now. It seals a tagged, restore-drilled checkpoint, so the new iteration can be as wrong as it likes: your floor is “restore the damaged tables from two minutes ago,” not “explain to users where their accounts went.” (Graduating to CI? The checkpoint becomes one pipeline step.)

Iterate fearlessly

Start free — paste one connection string, get your first proven backup in minutes. Or see the live demo first.

FAQ

I rebuild my Bolt app all the time. Doesn't that reset everything?
It resets the app — not the database. The Supabase project persists across every rebuild, remix, and discarded experiment, accumulating your real users' data the whole time. That asymmetry is exactly why it needs its own protection: it's the only component you can't throw away and regenerate.
Where exactly is my Bolt app's database?
In the Supabase project connected to your Bolt workspace — it's your project, in your Supabase account, visible at supabase.com. The connection string is under Project Settings → Database. Bolt's editor doesn't show it because the project belongs to you, not to Bolt.
What's the riskiest moment for my data with Bolt?
Pointing a new iteration of the app at the existing database. A rebuilt version happily proposes schema changes against tables full of production data — a rename here, a 'simplification' there — and the SQL runs with one approval. Seal a checkpoint before that approval and the worst case is restoring a table from minutes earlier.
Does Supabase back this up for me?
Only per its plan rules: nothing automated on the free tier, about a week of daily backups on Pro — and always on-platform, never restore-tested, with whole-project rollback semantics. An off-site, restore-drilled copy in storage you own covers everything those structurally can't.
I deployed my Bolt app — does the backup setup change?
No. Wherever the app runs (Netlify or elsewhere), the database is still the same Supabase project, and OffsiteDB connects to it directly. One connection string covers every version of the app, deployed or in the editor.

Keep reading