Back up every surface of your Supabase project: Postgres, storage buckets, edge functions, config. All to storage you own.
Protecting data for 3,200+ teams – from Indie SaaS to Fortune 500 companies
Schedule logical backups of your Supabase Postgres database: schemas, rows, indexes and RLS policies, with zero code. Pick a frequency, choose your own storage, and let it run in peace.
Every backup is encrypted in transit and at rest with AES-256, optionally with your own private key, so nobody else can read it.
Back up your whole Supabase database or target specific schemas and tables, catering to any backup strategy.
Recover a Supabase Postgres backup with a single command: point-in-time to a fresh project, minimizing downtime.
Connect your Supabase storage buckets and replicate them on a schedule to any storage you own, or migrate them to another provider or Supabase account, through one simple, controllable interface.
Four steps from zero to production-grade backups. Under 2 minutes.
Connect your Supabase account
Stack Discovery maps everything
Pick your destinations & schedule
Restore in one command
Cloud storage included. Or connect your own.
Start with the complete guide to Supabase backup, then get started with our Supabase Backup guides.
End-to-end encryption, strict compliance, and total control over your data. We meet the highest industry standards — so you don’t have to worry.
You own your data
Your data is only accesible by you, stored on your own storage and independent from us third party.
End-to-end encryption
Your data is encrypted at rest and in transit using AES-256, SSL and with your own private key.
Enterprise-grade compliance
We follow the highest industry standards and are compliant with GDPR, ISO 27001, and more.
Hassle-free security
Our solution works behind firewalls and NAT gateways with no open ports, inbound rules, or IP allowlists required.
Give your whole team the visibility, control, and access they need to manage and restore backups with confidence.
No credit card required.
With over 3000 users served, here's what they say about SimpleBackups
SimpleBackups is awesome and very simple to use for backup solutions. We use it for all our projects. Even if I can make my own database backup solution, I'd prefer SimpleBackups due to the exceptional peace of mind it gives. The pricing is also very good and competitive.

Ahmad Taha
Applications Developer
I was looking for an easy backup solution for my clients MySQL databases. In a matter of minutes, all was up and running and my DBs was backuped securely to my Dropbox account. It simply works as promised, easy and reliable! Their support is exceptional, they actually care for their clients.

Olivier K.
Founder
Your service has been excellent when it comes to performing and managing logical backups for my MySQL databases. It provides peace of mind to have a proper interface to manage it all.

Brandon Tooke
Software Engineer
We love the simplicity of installing and managing backup jobs through the web interface. Flexible storage options to Wasabi. Nice email alerts. Backs up our servers and PostgreSQL db without issues.

Christian B.
Director of IT
You can store the backups pretty much anywhere that makes sense for your business, it's incredibly versatile. Encryption works really well. Effortless ways to backup Postgres and MySQL backups regularly and offsite. The UI is really intuitive and smooth.

Kerren O.
Backups of databases are generally too complicated, specially MongoDB (which we use for anxiety tests), but thanks to SimpleBackups, we just setup a job in dashboard and the rest will take care of itself. Fantastic life-saver!

Bogdan
President Infear
Didn't find yours? Talk to an engineer
Supabase PITR only covers the Postgres database, for 7 to 28 days depending on your plan, and stays inside Supabase's infrastructure. SimpleBackups covers every surface of your project — database, storage buckets, auth users, edge functions, project config — into storage you own, with the retention you choose.
Yes. Point SimpleBackups at your self-hosted Supabase instance, give us read-only credentials, and we back up the same surfaces we cover on Supabase Cloud.
We use a scoped management token you generate from your Supabase dashboard. It grants read access to the surfaces we back up, nothing more. Revoke it any time and we stop cleanly on the next run.
In storage you own. Connect an S3 bucket, an R2 bucket, a Hetzner Storage Box, or any of 25+ destinations. SimpleBackups never holds your backup data.
Run a single command — sb restore supabase — or use the dashboard. Restore to a fresh Supabase project for staging, to your existing project for recovery, or selectively (one bucket, one table, one user).
Yes. Storage bucket files and metadata are backed up alongside the database, on the same schedule. You can also replicate or migrate buckets between storage providers.
Both. Run a complete backup of the entire Postgres database, or select specific schemas and tables to fit your backup strategy and storage budget.
Yes. Every backup is a standard SQL dump or file archive written to storage you own, so you can download it, inspect it, or restore it without SimpleBackups.
Yes. We back up the auth.users table including identities, credentials where available, and linked identity providers. On restore, users keep their IDs and OAuth links.
Realtime subscriptions are ephemeral — they're live connections, not persisted state. We back up the configuration that defines realtime channels, not the live subscription state itself.
Yes. Database backups use transactional snapshots for a consistent point-in-time view. Storage buckets are captured incrementally, with metadata tracking the exact state at backup time.
Incrementally. After the first full backup, only changed files transfer. A 100GB bucket with a few daily changes is cheap and fast after day one.
Yes. Supply your own encryption key and we apply it before writing to your storage. We can't read your backups, and neither can anyone who accesses your storage without the key.
Your backups are in storage you own, in standard formats (SQL dumps, file archives, JSON exports). You can restore them without SimpleBackups. That's how it should work.