-
- {capability.meta}
- {capability.title}
-{capability.copy}
-
- Your VPS has an
-
+
-
-
SELF-HOSTED OPERATIONS
-Your VPS has an
operational co-pilot.
- - GroundControl brings deployment, runtime evidence and infrastructure actions into one control plane that stays on your server. -
+
+
- SELF-HOSTED VPS OPERATIONS
+Build, deploy and operate your VPS from the tools you already use.
+GroundControl gives people and AI agents controlled access to deployment, runtime, terminal, domains and infrastructure operations without handing the conversation your server credentials.
+Open sourceSelf-hostedDocker nativeAgent ready
- 01 · DOCKER NATIVE
- 02 · OPEN SOURCE
- 03 · YOUR INFRASTRUCTURE
-
-
-
-
+
+
-
-
+
+
-
-
+
-
-
-
-
+
THE OPERATING PICTURE
-
- Know what is happening.
-
- Know what is happening.
Keep the controls close.
- GroundControl starts from the host you already have, preserving raw access while making system state easier to understand and act on.
+
-
- ONE CONTROL PLANE
-From host state to the next safe action.
-
- {capabilities.map((capability) => (
-
- {capability.number}
-
- ))}
-
+ WHY GROUND CONTROL
No local build box required.
Work can continue through deployments, runtime inspection, domains and the terminal without spinning up resources on your laptop, manually SSHing for every step, or jumping into GitHub just to trigger a deployment.
THE PRODUCT
One control plane for the full life of an app on your VPS.
{features.map((feature) =>
{feature.title}
{feature.copy}
{feature.meta}
-
+ BUILT AROUND OWNERSHIP
-“Your server remains the source of truth. GroundControl makes it legible.”-
- SELF-HOSTEDREVERSIBLE ACTIONSRAW ACCESS PRESERVED
-
-
+
+
FROM REQUEST TO RUNNING SERVICE
Less tab-switching. More finished work.
Use the GroundControl UI directly, or let an authenticated agent work through the tools GroundControl exposes. Repositories, build context, deployment targets, live host state and the terminal meet in one operating surface.
-
+
- 01Connect
Install GroundControl on your VPS and connect only the services your workflow needs.
+ - 02Describe or configure
Choose a template, use an existing Compose file, or tell an agent what you want deployed.
+ - 03Build and deploy
GroundControl runs the deployment against your infrastructure and keeps the evidence visible.
+ - 04Verify and operate
Check the public route, inspect runtime state, use the terminal, investigate failures and redeploy.
+
PRODUCTION TEMPLATES
Start from a real deployment shape, not an empty form.
Templates encode service relationships, domains, health checks, secrets and supporting infrastructure so common production stacks can be deployed intentionally.
{templates.map(([name, id, copy]) =>
{name}
{id}{copy}
-
+ START ON YOUR VPS
-
- One command.
-
- One command.
An independent control plane.
- The installer checks the environment, creates your GroundControl instance and gives you the credentials. Nothing is added to someone else’s dashboard.
-CAPABILITIES, NOT CREDENTIALS
Your infrastructure credentials stay with GroundControl. The client gets the operations you choose to expose.
GroundControl is single-tenant and self-hosted. It can run on the same VPS it manages, talk to additional hosts, and perform host-level work through its controlled execution layer.
INSTALL
Put GroundControl on your VPS.
Start with the installer, complete setup on your instance, then connect GitHub, Cloudflare or additional servers only when your workflow needs them.
- {installSteps.map(([title, copy], index) => (
-
- 0{index + 1}
-
- ))}
-
{title}
-{copy}
-TRY IT ON YOUR OWN VPS