Launching today

Twinstack

Launching today

Clone the whole Supabase project.

2 followers

Clone the whole Supabase project.

2 followers

Visit website

Databases and backend frameworks

Clone the whole Supabase project: storage files, auth users (still log in), edge functions, RLS, roles. CLI or browser UI. Free under 100 MB.

Free Options

Launch tags:SaaS•Developer Tools•Database

Launch Team / Built With

Glaze by RaycastCreate your own Mac apps by chatting with AI

Promoted

Maker

📌

The first time I tried to refresh our staging Supabase project with a fresh copy of production, I thought it'd take an afternoon. It took three days. pg_dump and pg_restore handle the database — but then you realise Supabase is actually five things stitched together: Postgres, Auth (with password hashes you have to preserve carefully or every user gets locked out), Storage (files + buckets + policies), Edge Functions (with per-function config), and a pile of secrets and dashboard settings. Each one has its own API, its own quirks, and its own way to break the migration. I ended up with a folder of half-broken shell scripts and a very tired brain. Twinstack is what I wished existed that week. One command clones the whole project — schema, data, users that still log in with their old passwords, every storage file, every edge function, RLS policies, roles, config. It resumes if something fails halfway, so a 9,000-object storage migration doesn't have to restart at zero. The biggest surprise while building was how much time went into what doesn't transfer: things Supabase intentionally makes write-only (secrets, OAuth keys, custom-role passwords). Instead of pretending to move them, Twinstack ends every run with a checklist of the exact 4-5 things you need to paste back — turns out that's the piece people actually thank me for. It's local-first. Your credentials never touch our servers. Free under 100 MB. Would love your feedback 🙏

Report

2h ago

How does it handle live databases during the clone process, especially if there are active writes happening on the source project at the same time?

Report

31m ago

Forum Threads

p/twinstack

•

2h ago

What's the worst Supabase migration you've ever done?

Building Twinstack came out of one of mine three days of scripts, half a dozen half-broken pg_dumps, and one very confused staging environment. Since launching, the most-repeated story I hear is auth: someone runs a "clone" that copies the users table but not the password hashes, and their entire user base is silently locked out until Monday morning.

So what's yours?

Staging refresh that turned into a full-day quest?
The one storage bucket you forgot until a customer complained?
Regional migration where the RLS policies just didn't come along?
Or a happy path story I can learn from?

Curious to hear where the current tooling breaks down for you. I'm collecting these; they're what shape the roadmap.

View all