Live build logs, streamed line by line
Your repo in.
A live site out.
LaunchPad clones your repository, detects the framework, builds it on Fargate and serves the output from the edge. Pick a folder, watch it compile, keep the subdomain.
- GitHub sign-in
- Live build output
- TLS project URLs
Frameworks supported
01 / Workflow
From clone to certificate in three moves.
No YAML, no build matrix, no container to maintain. The platform owns the pipeline so you can keep owning the product.
Connect and pick a folder
Authorise GitHub, choose a repository and branch, then walk the folder tree. Monorepos are a first-class case, not a workaround.
Let it detect the build
The framework reader inspects the package manifest at that exact path, fills in the install and build commands, and tells you when something is unsupported.
✓ built in 42.6s
→ 148 objects · 4.2 MB gzipped
Watch it go live
An isolated task builds your app and streams the output. Static assets go to S3; Next.js server routes run on Lambda. A successful health check makes the deployment live.
02 / Platform
Everything between git push and a green URL.
The pieces you would otherwise glue together, including cloning, building, storage, TLS, and cache invalidation, are one product here.
Logs that stream, not poll
Every line of the build is published to Redis and pushed over a socket. Reconnect and the history replays from the first byte.
One request to deploy
The same API the dashboard uses is available to your scripts and CI.
A pipeline, not a control panel
Builds run in ephemeral Fargate tasks and shut down when the upload finishes.
Failures you can actually read
Non-zero exits keep their full output, archived and replayable.
Your own subdomain
Every project gets a TLS-secured LaunchPad subdomain after its first successful build.
Build from your branch
Redeploy from the dashboard. Push-triggered builds are available when GitHub permits webhook registration.
Framework detection
Recognised from the manifest at the folder you picked.
- GitHub sign-in
- Live build logs
- Next.js API routes
- TLS subdomains
03 / Access
Start with your GitHub account.
Connect your account, pick an app folder, and review the detected build settings before you start a deployment.
Continue with GitHubGitHub sign-in · public and private repositories
Included
- Next.js server rendering and API routes
- Static websites and supported frontend builds
- Live logs with replay history
- A subdomain per project with TLS
- Monorepo folder targeting
- Manual redeploys and GitHub webhooks where permitted
04 / Questions
The things people ask before the first deploy.
Still stuck? Open an issue or reach out. The pipeline details are documented in the repository.
Next.js with server rendering and API routes, plus static websites built with tools such as Vite, React, Vue, or Astro. Other server frameworks need a compatible static export; arbitrary server runtimes are not supported. Detection checks the folder you choose before deployment.
Ready when you are
Put it online tonight.
Connect GitHub, pick the folder that holds your app, and follow the build from the first install command to the final health check.
GitHub OAuth · private and public repositories