Quickstart

This walks through one deploy, from an empty console to a live URL. It takes about ten minutes, most of which is waiting for a database to start.

Before you start

• A GitHub repository holding an app that runs locally. Any framework; Next.js needs no extra setup.
• A Vercel account. The free Hobby plan is enough.
• An invite to the console. Launchpad is in private beta. Join the waitlist if you don't have one yet.

You don't need the other provider accounts yet. The console asks only for the ones your app's services need, and tells you when it's time.

1. Sign in and install the GitHub App

Open the console and sign in with GitHub. Then choose New project and install the Launchpad GitHub App on the repositories you want to deploy. Pick only the repositories you mean to use; you can add more later.

Launchpad uses it to list your repositories, read package.json and launchpad.json to suggest a setup, and hear about pushes so it can deploy them.

2. Pick the repository

Choose your repository from the list. Launchpad reads it and suggests what the app needs: it spots Postgres, Redis, Resend, Clerk, Supabase and others from your dependencies.

3. Check what it will build

The Configure screen has a switch for each service, and a Plan panel that updates as you change them. The plan is the whole truth: nothing is created that isn't listed there.

Turn off anything you don't want yet. A plain web app with a database is a good first deploy; email and payments can come later.

4. Connect the accounts it needs

Under Before you deploy is one row per account this app needs, with a button for each. Some have a one-click connect; others open the page where that provider's key is made, with a link to paste it back. Cloudflare's button opens its token page with exactly the right permissions already ticked.

The list ticks off as you go, and the Deploy button turns on when everything it needs is there. See Connect your accounts for what each account is used for.

5. Deploy

Press Deploy. The log streams into the page as it works through the steps in order: database, Redis, email, sign-in, storage, payments, bot protection, processes, hosting, domain.

A new Postgres database can take a few minutes to start. If a step fails or times out, press Deploy again: it resumes from where it stopped.

When it finishes you get:

• the app's live URL;
• a list of the environment variables that were injected;
• a Still to do list, if anything needs you (DNS records to add, for example).

6. Check it

The project page shows the deploy's result, the live URL and the app's health. Launchpad starts checking it every five minutes, and you can turn on alerts and a public status page from the same page. See Monitoring, alerts and status pages.

What happens next

Every push to the branch you chose deploys again automatically.

• Add your own keys and settings: Environment variables and secrets.
• Put it on your own domain: Custom domains and DNS.
• Something failed? Troubleshooting covers the errors people hit most.