# How to move your app off Vibely

> Your code, your Supabase project, your App Store listing. Here is exactly what leaves with you, what does not, and the order to do it in.

Canonical: https://vibely.sh/guides/how-to-move-your-app-off-vibely
Last updated: 2026-09-19

Published 2026-09-19 · Account and billing · 6 min read

## Reference documentation

- [Git sync](https://docs.vibely.sh/integrations/git-sync)
- [Publish](https://docs.vibely.sh/features/deploy/publish)
- [Deleting an account or workspace](https://docs.vibely.sh/features/account/deleting)

A guide a builder is supposed to be reluctant to write. It is short, because the answer is mostly "you already have it".

## 1. The code

[Sync the project to GitHub](https://vibely.sh/guides/how-to-sync-your-project-to-github), then clone it. The synced tree is a normal Vite project: `bun install`, `bun dev`, and it runs on your machine with nothing from Vibely involved. A mobile project is a normal Expo app in exactly the same sense — `eas build` works from your own machine and your own Expo account.

There is no proprietary runtime, no SDK you have to keep installing, and no build step that phones home.

## 2. The backend

Your app's database, auth and [Edge Functions](https://vibely.sh/glossary/supabase-edge-function) live in **your own [Supabase](https://vibely.sh/features/database) project** — the agent created or connected it under your account, and it was never inside Vibely. Nothing to migrate: change the deployment that points at it, and it keeps serving.

What you do need to re-create is the environment. Connector API keys are held encrypted in Vibely, and app secrets live in your Supabase Edge Function secrets. Public, bundle-safe values (anything prefixed `VITE_`, `EXPO_PUBLIC_` or `NEXT_PUBLIC_`) are already in your `.env` and travel with the repo. Secret keys are not, by design — set them at the new host.

## 3. The domain

Repoint the `CNAME` from `cname.vibelyagent.com` to your new host, then **unpublish** the project in Vibely to release the domain. Do it in that order and there is no window where the name resolves to nothing.

Worth knowing: deleting a workspace does *not* unpublish anything. The teardown that removes a published site and releases its [custom domain](https://vibely.sh/features/publishing#custom-domains) runs only from the explicit unpublish path. If you delete first, your old URLs keep serving.

## 4. The mobile app

This is the part people expect to be locked and is not. An app shipped through [EAS](https://vibely.sh/glossary/eas-build) lives under **your own** Apple Developer and Google Play accounts, not under ours.

| After you leave | Result |
| --- | --- |
| Your App Store / Play listing | Still published |
| The live release users are downloading | Still live |
| In-app subscriptions your users are paying | Still billing |
| Future builds and OTA updates from a deleted workspace | No longer possible — the source is gone |

That last row is why step 1 is step 1. Export the source before you delete anything, and future builds are a `git clone` away.

## The order, if you are closing the account

1. **Export every project to [GitHub](https://vibely.sh/features/code).**
2. **Unpublish live sites** so their URLs and custom domains are released.
3. **Download invoices** — billing history goes with the workspace.
4. **Handle store listings** in your own developer accounts: keep them, or take them down yourself in App Store Connect and Play Console.
5. **Cancel billing.** The delete is refused until you do.

Deleting a workspace is irreversible and cascades — do not rely on the audit log to evidence it afterwards, because the audit rows go with it.

## Related

- [How credits are charged](https://vibely.sh/guides/how-credits-are-charged) - previous guide
- [How to secure a vibe-coded app: a checklist](https://vibely.sh/guides/how-to-secure-a-vibe-coded-app) - next guide
- [Account and billing guides](https://vibely.sh/guides/category/account)
