Runner types
Axio has two runner categories. They share the same job model; they differ in who owns the machines and what tenants can see.
| Aspect | ▤ Self-hosted | ☁ Provider (Axio-managed) |
|---|---|---|
| Who provisions | You | Platform operator (Axio) |
| UI | Administration → Runners | Invisible to tenants.Hosted fleet tab in the provider org only. |
| How you target | Your labels and groups | axio-linux, axio-windows, … |
| Registration token | axreg_\* | axpreg_\* (or internal API) |
| Billing | Your infrastructure | Metered minutes and storage on the subscription |
axio-\* labels | Never assigned | Applied automatically |
▤ Self-hosted
Install @axio/runner-core on a VM, Docker host, or Kubernetes cluster. Connections are outbound-only.
Your
Infrastructure ▣ VM ◉ Docker host ✥ Kubernetes cluster
→ Infrastructure ▣ VM ◉ Docker host ✥ Kubernetes cluster
⚙
→ @axio/
runner-core Agent ✓ Axio Overview inventory ▤
1GroupCreate a runner group in Axio
2Registration commandGenerate and run the command
3AgentRegisters and starts sending heartbeats
4Overview inventoryRunner appears in the inventory
ⓘ See setup-and-registration and deployment for detailed steps.
☁ Provider (hosted)
Like GitHub-hosted runners. Axio runs a shared fleet in the platform provider organization (seed: anantacloud). Tenants never list those runners, groups, or tokens.
Customer tenant Select a hosted label on the workload
→ axio-linux axio-windows … ☁ Axio-managed fleet Runs in provider organization (anantacloud)
→ ▤ Executes IaC jobs
⚠ Customers only pick a hosted label on the workload. Requires
providerRunnerAccessEnabled on the plan.Operators use Runners → Hosted fleet (or scripts/setup-hosted-runner-fleet.ts locally).
ⓘ See hosted-fleet for more details.
▣ Scheduling reminder
☁ Workload with
axio-\* Runs on provider org fleet. ● Workload with customer labels Runs on your inventory, scoped by group.
⚙
automatic Tries self-hosted first unless hosted labels force the shared fleet.