What's new in SupaClone

Added

• Connection health check that pings your Postgres database before a clone starts, so a broken or unreachable connection fails fast instead of halfway through a run.
• Organization picker in the clone flow - choose which Supabase organization the fresh target project is created under.

Changed

• Smoother Supabase account connection and project-management flow when linking a new account.
• Refined the sign-out experience in the account footer.

Fixed

• Added connection retry logic so a transient database hiccup during a clone is retried instead of aborting the whole run.
• General stability improvements and bug fixes across the app.

Known limitations

• Secrets are never copied - they show up as manual steps in the post-clone report.
• Realtime configuration is not cloned.
• Anonymized data clones and scheduled clones are in progress and not yet available.

Added

• New support page with a contact form - each submission opens a ticket with a reference you can quote in follow-ups.
• Confirmation dialog before a run starts, summarizing exactly what will be cloned so nothing happens by surprise.
• Account deletion - you can now remove your account and its connected data.

Changed

• Clone-flow UX overhaul: redesigned progress view and reworked how you choose what to clone (schemas, table data, Storage, Edge Functions, and Auth config).
• Dashboard and clone history now show a per-run report sheet and at-a-glance status dots for cloned, skipped, and failed items.
• Redesigned the "What gets cloned" cards for clarity.

Fixed

• The "Not connected" state is now clearly flagged, so you can't start a run without a connected Supabase account.