The operating model
- A platform administrator deploys the central platform.
- A workspace owner creates a workspace and invites members.
- An authorized member registers a Kubernetes cluster or Linux VM as a target.
- The generated AgentK or AgentV installation connects outbound to the control plane.
- Members investigate the target through chat or launch a Workflow.
- AcornOps compiles the run’s exact model, target, tool, and approval scope.
- The target connector executes only the operations allowed by the member, workspace, target, and run.
- The management console retains the run state and safe results for review.
Core platform
The core runtime contains four services:
The control plane is the public API boundary. The execution engine and LLM gateway remain internal in production.
Deployments can optionally add the separate platform admin console, a governance-only browser application and same-origin BFF. It administers deployment-wide users, workspace access, plans, platform settings, and admin audit history without exposing tenant operations.
Connected targets
AgentK runs in a connected Kubernetes cluster. AgentV runs as a systemd service on a connected Linux VM. Both initiate outbound connections, report inventory and health information, and advertise their available target-native tools. These connectors are different from specialist Agents. A specialist Agent is a workspace definition used by a Workflow. AgentK and AgentV are target-side services.Two ways to run work
- Target chat investigates one target with its target-native assistant and live capabilities.
- Workflows apply reusable instructions through one or more specialist Agents and may run manually or through configured triggers.
Continue
Learn the core concepts
Understand the objects you see in the management console.
Review the architecture
Examine component responsibilities and trust boundaries.
Use an existing platform
Choose a Kubernetes or VM quick start.
Deploy AcornOps
Prepare and install the central platform.