Own the path to production.

Agent-assisted deployment.
End to end.

Bring your project and the agents you already use. GroundControl connects configuration, rollout and verification on infrastructure you own, with a clear record of every deployment.

Already installed? Continue setup →
Self-hostedMCP + OAuthOpen source

Deployment, with ownership built in.

From the first deploy to the next release, your project stays in your hands. Bring your code, choose your infrastructure, and work with your agent to configure, deploy and verify.

  1. 01Source
  2. 02Configure
  3. 03Deploy
  4. 04Verify

Inside GroundControl

Start with the application you’re building.

Pick a folder from your computer or import a GitHub repository. Your project brings the source, purpose and deployment instances together.

Add source first. Choose its deployments separately.

Add your first project
GroundControl Add project chooser with folder and GitHub import options
Current interface · isolated demo · 20 October 2026Enlarge ↗︎

01 / From instruction to execution

One shared view. From intent to result.

GroundControl connects your application’s source, containers, configuration, and public address. Your agent works from that shared context, with tools to carry an authorized request through to a result you can inspect.

01

Inspect real application state.

Ask your agent what is deployed, read the logs, and check service health. It works from your application’s state and deployment history.

02

Let your agent take action.

Approve the capabilities and deployments it can use through OAuth. GroundControl executes supported deployment requests on your infrastructure while holding the credentials.

03

Follow through to the result.

Get runtime checks and public endpoint evidence for the operation. A durable operation ID lets your agent return to the same work after a timeout or in a later conversation.

Why GroundControl

Your infrastructure, connected to the agents you use.

Read the story

02 / Start with what you have

You installed it.
Here is what comes next.

Start on your computer or connect an existing Linux server. Add the application you’re building, then decide where and how its deployments run.

Open the post-install checklist →

03 / Autonomy without surrender

Your infrastructure.
Your agents.
Your final say.

Bring a project from your computer or GitHub. Connect its existing deployments or launch a new instance on your own infrastructure. Keep your sources and environments together.

MCP gives your agent the tools. OAuth defines its access. You can work through the interface or your agent, using the same application identity and recorded results. Review and revoke access from the Agents workspace.

Read the philosophy and core concepts →
Example · one application, independent deployments
ProjectWeekend plannerFolder / GitHub repository
Developmentweekend-localDocker on your computer
Productionweekend-productionOn your VPS
webPublic applicationapiApplication servicepostgresPersistent dataredisCache / queue
Public routeapp.example.com → webVerified separately

An OAuth grant selects the deployment. Operations act on that identity and record their results.

04 / Evidence from a real VPS

From GitHub push
to agent insight.

For managed workloads with merge automation enabled, a signed GitHub push starts a deployment your agent can follow. In this recorded example, GroundControl deployed RentAWeekend, and ChatGPT inspected its health and operation record through MCP.

GroundControl runtime image verification and public HTTP 200 evidence for RentAWeekend
Recorded RentAWeekend release · 21 September 2026 · opened in the desktop UI on 22 SeptemberEnlarge ↗︎

Captured through MCP

RentAWeekend

Health check
22 Sep 2026
Runtime
4 containers healthy
Public endpoint
HTTP 200

Recorded 22 September 2026 through a scoped MCP connection.

Open the health response ↗︎Inspect the deployment record →
Where we’re goingProduct direction

From verified operations
to proactive recovery.

Serendepify’s vision is a system that understands service relationships, tests affected customer journeys, and helps recover from regressions within an operator’s policy. This is the direction for Autopilot, not a promise of unattended recovery in today’s release.

Explore the Serendepify vision

The operator’s handbook

Understand it.
Then put it to work.

Follow the commands, product steps and checks for installation, discovery, agent access and deployment.

Explore the handbook →

Start with one host and one application

Your infrastructure.
Ready for your agent.

Install GroundControl, choose an application, and connect your agent. Start with a health check, then explore the operations your workload supports.

Follow the installation guide
Start from your computer
curl -fsSL https://raw.githubusercontent.com/teckedd-code2save/groundcontrol/main/scripts/start -o groundcontrol-start
bash groundcontrol-start

Choose this computer or a remote Linux server.
macOS / Linux · Windows through WSL · Docker for local installs.