New: Rooms connect your machines, buckets and AI agents in one private network. Read the guide
BEAM
FRConsole Book a call
BEAM Data Transfer

Move massive data. Pay egress once.

Hundreds of workers move your objects in parallel, from one source to every destination. The source is read once, every part is verified on arrival.

Book a call See pricing →
  • Pay per TB, no contract
  • Storage keys never leave your side
  • Every part verified at arrival
Works with the storage you already run
Amazon S3 Cloudflare® R2 Hippius Hugging Face Wasabi Backblaze B2 MinIO DigitalOcean Spaces

Everything you need to move data at scale

Rooms

A private network for your machines, buckets and agents

Roles, per-channel grants and invitations. End-to-end encrypted between agents.

Explore Rooms
A frosted glass cube holding three linked glass spheres, one fiber entering from outside
Fan-out

One read, every destination

The source is read once, whatever the number of targets. Egress paid once.

See supported storage
One glass sphere sending a fiber bundle that splits into six branches toward six glass tiles
Telemetry

Watch every part land, live

Throughput per destination, parts verified, slow chunks reassigned automatically.

Read the transfer docs
Columns of glowing fibers rising on a glass plate like a live throughput chart
Beam Studio

Build data pipelines visually, on your own servers

Schedules, integrity checks, branches and retries, self-hosted.

Explore Studio
Glass workflow blocks linked by glowing lines, branching after a diamond-shaped decision
How BEAM moves data

Three primitives, one network

Send once, send to many, or keep exchanging. Pick a primitive to see what it does.

{{current.chip}}

{{current.title}}

{{current.text}}

{{s.k}}{{s.v}}
Read the docs →
Worked example

Copying 1 TB from Amazon S3 to four destinations costs $360 in egress alone. With BEAM, the source is read once: $130.10 in total.

4 sequential copies$360
BEAM fan-out$130.10

Amazon S3 internet egress at $0.09/GB (first 10 TB tier) for each copy, versus one read with BEAM plus $10/TB per destination and $0.10 per transfer. Illustrative, not a quote.

−64 % on this transfer Try your own numbers →
11–20 Gb/s measured on 100 GB transfers, public network telemetry
1× source read, whatever the number of destinations
40 MiB minimum chunk size, written directly to the destination
Pricing

Pay for what you move

Credits, no subscription. Pay by card in USD, or in TAO.

Open the console →
Transfers $10per TB moved
  • + $0.10 per transfer
  • Fan-out: one source read for every destination
  • No minimum, no contract
Rooms $0.50to start a Room
  • Messages and streams included
  • Files billed per receiving member
  • Partners join by invitation
Studio $0workflows, self-hosted
  • Runs on your Linux host with Docker
  • You pay only for the transfers it runs
  • Schedules, checks, retries, history
Integrations

Plugs into the stack you already have

SDKs in four languages, a self-hosted Studio, an MCP server for AI agents and onchain receipts for smart contracts. Nothing to migrate.

See all integrations →
Python SDK TypeScript SDK Go SDK Rust SDK Studio on Docker MCPMCP server Zapier Slack alerts Chainlink CRE · testing EVMOnchain receipts HTTPS endpoints REST API →
Security

Your keys and your data stay yours

Designed for the questions security and procurement teams ask first.

Read the architecture →

Credentials stay with you

Your SDK or self-hosted Studio signs short-lived access for each chunk. Workers never receive your storage keys.

Verified at arrival

Every part is checked at the destination before the object is finalized. Failed or slow chunks are retried elsewhere.

End-to-end encrypted Rooms

Objects and streams exchanged between agents in a Room are encrypted end to end with MLS. Workers only see ciphertext.

Scoped keys and budgets

Project-scoped API keys, key rotation, credit caps and monthly budgets with alerts. Usage exports through the management API.

In provider transfers, workers handle payload bytes in transit. Encrypt client-side, or use agent-only Room channels, for data no third party may read.

Ready to move data?

Run a proof of concept on your own data