opsgate

한국어 · Website

AI proposes. Your passkey runs it.

opsgate is a self-hosted, open-source MCP server for Kubernetes with human-in-the-loop approval, written in Go, for people who run servers on their own and want to hand them to AI without handing over a shell or kubectl. Every change to your server, whether an alert rule or an AI client such as Claude, ChatGPT, Claude Code or Cursor suggests it, becomes one approval card: the exact plan, who suggested it and whether it can be undone. Approve the card with a passkey on your phone or computer, and the server runs exactly that plan, then tells you whether the service recovered. Nothing else can make a change.

Three promises:

1. Only what you approved runs, exactly as approved. The server plans again before it runs and stops if anything changed.
2. Nothing that deletes your data becomes a card. Restart, scale, image restore and replacing a pod its controller recreates are the whole catalog.
3. From alert to fix in a few taps: the notification, an action, Approve.

The same card approves everyday AI changes, such as writing a note, so passkey approval is already a habit when an outage comes.

opsgate is not a shell or a general agent, not a monitoring dashboard, not on-call paging for a team, and it never repairs anything without a person.

Status: not 1.0 yet. The core loop (alerts, approval cards, passkey approval, recovery check) is kept compatible as described in stability; notes, the host provider and the analyzer are experimental. Changes require user authorization, allowed targets and human approval. Read restrictions and output redaction reduce sensitive data exposure. Third-party security review is pending; the security policy explains the protections and remaining limitations.

The problem

Running a server alone usually leaves two gaps:

• You find out late. Without proper alerting, you hear about an outage from users, or stumble on it yourself.
• You know the fix but cannot reach the server. A phone SSH app works, but typing commands on a phone in the middle of an outage is slow and error-prone.

Giving an AI assistant a shell would close the second gap and open a worse one: a single wrong or irreversible command. opsgate closes both gaps and keeps every change in front of a person.

How it handles an incident

1. Know first. opsgate watch follows the Kubernetes API and sends alerts to Discord, webhooks or email as soon as something fails. It can also put the alert in your approval inbox and push a notification to your phone. See watch alerts.
2. Stabilize from anywhere. Tap the notification or the alert's Choose an action link. After a passkey sign-in you see the actions that fit the current state, such as restoring the last working image or restarting the workload. Pick one, review its fresh plan and approve: it runs right away. opsgate then watches the workload and tells you whether it recovered, not only that the change was applied. If it can be reversed, an Undo button appears. A phone browser is enough.
3. Then find the cause. With the service back, ask your AI client to investigate through opsgate's read tools, or let the optional analyzer make a first pass.
4. Remember it. The optional note provider keeps runbooks and past incidents in plain Markdown, and assistants are instructed to check them first and offer to record the outcome. See notes.

Design principles

No arbitrary commands

Only purpose-built tools exist. There is no shell tool and no Kubernetes Secrets tool.

Everything starts off

Providers, write actions and allowlists ar

... View full README on GitHub