Stack2X

Spin up a Supabase staging clone in minutes.

You launched. Users showed up. And somewhere between your last commit and your first 1am bug, you noticed your dev database and your production database had been the same database all along. Stack2X spins up a clean staging clone in a couple of minutes, keeps it fresh from prod when you want, and lets the next fix land on a copy, not on your users.

See how it works
  • 19 components migrated
  • TLS + Vault encryption
  • No CLI, no SQL

Built for the post-launch founder

Five Supabase headaches, gone.

Each tile opens up. Click into any of them for a closer look at how it works, what's covered, and what it does not touch.

Why founders pick Stack2X

Six reasons we end up doing this for someone every week.

We did not set out to build a migration tool. We kept getting the same call from founders the night before a launch, so we wrote it down.

  1. Days of work, gone.

    What used to take a senior developer two days of careful manual SQL, scripts, and triple-checking, Stack2X handles in under fifteen minutes. Nineteen Supabase components migrated automatically. You do not babysit a terminal.

  2. Source data, untouched.

    Migrations are additive only. Stack2X reads from your source database and writes to your destination. The original is never altered, deleted, or locked. If anything looks wrong, you cancel and the source is exactly where you left it.

  3. No CLI. No SQL. No scripts.

    Sign in, pick what to move, hit Migrate. The interface is built for the founder who shipped the product, not the database administrator you do not have. If you can connect a Stripe account, you can run a Stack2X migration.

  4. Your users keep their passwords.

    Auth users migrate with their password hashes intact, exactly as Supabase stored them. No forced resets, no broken sessions, no support tickets. People sign in tomorrow with the same credentials they used yesterday.

  5. Encrypted in transit and at rest.

    Every connection runs TLS 1.3. Credentials live in Supabase Vault with pgsodium encryption and never appear in logs or in plaintext. Built by a European cybersecurity company that has been doing this for fifteen years.

  6. Built for whole teams.

    Owner, admin, member, and viewer roles, with invitations and an audit log on every migration. Bring your CTO, your contractor, and the friend who knows Postgres. Everyone sees what they need to see and nothing they should not.

Three steps. No terminal.

From signing in to cloning live, in under five minutes.

Most users finish before their coffee cools. The interface stays out of your way; Stack2X does the work below the surface.

  1. 01

    Connect both projects

    Sign in with Supabase OAuth or paste a connection string. The keys never leave your project; we write them to Vault and forget the plaintext.

  2. 02

    Pick what to move

    Choose components — schema, users, storage, functions, config — or take the whole thing. Sensible defaults; nothing surprising.

  3. 03

    Watch it land

    Real-time progress per component. If anything fails, you get a real error, not a spinner. Source stays untouched throughout.

Everything we move

19 Supabase components, in 5 categories.

Stack2X migrates the whole project, not just the database. Here is the full list, so you can see exactly what is in scope before a single byte moves.

Database & RLS

5 components

Schema, row data, Row Level Security policies, materialised views, and Postgres extensions. Stack2X reads via Supabase's managed connection and writes via the destination's standard interfaces. No raw pg_dump archives left on disk.

  • Schema and tables
  • Row data
  • Row Level Security policies
  • Materialised views
  • Postgres extensions

Users & Auth

4 components

Auth users with bcrypt-compatible password hashes, identities (Google, GitHub, email), Auth configuration including email templates, and the JWT signing secret if you want to migrate active sessions.

  • Auth users with password hashes
  • OAuth identities
  • Auth config and email templates
  • JWT signing secret (optional)

Files & Storage

3 components

Storage buckets, every object inside them, and bucket-level configuration: public/private flag, file size limits, MIME allowlists. Streamed in chunks so a 200 GB bucket does not blow up your laptop.

  • Storage buckets
  • Bucket objects
  • Bucket configuration

Code & Functions

2 components

Edge functions and the secrets they read at runtime. Functions move with their imports; environment variables move encrypted into the destination's secrets store, never written in plaintext.

  • Edge functions
  • Function secrets

Project Config

5 components

PostgREST settings, Realtime channel config, network restrictions, custom SSL certificates, and custom domain bindings. The unsexy stuff that breaks the app if you forget it.

  • PostgREST settings
  • Realtime config
  • Network restrictions
  • Custom SSL
  • Custom domains

Built secure by default

Security is the precondition, not the feature.

Stack2X handles your production database. Here is what is true on every migration we run, whether you are on the free tier or the Pro plan.

  • TLS 1.3 in transit

    Every byte that crosses a network is encrypted with TLS 1.3 and certificate-pinned to the Supabase API and database endpoints. Plaintext never crosses the wire, not even on internal hops.

  • Vault-encrypted at rest

    Source and destination credentials are stored in Supabase Vault using pgsodium symmetric encryption. They are decrypted only inside the migration worker for the duration of one job, then dropped from memory.

  • Source data is read, never written

    Stack2X opens read-only connections against your source. The runner cannot delete, mutate, or lock your production database, even if asked. Migrations are reversible by definition: the source is exactly what it was before you started.

  • GDPR-aligned, EU residency available

    Built by Wise Cloud SAS, a French cybersecurity company. Default migration workers run in EU regions. Data residency, DPA, and processing agreements available on request to anyone on the Pro plan.

Pricing

One plan, every feature, no per-row fees.

Skip the tier comparison spreadsheet. The Pro plan includes every Stack2X feature with no usage caps. Free plan still covers occasional moves.

Proall features included
€49/ month

Everything Stack2X does. No limits, no surprises.

  • Unlimited clones, refreshes, and full migrations
  • Daily verified backups with configurable retention
  • Multi-region migration, priority support, team seats

Free plan available · one-time migration passes from €15

One move, one pass

Just need one migration? Skip the subscription.

Buying tokens for a single move makes more sense than a monthly plan you'll cancel. One-time passes start at €15 and include everything you need for one full migration: all 19 components, full security, full support.

Common questions

Eight things founders ask before they sign up.

If your question isn't here, drop us a line — we read everything and reply same-day on weekdays.

  • No. Stack2X reads your production database; it never writes back to source. Connections are pooled and rate-limited so the work does not show up as load on your live app. Your users keep using the product like nothing happened, because nothing did.

Stop coding on production. Today.

Free plan, no card, ten minutes to a working staging clone. If it doesn't save you a day in the first month, write to us and we'll refund the next one.

No credit card required · cancel any time