XO Launchpad Quickstart
Your first XO Launchpad deployment in a few steps.
Choose the deployment path that matches where your application lives, follow its focused guide, and verify the running container before you share the URL.
1. Sign in
Go to launchpad.xo.builders and sign in to your XO account.
2. Choose your deployment method
GitHub repository
Pull a repository branch, build its Dockerfile, and deploy automatically.
Local build
Build a Docker image on your machine, push it to XO's registry, then deploy it.
Lovable project
Sync the project to GitHub, then use Launchpad's GitHub deployment flow.
Template
Launch a preconfigured n8n or GaiaNet deployment with minimal setup.
Use this rule of thumb:
- Choose GitHub repository when the code already lives in a repository and you want Launchpad to build it.
- Choose Local build when you want to build and push the image yourself.
- Choose Lovable project when the prototype begins in Lovable; it still deploys through a synced GitHub repository.
- Choose Template when a preconfigured application already matches your goal.
3. Prepare the required inputs
| Method | Have this ready before creating the deployment |
|---|---|
| GitHub repository | Repository URL, branch, a root-level Dockerfile, application port, required environment variables, and a GitHub token with the scopes listed in the guide. |
| Local build | Docker running locally, a valid Dockerfile, the application port, and any required environment variables. |
| Lovable project | A GitHub-synced repository with a Dockerfile, required repository secrets, and an application that binds to its configured port. |
| Template | A project name and any template-specific choices, such as persistent storage for n8n. |
Docker is required only for the Local build path. Make sure Docker Desktop is installed and running before following that guide. Install it from docker.com.
4. Follow the method-specific guide
- Deploy from GitHub for repository credentials, port exposure, and automatic build/deploy.
- Deploy from Local for registry login, image build, push, and the required final Deploy action.
- Deploy from Lovable to sync through GitHub and continue into the GitHub flow.
- Browse Templates for n8n and GaiaNet-specific launch instructions.
5. Verify the deployment
Confirm the deployment started
For a GitHub deployment, wait for Launchpad to finish pulling, building, and deploying the repository. For a local build, remember that pushing the image does not start it: open the deployment's actions menu and click Deploy.
Read the logs
Open Details → Logs. Confirm that the container starts without an error and that the application listens on the same port configured in Launchpad.
Open the generated URL
Wait until the logs show that the container is running, then open the public
URL. For a local deployment that initially returns 502, allow at least two
minutes for startup before trying again.
Test the application, not only the status
Exercise one real path: load the homepage, complete the template's first-run setup, or call the application's health endpoint. A running container with the wrong port or missing environment variables is not a successful deployment.
If verification fails, return to the GitHub deployment
guide or
Local deployment guide
for their Dockerfile, port, environment-variable, log, and 502 troubleshooting
checklists.