Deadlines do not care about distance
A broadcaster in one city, a post house in another and a platform ingest point on a third continent: the same package has to arrive at all of them, intact, before a cut-off. Ordinary TCP uploads slow down with distance and stumble at every lost packet, so the last few percent of a large master can take longer than the first ninety.
Boita’s accelerated transfer engine uses UDP with its own rate control. It fills your connection and holds that rate over any distance, and it runs large packages as parallel sessions so one delivery can use everything your plan allows.
Proof of delivery, not a hope
Every file carries the checksum the server recorded when it arrived. The sender dashboard shows views and downloads per file and per recipient, so you know a delivery landed and who collected it. Delivery receipts list files, sizes, checksums, timestamp and who downloaded, with a CSV verification report, and as a PDF on Scale and above.
Every share link has an expiry, and you can add a password and a download limit. Download tokens are minted per download and expire in minutes, so revoking a link stops new and resumed transfers immediately. Recipient verification by one-time email code names who downloaded, and a deadline priority lane makes other transfers give way to the one that is due.
A 400 GB mezzanine package on Pro, over a 1 Gbps line, is on the server in about two hours when it arrives as a set of files the plan’s ten sessions can carry at once; wrapped as one file it moves in a single session at 45 Mbps and takes far longer; a 1 TB episode drop on Scale over the same line takes about two and a quarter hours, line-limited. The calculator on the home page models your own line and distance.
Standing deliveries without scripts
A watch folder in the desktop app turns a delivery folder into a standing instruction: whatever lands here goes there. It survives restarts, only sends files once they have stopped changing, and never re-sends what is already on the server. For platforms that receive from many suppliers, an upload portal gives each supplier a request link that drops their package into its own inbox folder with an email to both sides, and delivery specs flag off-spec files on arrival.
Enterprise workspaces auto-deliver anything landing in a folder to their own transfer server or S3-compatible bucket, and any workspace on Pro and above drives Boita from a pipeline through scoped API keys and signed webhooks.
Security that a compliance team can read
Transfer sessions are encrypted end to end by the engine, web and share pages are HTTPS only, and each workspace has its own storage root and encryption key. Two-factor authentication and a per-workspace audit log of logins, shares, downloads and admin actions are on every plan. Single sign-on, SCIM, audit export to a SIEM and malware scanning on arrival are on Enterprise; workspace policies cap link expiry and require passwords today, with enforced MFA and allowed recipient domains coming.
- Line-rate transfers over distance, parallel sessions per plan
- Checksums on every file; receipts with a verification report, PDF on Scale and above
- Expiry, password, download limits, recipient verification and instant revocation
- Watch folders and upload portals for standing supplier deliveries
- Audit log, two-factor authentication; SSO on Enterprise