Skip to main content
Connect machines through sandbox private networking for private IPv4 TCP and UDP traffic between running machines in the same organization when their placement supports it. Reachability depends on placement.

​
Discover network information

The API is GET /sandboxes/{id}/network; MCP exposes bead:network_get. The response includes the machine’s privateIP, endpoint information, and organization scope. Read the current address for every machine you intend to contact. Start a service on an appropriate guest interface, then connect from another machine in that organization using its discovered private address and application port.

​
Placement and membership

Co-location is preferred. Cross-machine reachability depends on the deployment’s authenticated overlay and current placement. Do not assume that arbitrary machines placed on different hosts can reach each other. Membership is scoped by organization and current machine identity. Pause, snapshot, and deletion revoke the old membership. Read network information again after lifecycle changes or a fork. Private peer networking supports IPv4 TCP and UDP. Custom network groups and IPv6 peer networking are unsupported.

​
Choose an access path

Private membership does not open reserved guest control ports or provide a public listener. Configure application authentication for services that need it.