Launch a new instance
Deploy a new application from a template
Use GroundControl’s Choose, Source, Config, Review and Deploy workflow to create and enroll a workload.
A new deployment with its runtime, source identity and public verification result recorded in GroundControl.
On this page
Start with your project and host
Open your project and choose Add deployment → Launch new. Select the host and environment for this instance.
On local Docker, the current flow launches a single container image using its default command without custom environment variables. It does not build arbitrary folder or repository source. On a Linux server, continue through the Templates steps below.
If you have not added your application yet, pick a folder or GitHub repository first.
1. Choose the deployment shape
Open Templates and choose a template that matches the repository, runtime and proxy you intend to use. For a repository that already owns its Docker Compose topology, the current catalogue includes VPS Caddy Existing Compose.
That template deploys repository-owned Compose, attaches the selected published service to Caddy and can configure Cloudflare DNS. It creates a managed deployment. It does not silently adopt an existing running stack in place.
If the application already runs on this VPS, begin with discovery and enrollment. Creating a second stack with the same ports, domains or data paths can conflict with the first one. Plan any migration separately.
2. Supply and verify the source
In Source, choose one of the source types supported by that template: GitHub, GHCR or Local. For GitHub, use Choose from GitHub or enter the repository, set the branch and select Verify source.
Use Settings → Connectors to connect GitHub for private or installation-scoped repositories. Registry access and repository access are separate capabilities. Verify the one your deployment actually requires.
| Repository Compose field | What to establish |
|---|---|
| Repository Compose file | The file in your source repository, commonly docker-compose.yml. |
| Public Compose service | The application entrypoint, such as web or gateway. |
| Published host port | The host port the selected service exposes for the proxy. |
| Public verification path | A real route whose expected result establishes useful application health. |
3. Configure and review before execution
In Config, supply the deployment identity, domain and template inputs. Configure required environment values through the product controls. Choose the correct Cloudflare zone or saved tunnel when that path is used.
Select Preview → to enter Review. Read the generated or selected Compose configuration and proxy plan. Check the application services, public entrypoint, ports, networks and persistent volumes.
You can explain what will be created, which hostname will point to it, how configuration reaches the services and where data persists. Resolve port or domain conflicts before pressing Deploy.
4. Deploy, inspect the evidence and open the workload
Select Deploy and follow the stage output. The workflow creates the runtime and automatically enrolls the result as a managed deployment. Use Open Deployments to find it afterward.
Read runtime and public checks separately. The UI can report Deployed, public route needs attention; treat that as unfinished public verification. Inspect the failure evidence and route before retrying.
Once the application is verified, connect an agent. Configure merge automation only after linking the explicit repository and verifying the normal deployment path.