https://console.demo.acornops.dev/ for evaluation, backed by https://api.demo.acornops.dev.
Choose your path
Try the demo
Explore the public demo before deploying AcornOps into your own environment.
Self-host AcornOps
Deploy the platform, configure dependencies, and connect Kubernetes clusters or VMs.
Build integrations
Build bots, workflow adapters, custom clients, or external MCP tool providers.
Operate a deployment
Verify health, rotate secrets, inspect failures, and keep routes aligned.
What AcornOps gives you
- A workspace model for grouping targets, Kubernetes clusters, VMs, members, MCP servers, tool settings, and investigation history.
- A browser management console for target inventory, findings, runbooks, members, settings, and chat-based troubleshooting.
- A control plane that owns auth, sessions, workspaces, the target core, target registration, agent connections, run state, and API authorization.
- An execution engine that performs troubleshooting runs and streams progress back to the control plane.
- An LLM gateway that enforces run-scoped model and tool permissions before provider or remote MCP traffic leaves the platform.
- A AgentK that runs inside each connected Kubernetes cluster and connects outbound to the control plane.
- A AgentV that runs on Linux/systemd hosts and connects outbound to the control plane.
Start with deployment
Prepare the platform, connect targets, and expose the management console.
Build against the control plane
Use webhooks, run events, approvals, and the public control-plane API.
Review the architecture
Understand the control plane, execution engine, LLM gateway, and target-agent boundaries.
Self-host workflow
- Deploy the central platform with either the Kubernetes chart or VM Compose stack.
- Sign in to the management console and create a workspace.
- Register a Kubernetes cluster or Linux VM from that workspace.
- Install the generated AgentK or AgentV command.
- Review findings, manage available tools, and start troubleshooting sessions.
Platform components
Management console
Browser application for workspaces, targets, investigations, sessions, and tools.
Control plane
API, auth, workspace state, agent WebSocket connections, and orchestration entrypoint.
Execution engine
Run execution, tool-call coordination, and Redis-backed run reservation.
LLM gateway
Provider routing, model access, MCP registry, secrets handling, and request auditing.
AgentK
Outbound Kubernetes connector for snapshots, logs, and tool execution.
AgentV
Outbound Linux/systemd connector for host snapshots, logs, and read-only tools.
Self-host surfaces
- Console:
https://console.example.com/ - Public docs:
https://docs.acornops.dev/ - Public control-plane API:
https://api.example.com/api/v1 - Agent WebSocket:
wss://api.example.com/api/v1/agent/connect
example.com with domains you control. Execution engine and LLM gateway are internal services. They should not have public DNS records or public ingress routes in production.
Where to go next
Kubernetes
Helm deployment for the central platform, with operator-provided Postgres and Redis.
VM Compose
Docker Compose deployment path for single-VM environments.
Configuration
Required secrets, OIDC settings, LLM provider settings, and runtime limits.
Integrations
Bot adapters, webhook handling, user-attributable approvals, and public API boundaries.
MCP and tools
Builtin tools, remote MCP servers, public headers, and write confirmations.
API overview
Browser session flow, API families, integration boundaries, and workflow notes.