Metered by traffic, not by seat

Pricing

You pay for bytes that leave the edge. Storage during a transfer's lifetime, ingest, dedupe and the API are not billed separately.

Free
$0
For evaluating the protocol and moving the occasional build.
  • 50 GB egress per month
  • 5 GB per transfer
  • 8 blocks in flight
  • 7-day link lifetime
  • Community support
Start free
Team
$29/mo
For teams shipping masters, datasets and releases on a schedule.
  • 1 TB egress included, then $6/TB
  • 200 GB per transfer
  • 64 blocks in flight
  • Custom link policies and passwords
  • Audit log with 90-day history
  • Email support, next business day
Start free trial
Scale
Talk to us
For pipelines where transfer is part of the product.
  • Committed egress, from $3/TB
  • 2 TB per transfer
  • 512 blocks in flight
  • Private edge and bring-your-own bucket
  • SSO, SCIM and scoped keys
  • Support with response targets
Contact us

What counts as egress

OperationBilledNote
Upload (ingest)noIncluding retried and re-verified blocks.
Download by a recipientyesCounted once per delivered byte.
Deduplicated blocknoAn identical block already stored uploads as a no-op.
Range request / resumedelivered bytes onlyRestarting a download does not re-bill the part already sent.
API and webhooksnoRate limits apply; see the reference.
Overage is billed at the plan rate rather than blocking the transfer. Nothing stops mid-flight because a threshold was crossed.

Questions people actually ask

Can I self-host the client?

Yes. The reference client is permissively licensed and the protocol is documented in full — nothing in it depends on our binaries.

What happens when a plan lapses?

Links stop resolving and objects are erased on the normal expiry schedule. There is no grace period in which your data sits on our disks unpaid.

Do you keep the encryption keys?

No. They are derived in the client and travel in the URL fragment, which browsers do not send to servers. We cannot read an object, and neither can anyone who compels us.

Is there a hard transfer ceiling?

Per transfer, yes — see the table above. Across transfers, no: pipelines routinely chain sessions and reuse deduplicated blocks between them.