Trust Center

Security and control,
built into the network.

Explore how Pilot handles identity, encrypted transport, trust, coordination, policy, and audit across core and managed deployments.

Security documentation →Inspect the sourceReport a vulnerability
SourceAGPL-3.0Daemon and protocol implementation are public.
Private-node accessTrust or network policyApplication traffic requires an applicable grant.
SpecificationPublic wire formatImplementation-aligned technical reference.
EnterpriseEarly accessManaged controls are available for evaluation.
Architecture

Peer connectivity.
Lightweight coordination.

Pilot separates encrypted agent traffic from the services used for identity registration, discovery, NAT traversal, and relay fallback.

EndpointAgent AEd25519 identity
Coordination planeRegistry + beaconDiscovery, public keys, endpoint exchange, NAT assistancePilot-operated by default · endpoints are configurable
Payload planeEncrypted peer tunnelX25519 key exchange · AES-256-GCM tunnelDirect when possible · encrypted relay fallback when needed
EndpointAgent BEd25519 identity
What coordination can seeRegistration metadata, public keys, advertised endpoints, timing, and network membership needed to operate the service.
What relay fallback carriesEncrypted payload packets. The relay adds a hop and can observe traffic metadata, but it does not receive tunnel keys.
What you can changeRegistry and beacon endpoints are configuration values. Dedicated and on-premises deployments are enterprise early access.
Governance boundary

Network controls for
real-world workflows.

Pilot authenticates peers and constrains network access. Application-level scopes and approval rules can be layered on top for business actions.

Pilot enforcesNetwork authority
  • Persistent agent identity and signed handshakes
  • Private-node stream and datagram admission
  • Peer trust, network membership, rejection, and revocation
  • Network membership and port policies
  • Role-based administration and key lifecycle
  • Structured network and security audit events
Your system enforcesBusiness authority
  • Which tasks an agent is allowed to perform
  • Purchase limits and counterparty approval
  • Human review for consequential actions
  • Data classification and retention rules
  • Prompt, model, and tool-level safety controls
  • Legal, regulatory, and contractual compliance
!

Layer controls around consequential actions. Cross-company workflows can combine Pilot network policy with application-level scopes, spend or order caps, and approval gates.

Control surface

Controls a security team
can evaluate.

Core protocol controls ship in the open-source daemon. Private and enterprise operations are early access and should be evaluated against your production requirements.

Core · available

Trust & revocation

Private nodes admit application traffic through peer trust or shared-network membership, with reject and revoke controls.

Core · available

Encrypted transport

Ed25519 identity, X25519 key agreement, and AES-256-GCM authenticated tunnels.

Enterprise · early access

RBAC & key lifecycle

Owner, admin, and member roles; delegated administration; rotation, expiry, and forced renewal.

Enterprise · early access

Identity integration

Native OIDC/JWT validation, provider webhooks, directory sync, role mapping, and bridge paths for other identity systems.

Enterprise · early access

Network policy

Membership limits, port allowlists, join rules, policy expressions, and fail-closed policy retention.

Enterprise · early access

Audit export

Structured events with export to Splunk HEC, CEF/Syslog, JSON endpoints, and webhooks.

Product status

Capabilities and
availability.

A concise view of shipped functionality, early-access controls, and the responsibilities that remain at the application layer.

TopicStatusPrecise statement
Protocol implementationAvailable

Source is published under AGPL-3.0 and can be inspected, modified, and redistributed under that license.

Wire specificationPublished

The protocol message types, addressing, transport, encryption, and trust model are available for technical review alongside the implementation.

Pre-trust hardeningConfigurable

Optional strict controls extend trust checks to key exchange, private directory operations, and NAT-punch authorization. They are enabled per deployment after compatibility review.

Private / enterprise networksEarly access

Managed and dedicated deployments, identity integrations, policies, and audit exports are available for evaluation; availability and SLAs are not represented as generally available.

Security certificationCurrent status

Independent certification is not currently listed. Customers can evaluate the available technical controls against their own compliance requirements.

Business-process governanceApplication layer

Pilot governs agent connectivity; application authorization, approval flows, and legal authority are configured by the deploying organization.

App Store

Curated packages.
Layered control.

Listed apps are reviewed and verified before discovery, while network trust and application policy continue to shape access at runtime.

  • App review answers whether a listing meets catalogue requirements.
  • Network trust answers whether two endpoints may communicate.
  • Application policy answers what methods, data, spend, and side effects are allowed.
Read the App Store model →
Metric definitions

How network activity
is measured.

Homepage figures come from the public network telemetry endpoint. The definitions below show how each live service counter is calculated.

total_nodes

Registered agent addresses

Cumulative addresses issued by the public registry, rather than a unique organization or customer count.

active_nodes

Agents online now

Agents currently represented as active by the registry heartbeat state. This counter can change rapidly.

requests_per_sec × 3,600

Protocol requests per hour

A rate derived from current registry telemetry. It includes protocol traffic and should not be read as completed business tasks.

Source: public network telemetry JSON. Build-time values are used as a fallback when the endpoint cannot be reached. These operational counters have not undergone independent audit.

Evaluate Pilot

Start with the
technical model.

Review the implementation, test inside an isolated network, define the application authority your agents will retain, and bring the evidence to your security team.

Review security →Readiness report (PDF)Contact the team