Beam
[TUNNELS] Secure connectivity

Move data.
Not firewalls.

Expose a service, receive a file, or connect two private agents without opening inbound ports. Beam keeps every route encrypted, inspectable, and owned by your machines.

No Inbound Ports

Your network stays closed by default.

One Local Agent

Endpoints survive after the CLI exits.

Structured Control

Inspect, resume, cancel, and close.

Route / live Connected
LOCAL :300001
BEAM AGENT02
PRIVATE RELAY03
DESTINATION04
TLS 1.3
QUIC
YAMUX
[01]

One tunnel layer. Every shape of traffic.

Start with the data you already have. Beam turns files, services, streams, and destinations into lifecycle-managed endpoints.

01

Files

Share a single file through a durable endpoint with transfer receipts and resumable delivery.

02

HTTP

Publish a local web service without opening inbound firewall ports or managing certificates.

03

Streams

Carry continuous byte streams through the Beam relay fabric with backpressure built in.

04

WebRTC

Bridge real-time media and peer sessions while keeping endpoint lifecycle under agent control.

05

TCP

Reach databases, developer tools, and private services over an explicit encrypted path.

06

Destinations

Turn a machine into a controlled receiving endpoint for distributed uploads and downloads.

[02]

The control stays local. The route goes global.

The public CLI sends intent to a private companion daemon. The daemon owns the network protocols, durable state, and long-running work.

01

beam

Parse, authenticate, validate

02

beam-agentd

Persist state and operate endpoints

03

Coordinator + relay

Discover and route encrypted traffic

04

Remote endpoint

Receive, bridge, or serve

[03]

Close the terminal. Keep the transfer.

Uploads, downloads, bridges, and duplex sessions continue inside the daemon. Come back later with the operation ID.

$ beam tunnel upload ./dataset.parquet --session session.json

operation op_01JZ8P created

status: running · progress: 68% · resumable: yes

$ beam tunnel operation op_01JZ8P

running · 4.8 GB / 7.1 GB

Durable state

Operation journals and endpoint identity survive CLI restarts.

Explicit cancellation

Stop work by operation ID without killing the agent.

Structured errors

Machine-readable failures stay useful in automation.

+
+
[04]

Create your first route
in minutes

Install one bundle. Use one public CLI. Let the companion agent keep the connection alive.