Managed Cloud

The Exo control plane is at https://exo.adaptive.live. You only install the operator in the cluster where your agents should run, and connect it. Four short steps.

The setup

• The operator: the autonomic-manager Deployment, its RBAC, and the admission webhook, in your cluster.
• A deployment token: minted in the managed dashboard, it links this cluster to your tenant.

1 · Install the operator

Helmhelmexo-installexo-installManifestskubectl apply

In the managed dashboard, go to Deployments → New, name the deployment (e.g. prod-eu-west-1), and copy the token shown once.

Step 1 — create the namespace and store the token as the autonomic-auth secret:

●terminal· bash

copy all

copy

kubectl create namespace autonomic-system

copy

kubectl -n autonomic-system create secret generic autonomic-auth \
  --from-literal=token=<your-deployment-token>

Step 2 — install the operator in managed mode:

●terminal· bash

copy all

copy

helm repo add exo https://exo.assets.adaptive.live/charts

copy

helm repo update

copy

helm upgrade --install autonomic exo/autonomic \
  --namespace autonomic-system --create-namespace \
  --set manager.managed=true

2 · Verify

Within a few seconds the deployment flips to online in the dashboard and its resource lists populate. If it stays offline, check the operator logs:

●terminal· bash

copy all

copy

kubectl -n autonomic-system logs deploy/autonomic-manager --tail=50

That's it. The cluster is connected. Next, mint roles and create your first agent. For token rotation and the one-token-per-deployment rule, see Tokens & deployments.

What's next

• Create your first agent: declare a tool and an agent, sign in, and fire the first run on your connected cluster.
• Create tools: define the actions your agents can call and how they map to your systems.
• Build agents: compose tools, prompts, and models into the agents your team will invoke.
• Set access control: keep most agents open to the team and restrict the sensitive few.
• Tokens & deployments: rotate deployment tokens and manage one-token-per-deployment.