[ connection_status: established ]

> Device-to-device connectivity for edge AI

Encrypted NAT-traversing streams between cameras, robots, and GPU workers. Open source.

Open source
Built on iroh
NAT-traversing
E2EE
src/main.rs — peerbase-sdk
let session = pb.connect("camera-1").await?;
let mut video = session.open_stream("4k-feed").await?;
let mut events = session.open_stream("inference").await?;

// Stream initialized. Direct link established.
loop {
    let frame = video.next().await?;
    process_frame(frame);
}
main.rs_
Architecture Node
US-WEST-2 // NODE_ID: 8F2A...9C11
01 // DIRECT_CONNECT

Punch through symmetric NATs using STUN/TURN. Direct IP-to-IP delivery with sub-50ms latency. Relay fallback when direct fails.

02 // NAMED_STREAMS

Open multiple named streams per session. Video, telemetry, and control on one encrypted connection. No port management.

03 // SELF_HOSTABLE

Run your own control plane. No vendor lock-in. One binary, one config file. Or use managed cloud — your call.

01. HOW IT WORKS

01

Identity

Each device gets a persistent cryptographic identity and registers with the control plane by name.

$ peerbase device enroll --name camera-1
02

Discovery

Find peers via the API and connect using name-based routing. NAT traversal is automatic.

let session = pb.connect("camera-1").await?;
03

Streaming

Open named bidirectional streams and pipe any data. Video, sensor, control — all multiplexed.

let stream = session.open_stream("4k-feed").await?;

02. USE CASES

Built for demanding high-bandwidth environments where latency and security are non-negotiable.

> video-surveillance
> robotics
> ai-inference
> iot-fleet

03. PRICING

Free while in beta

Peerbase is free to use during the beta period. Managed cloud and self-hosted — both fully available, no limits.