Skip to main content
This section is for platform administrators and self-hosters. If your organization already operates AcornOps, choose the Kubernetes quick start or VM quick start instead.

​
Deployment layers

AcornOps has two independent layers:
  1. The central platform runs the management console, control plane, execution engine, and LLM gateway.
  2. Target connectors run as AgentK in each Kubernetes target or AgentV on each Linux VM target.
Deploy the central platform first. Workspace administrators connect targets afterward from the management console.

​
Choose a central-platform deployment

Kubernetes

Use the AcornOps platform Helm chart with external Postgres and Redis.

VM Compose

Use the single-machine stack for smaller environments and operational testing.
  1. Prepare the prerequisites.
  2. Select one complete, published stack from the stack-versions.yaml release matrix. Do not combine independently released component tags.
  3. Deploy the central platform on Kubernetes or with VM Compose.
  4. Configure platform policy.
  5. Complete the production readiness checklist.
  6. Optionally configure the platform admin console for deployment-wide governance.
  7. Hand workspace onboarding to the intended owners and users.
  8. Use the operations guide for upgrades, health, and rotation.
The deployment reference and configuration reference preserve the complete setting and behavior details.

​
Govern the deployment

Platform admin console

Manage users, workspace access, plans, platform policy, and admin audit history through the governance-only console.

Control-plane admin API

Run narrowly scoped operational or break-glass administration that is not exposed in the console.