Files
Share a single file through a durable endpoint with transfer receipts and resumable delivery.
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.
Your network stays closed by default.
Endpoints survive after the CLI exits.
Inspect, resume, cancel, and close.
Start with the data you already have. Beam turns files, services, streams, and destinations into lifecycle-managed endpoints.
Share a single file through a durable endpoint with transfer receipts and resumable delivery.
Publish a local web service without opening inbound firewall ports or managing certificates.
Carry continuous byte streams through the Beam relay fabric with backpressure built in.
Bridge real-time media and peer sessions while keeping endpoint lifecycle under agent control.
Reach databases, developer tools, and private services over an explicit encrypted path.
Turn a machine into a controlled receiving endpoint for distributed uploads and downloads.
The public CLI sends intent to a private companion daemon. The daemon owns the network protocols, durable state, and long-running work.
Parse, authenticate, validate
Persist state and operate endpoints
Discover and route encrypted traffic
Receive, bridge, or serve
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
Operation journals and endpoint identity survive CLI restarts.
Stop work by operation ID without killing the agent.
Machine-readable failures stay useful in automation.
Install one bundle. Use one public CLI. Let the companion agent keep the connection alive.