Resumable by default
Every upload is cut into 64 MB parts with independent checksums. Lose your connection at 91% and the client picks up exactly where it stopped — days later if it has to.
FileBeam moves 200 GB build artifacts, raw camera footage and nightly database dumps between people, CI runners and cold storage — encrypted, resumable and addressable over a plain REST API.
All regions operational · 99.98% uptime over the last 90 days
Moving data every day for teams at
Most tools were built for a 4 MB attachment. We built ours for the 40 GB one that has to survive a hotel Wi-Fi and a mobile hotspot on the same journey.
Every upload is cut into 64 MB parts with independent checksums. Lose your connection at 91% and the client picks up exactly where it stopped — days later if it has to.
Keys are derived in the browser with AES-256-GCM before the first byte leaves the machine. Our storage nodes hold ciphertext and a content hash — nothing that can be read back.
42 points of presence terminate the TLS session close to the sender, then push over our own backbone. Median first byte across Europe sits at 118 ms.
Everything the dashboard does is one REST call away: create a transfer, stream parts, rotate a link, revoke it. Signed URLs work with plain curl and any S3-style client.
Set a wall-clock deadline, a download budget, or both. Expired objects are unlinked from the index within 60 seconds and purged from disk on the next sweep.
Every download is logged with an IP, an ASN and a user agent, exportable as newline-delimited JSON or streamed straight into your SIEM over a webhook.
One token, three endpoints. Push nightly artifacts from CI, hand a customer a one-time link from your own backend, or mirror a bucket without babysitting a shell script.
# 1. open a transfer curl -X POST https://api.filebeam.lol/v1/transfers \ -H "Authorization: Bearer $FILEBEAM_TOKEN" \ -d '{"name":"nightly","expires_in":604800}' # 2. stream the payload, part by part curl --upload-file build.tar.zst \ "$UPLOAD_URL&part=1" # 3. seal it and hand out the link curl -X POST "$TRANSFER_URL/seal" \ -H "Authorization: Bearer $FILEBEAM_TOKEN" # => https://filebeam.lol/d/8Kq2vHt4
import { Beam } from "@filebeam/sdk"; const beam = new Beam(process.env.FILEBEAM_TOKEN); const t = await beam.transfers.create({ name: "nightly", expiresIn: 604800, maxDownloads: 3, }); await t.upload("./build.tar.zst", { partSize: 64 * 1024 * 1024, onProgress: (p) => console.log(p.percent), }); console.log(await t.seal());
from filebeam import Client beam = Client(token=os.environ["FILEBEAM_TOKEN"]) t = beam.transfers.create( name="nightly", expires_in=604800, recipients=["ops@example.com"], ) with open("build.tar.zst", "rb") as fh: t.upload(fh, part_size=64 << 20) print(t.seal().url)
We keep the smallest amount of data that still lets a transfer work, and we can tell you exactly what that is.
Content keys never reach our infrastructure. A transfer link carries the key fragment after the URL hash, so it is never sent to the server on download either.
Expiry unlinks the object from the index immediately and the storage sweep reclaims the blocks within 24 hours. Backups inherit the same TTL — no orphan copies.
Every workspace gets its own KMS key and its own storage prefix. Cross-tenant reads are impossible by construction, not by an access-control check.
No seat maths, no annual lock-in. Storage is billed by the gigabyte-day, egress by the gigabyte.
For one person moving the occasional big thing.
Shared workspace, API tokens and audit export.
Dedicated egress, private regions, DPA and SLA.
FileBeam is in a closed beta while we finish the abuse pipeline. Every account is reviewed by a human before the first upload is allowed, which keeps the platform out of the phishing-hosting business. Requests are usually answered within two business days.
No. A transfer link works in any browser and with curl. Only the sender needs a workspace. If a transfer is marked confidential, the recipient will additionally be asked for the passphrase you set.
The object is unlinked from the index within 60 seconds and stops resolving. Storage blocks are reclaimed by the next sweep, which runs every six hours. Expired transfers cannot be revived — re-upload is the only path.
Primary storage sits in Frankfurt and Helsinki with erasure coding across three availability zones. Enterprise workspaces can pin a region and disable replication outside it.
Team and Scale workspaces can serve links from a domain you control. Point a CNAME at edge.filebeam.lol and we issue and rotate the certificate for you.
Request access and we will get back to you with an invite code.
Uploads are tied to a workspace so links can be revoked later. Free accounts get 5 GB and 7-day links.