01
Distributed data plane
AgentSight Nodes capture, materialize, query, and retain detailed runtime evidence close to the agents they observe. Each Node remains authoritative for its own session data.
Architecture
A distributed, local-first data plane for AI agents.
AgentSight separates runtime evidence from cloud coordination. Detailed agent data stays on customer-controlled Nodes and Site Gateways, while the hosted layer coordinates how people and machines discover, reach, govern, and collaborate across the distributed fleet.
Three planes
Keep evidence close to execution. Coordinate globally.
The same architecture works from one laptop to a distributed enterprise fleet. Scaling adds coordination and federation instead of moving every trace into a central warehouse.
02
Coordination plane
AgentSight Cloud coordinates identity, discovery, managed connectivity, policy, capabilities, audit, and collaboration without becoming the authoritative telemetry store.
03
Presentation plane
The hosted app, CLI, and other clients query the same Node protocol across local, direct, managed, and enterprise deployments.
One protocol, four deployment modes
Start local. Grow into a distributed fleet without changing the data model.
Local, direct, managed, and enterprise modes share the same AgentSight Node, session model, query semantics, and presentation layer. The difference is how identity, connectivity, policy, and federation are provided.
- 01Local
One Node, local evidence, local or hosted UI, no cloud dependency required.
- 02Direct Fleet
Multiple Nodes over LAN, VPN, Tailscale, WireGuard, SSH tunnels, or other direct connectivity.
- 03Managed
AgentSight Cloud provides identity, discovery, managed connectivity, collaboration, policy, and fleet access.
- 04Enterprise Site
Site Gateways federate large fleets while keeping detailed evidence inside customer-controlled Nodes and sites.
Why distributed matters
Privacy, cost, availability, and scale come from the same design.
AgentSight does not need a second authoritative copy of every prompt, response, process, file event, or resource sample in its cloud in order to provide a unified product.
Data ownership
Customer-controlled evidence
Detailed runtime evidence remains on the Node or customer-controlled Site Gateway by default.
Economics
No telemetry warehouse tax
Cloud pricing can follow coordination and governance value instead of trace count, token volume, or hosted retention.
Resilience
Capture does not depend on the cloud
Nodes continue local capture, materialization, retention, and query even when the coordination plane is unavailable.