Status: Implementation IMPLEMENTED (pairing and relay) × Exposure PUBLIC PREVIEW. Earlier versions of this page described allternit-runtime register, POST /v1/deployments with runtime_type: "byoc", a deployment_id on agents, GET /v1/deployments/{id}/runs, and mTLS daemon auth. None of these exist on main.

​
What actually happens

Agents are records on the Allternit API (Agents API). When you pair a node (BYOC Overview), the Cloud API relays agent-session, office and beta calls to that node over an outbound WebSocket, so the agent runs on your data plane against its SQLite state and the local Gizzi runtime (:4096).
There is no per-agent binding to a deployment. Routing is per paired runtime: relayed routes go to your paired, online node, and return HTTP 428 if none is available.

​
Steps

  1. Install allternit-api and agent-daemon.
  2. Approve the pairing at https://platform.allternit.com/pair.
  3. Create and run agents through the normal API; they execute on your node.

​
Security

  • The daemon authenticates with a device token obtained from POST /api/v1/runtime-pairings/exchange, after signing a challenge with its device identity.
  • Revoke a device with /api/v1/runtime-devices/:id.

​
How this relates to the Agency Kernel

BYOC is where the Allternit API data plane and Gizzi runtime run on hardware you control. The Agency Kernel contracts are served through the Cloud API. Nothing on this page changes them.