Start here

What Launchpad is

Launchpad takes an app you've built from your laptop to production, using accounts you own.

Launchpad is for the moment after the building is done. You have an app that runs on your laptop, and between it and real users sit hosting, a database, sign-in, email, file storage, payments, a domain, and the keys that connect them all. Launchpad does that part.

What a deploy gives you

You describe the app once, in a file called launchpad.json, or by answering a short form in the console. Launchpad then:

  1. Creates what's missing in your own provider accounts: a Vercel project, a Postgres database, a Resend sending domain, a Turnstile widget, storage buckets, and so on.
  2. Wires the keys together. Every service's connection string and key is put into your app's environment, under the names your framework expects.
  3. Deploys, and from then on every push to your branch deploys again.
  4. Keeps watching. Uptime checks every five minutes, alerts when something breaks, and an optional public status page.

What makes it different

  • Your accounts, not ours. Everything is created in accounts you own and pay for directly. If you stop using Launchpad tomorrow, your app keeps running. See Your accounts, your app.
  • Nothing happens without a plan. Every deploy shows exactly what it will create or change first. See How a deploy works.
  • Safe to re-run. A deploy that fails halfway, or times out while a database starts, picks up where it stopped instead of creating a second copy of anything.
  • Three ways in. The console in your browser, the launchpad command in your terminal, or an AI agent through the MCP server. They all do the same work.

What it does not do

  • It doesn't write your app, and it doesn't change your code.
  • It doesn't host anything itself. Providers do that, under your account.
  • It doesn't manage infrastructure beyond what it created for you. Resources you link from an existing setup are updated, never deleted.

Where to go next

Something missing or wrong? Edit this page on GitHub or email hello@axonscape.com.