One local control plane
The CLI, local dashboard and agent integrations use the same execution services. Provider tokens, SSH keys, plans and audit data stay on your workstation.
vops
Local control plane. Agentless servers. Compare providers, operate the machines you already own, deploy applications, and govern development agents without handing them your infrastructure credentials.
Your servers stay yours
Provision through a supported provider or bring any reachable Linux host. vops operates it over SSH without installing a permanent vops control plane.
Plan before changing
Cost-bearing and destructive work is made visible before it runs. Ownership checks, dry runs, immutable plans and explicit approval limit surprises.
Agents with boundaries
Connect Codex, Claude Code, OpenCode or Antigravity, then give each session an objective, targets, lifetime and budget instead of raw credentials.
Start here
What vops is The five-minute model: local-first, agentless servers, and where vops fits.
Your first ten minutes Install vops, compare providers without credentials, and open the local dashboard.
Bring your own server Register a host over SSH, inspect it, and prepare it for applications.
Deploy an application Take a flui.yaml from plan to approval, deployment and verification.
Operate safely
Dashboard guide Understand every local view, its data source, its CLI equivalent and its safety boundary.
Choose an agent approach Adopt agent support progressively: knowledge, governed advisory access and future protected mode.
Safety and ownership What vops refuses, when it asks for approval, and what ownership checks protect.
CLI reference The command topics, grouped by the work people use them for.
Troubleshooting A product-level diagnostic path for hosts, applications, ingress, credentials and agents.
Security model The workstation, provider, host, dashboard and agent trust boundaries in one place.
These are the human-facing vops docs. The procedural skill, MCP schemas and machine-readable capability catalog used by development agents ship with vops itself so they can stay versioned with the executable.