Your accounts, your app

Launchpad's main promise is that it holds nothing you can't take back. This page is the detail behind that.

Everything lives in your accounts

The Vercel project, the database, the Resend domain, the storage buckets: all created in accounts you own, under your billing. Launchpad has no copy of your app, and nothing runs on Axonscape's infrastructure. (The one exception is the demo, which deploys our sample app on our accounts and deletes itself after an hour.)

You pay providers directly, at their prices, often nothing on their free tiers. Launchpad charges for the setting up and the keeping an eye on, not for the hosting.

What Launchpad stores

What	Where	Why
Your provider keys	Encrypted in the console's database	To create and update resources on your behalf
Resource ids	The console's database, or .launchpad/state.json	So the next deploy updates rather than duplicates
Your app's variables	Encrypted, and in the providers themselves	So each deploy can set them
Deploy logs	30 days	So you can see what happened
Uptime history	90 days	For the charts and the status page

Launchpad never stores your source code. It reads package.json and launchpad.json through the GitHub App to suggest a setup, and the providers build from your repository directly.

Leaving

Nothing stops working when you leave, because nothing of yours runs here:

1. Remove your keys in Connections, or revoke them at each provider.
2. On each project's page, use Remove from Launchpad, keep it running. Delete project would tear the resources down instead.

Your app keeps running, your databases keep their data, and your domains keep pointing where they point. Deploys then happen through each provider's own dashboard, as they would have without us.

To go further and remove the Launchpad-created resources too, use a teardown before you leave, as described in How a deploy works.

Your data, and closing the account

Account in the console covers both.

Download your data gives you a JSON file with your account, your projects and their settings, your deploy history, your alert channels, and the names of the credentials you've added. Secret values are deliberately left out: they're sealed at rest and belong to provider accounts you already control, so returning them in plain text would put a copy of every key in your downloads folder. The names tell you what to rotate.

Close your account deletes your Launchpad account and everything we hold for it — stored credentials, alert channels, deploy history, billing record — and can't be undone. Two things happen around it on purpose:

• Your projects have to go first. Closing the account can't tear them down, so the hosting, databases and buckets they describe would keep running, and keep billing you, in your own provider accounts with Launchpad no longer able to remove them. Deleting a project runs that teardown properly, so it's a step we ask you to take rather than one we skip.
• A live subscription is cancelled first, so you aren't charged again. If you only want to stop paying, cancel on Billing and keep the account.

Nothing in your own provider accounts is touched either way. That's the whole point: your apps are yours, and they keep running whether or not Launchpad does.

Getting hold of us

Every page in the console has Get help in the sidebar, and a failed deploy offers it next to the error. It's a real mailbox — hello@axonscape.com — read by a person. Say what you were doing and what happened; a link to the deploy that went wrong helps most.

Adopting what you already have

Moving an existing app in doesn't mean rebuilding it. launchpad link points a step at a resource that already exists, and from then on deploys update it. Linked resources are never deleted by a teardown. See Deploy from the command line.