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

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.

Deployments

Build and deploy from connected repositories to Docker Compose, static sites, k3s, Cloud Run and Terraform-backed targets.

Build · deploy · verify · redeploy

Runtime

Inspect containers, services, health, logs, processes and host telemetry from the same place you deploy them.

Docker · services · logs · health

Terminal

Use a real browser terminal against the VPS, including host-level commands when GroundControl itself is running in Docker.

Shell · host operations · AI commands

Intelligence

Investigate broken customer journeys from live evidence, connect changes to failures and prepare the next safe action.

Evidence · investigation · recovery

Domains & edge

Connect Cloudflare, provision DNS, route through Caddy and verify the public HTTPS path as part of deployment.

Cloudflare · Caddy · DNS · TLS

Your infrastructure

GroundControl is self-hosted and single-tenant. Your instance, data and operational credentials stay on infrastructure you control.

Open source · self-hosted · single tenant

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.

  1. 01
    Connect

    Install GroundControl on your VPS and connect only the services your workflow needs.

  2. 02
    Describe or configure

    Choose a template, use an existing Compose file, or tell an agent what you want deployed.

  3. 03
    Build and deploy

    GroundControl runs the deployment against your infrastructure and keeps the evidence visible.

  4. 04
    Verify 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.

Existing Compose

vps-caddy-existing-compose

Bring a production docker-compose.yml from Git. GroundControl discovers the service graph, env requirements, ports and health checks, then publishes the selected service.

Odoo Community

vps-caddy-odoo-community

Deploy Odoo Community with PostgreSQL, persistent data, generated credentials, a public domain and local recovery archives.

Next.js SaaS

nextjs-saas-postgres-redis

Next.js with PostgreSQL and Redis for auth, queues, sessions and application state.

FastAPI + worker

fastapi-worker-postgres-redis

FastAPI/Uvicorn, worker, PostgreSQL and Redis with a production-shaped service layout.

Monorepo

monorepo-web-api-worker

Separate web and API domains with a worker, PostgreSQL and Redis behind the same deployment workflow.

Microservices + ops

caddy-secure-microservices-observability

Web, API, worker, PostgreSQL, Redis, object storage, logs and uptime checks in one Caddy-first stack.

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.

$curl -fsSL https://raw.githubusercontent.com/teckedd-code2save/groundcontrol/main/scripts/bootstrap | bash -s -- -i ~/.ssh/id_ed25519 root@YOUR_VPS_IP

TRY IT ON YOUR OWN VPS

Build there. Deploy there. Operate there.