Status: Implementation IMPLEMENTED × Exposure PUBLIC PREVIEW. Earlier versions of this page described an allternit-runtime service on port 8080 with a runtime.yaml, /status and a Metrics endpoint. Those do not exist on main.

​
Network posture

  • allternit-api binds 0.0.0.0:$ALLTERNIT_API_PORT. Block that port at the host firewall; only the local agent-daemon needs it.
  • The node needs only outbound HTTPS/WSS to api.allternit.com. The relay (/api/v1/runtime-relay/connect/:runtimeId) carries browser and SDK traffic to the node, so no reverse proxy, TLS certificate or inbound port is required.
  • If nothing is paired and online, relayed routes return HTTP 428.

​
Health checks

​
Backups

State lives under ALLTERNIT_DATA_DIR (per-instance SQLite). Stop the process, copy the directory, start it again. A device identity file (ALLTERNIT_RUNTIME_IDENTITY_PATH) belongs to the paired daemon; losing it means re-pairing.

​
Revoking a node

A paired device can be revoked through the Cloud API (/api/v1/runtime-devices/:id, /api/v1/runtime-devices/:id/revoke-self). See Cloud API.

​
Scaling

One paired node is one runtime. Provisioned and hosted instances are managed through the Cloud API (/api/v1/provisioned-instances, /api/v1/hosted-runtimes). There is no built-in horizontal scaling of a single node.

​
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.