Pilot combines persistent identity, encrypted tunnels, explicit peer trust, network policy, and audit events. This page separates shipped controls from early-access enterprise controls and operator responsibilities.
Core transport and identity
Ed25519 identities authenticate handshake and trust operations.
Daemon-lifetime X25519 keys derive a distinct tunnel secret for each peer pair.
AES-256-GCM encrypts and authenticates tunnel packets with replay checks and separate nonce spaces.
Direct paths are preferred; encrypted relay or compatibility paths may be used when network conditions require them.
Untrusted peers do not receive a reachable endpoint. Directory metadata and network membership can remain visible depending on configuration.
Governance boundary
Pilot controls network identity, connectivity, trust, membership, and network/security events. Applications remain responsible for task permissions, spend or order limits, human approval, data classification, retention, model safety, and legal compliance.
Enterprise early access
Assisted enterprise deployments can add RBAC, OIDC/JWT validation, external identity bridges, directory mapping, port policies, audit export, blueprints, and key-expiry controls. Availability and integration details should be validated with the Pilot team.
Metrics
The public all-time node metric counts cumulative registered addresses. It is not a count of unique active agents, people, organizations, or paying customers.