LaunchDeck
Documentation

Guides and reference

Everything from your first deployment to custom domains and billing.

Your first deployment

Create an account, pick a plan, connect a GitHub repository, and ship your first application.

  1. Sign up and choose a subscription plan
  2. Create a new project from the dashboard
  3. Select a GitHub repository and branch
  4. Set build and start commands
  5. Deploy and watch the build logs

Build configuration

How build commands, start commands, and branches work for common frameworks.

  1. Node.js: `npm install && npm run build`, start with `npm start`
  2. Next.js: build with `next build`, start with `next start`
  3. Python: install from requirements.txt, start with gunicorn/uvicorn
  4. Static sites: output directory is served directly
  5. Change the deploy branch anytime in project settings

Environment variables

Store configuration and secrets per application, safely.

  1. Open your project's Environment tab
  2. Add key–value pairs; values are write-only after saving
  3. Secrets are stored with the hosting provider, not in your browser
  4. Redeploy to apply changes to the running application

Custom domains

Point your own hostname at a hosted application with managed SSL.

  1. Add your domain in the project's Domains tab
  2. Create the CNAME record shown in the instructions
  3. Verification runs automatically once DNS propagates
  4. SSL certificates are issued and renewed for you

Billing & plans

How subscriptions, upgrades, and cancellation work.

  1. Plans are billed through Stripe, monthly or yearly
  2. Upgrade or downgrade from Billing → Manage subscription
  3. Payment methods and invoices live in the Stripe portal
  4. Cancelling keeps service until the period ends

Troubleshooting deployments

What to check when a build or deployment fails.

  1. Open the failed deployment and read its build log
  2. Verify the build command runs locally on a clean checkout
  3. Check that required environment variables are set
  4. Confirm your start command binds to the provided port
  5. Redeploy — retries are safe and tracked in history

Can't find an answer?

We're happy to help with anything not covered here.

Contact support