In this article
An agent may write an analysis program but still be unable to reach a company's existing database. Understanding a service and connecting to it are separate problems.
The brazosd virtual private network, called VPC in the product, addresses connectivity. It gives authorized cloud execution environments a path to services exposed through connected devices.
A recognizable address for distributed services
Services live on office computers, servers, and private networks. Their addresses may change, and they may not be reachable directly from the public internet.
The private network gives connectors organization-scoped identities and addresses. The caller identifies a target; the platform routes the connection to the corresponding device and exposed service port.
An internal telephone system is a useful analogy. A caller need not understand every wire behind an extension, but the system must know where it leads and who may call it. Addressing identifies a destination; authorization decides whether access is allowed.
How a connection crosses the boundary
The implementation is called PseudoNet. A typical connection travels from a cloud execution environment through virtual routing and a platform gateway, then through the connector channel to a service reachable from the device.
| Layer | Responsibility |
|---|---|
| Organization-scoped address | Identify the intended target |
| Virtual routing | Select the platform connection path |
| Gateway and connector | Bridge cloud and device networks |
| Port mapping | Select the service exposed by the device |
| Identity and permission checks | Decide whether access is allowed |
Swipe to see the whole table
The current path serves TCP connections, including many databases and HTTP services. It does not automatically carry every network protocol; UDP and QUIC support cannot be assumed.
Reachability is separate from permission
Knowing a private hostname does not grant access. Device ownership, organization scope, and enterprise permission rules remain relevant.
Agent sessions access devices under the session user's identity and device permissions. Naming a device in a conversation is not authorization. A connector also exposes only configured services; removing a mapping or taking the device offline changes what is reachable.
Reliable connectivity therefore combines routing, identity, a deliberately limited service exposure, and live availability.
Why this matters to an agent platform
Without a common connection layer, each internal system may require a public endpoint or a custom bridge. Integration effort then limits what agents can actually use.
A private network moves part of that effort into the platform. Existing services can remain on their current devices and networks while authorized agents or applications reach them. A company can begin with one service and expand gradually, preserving previous investments in data and software.
Connectivity still needs meaning
A network answers “can this be reached?” An API or tool contract answers “what can be done, with which inputs?” Connecting a service does not teach an agent its operations automatically.
A service might be reached through VPC and expose actions through an API or MCP tools. MCP is a protocol for describing and providing tools to agents. It complements networking rather than replacing it.
Connected devices and enterprise permissions explain the other parts of this system: usable capabilities and authorized action.