Versions, deadlines and too many recipients
A single commercial ends up as a family of files: a 4K master, cut-downs for each length, broadcaster-specific versions, social crops, a DCP for cinema, and the rushes and project files that made them. Each goes to a different party, often in a different city, and most of them are due at once. Consumer file-sharing links stall over distance because they run over TCP, and a browser upload that fails at the last percent of a 200 GB master costs an evening.
Couriered drives work until one is lost, a lab receives a corrupt copy, or the wrong version ships.
One link per recipient, at full speed
Boita moves data with an accelerated transfer engine over UDP with its own rate control. A transfer climbs to your line rate and holds it whether the broadcaster is across town or the lab is abroad. Big deliveries run as parallel sessions sized to your plan, and in the desktop app a dropped link or a closed laptop resumes by itself rather than restarts.
Send a share link per recipient with an expiry, an optional password and a download limit, straight from Boita by email with a message. The recipient opens a clean page, sees the file list and sizes and downloads without creating an account. The sender dashboard shows who viewed and downloaded which file, so you see which broadcaster has collected its version.
Rushes in, masters out
An upload portal is a request link a production company or DIT uses to send rushes, camera originals or a director’s cut into a folder you choose. Each upload lands in its own dated inbox folder with the sender’s name attached, on a token that can write to that folder only, and both sides get an email when it completes. Nobody with a portal link can see anything else in your workspace. From a browser an interrupted upload starts again; for large rushes the page offers the free desktop app, which resumes.
For labs and finishing houses, a watch folder in the desktop app turns a delivery folder into a standing instruction: a DCP or master dropped there uploads on its own once it has stopped changing, and a render that is still being written never ships half-done.
Proof that the right version landed
The server records a checksum for every file at transfer time and shows it in the file details, so a lab can confirm the DCP it received is the one you sent. Every link can be revoked in seconds; download tokens expire in minutes, so a superseded version stops being downloadable the moment you pull it. Delivery receipts list files, checksums, timestamp and who downloaded, as a PDF on Scale and above.
A 200 GB graded master is one file: one session, 45 Mbps, about ten hours. Sent as picture, stems and sidecars, the ten sessions carry them together in about an hour. Plans are flat monthly amounts, billed in INR with GST invoices in India and in your own currency elsewhere, with no per-GB fees and no charge when a broadcaster downloads a version twice.
- Line-rate transfers over distance; parallel sessions per plan
- One share link per recipient, with expiry, password and download limits
- Sender dashboard: who downloaded which version, and when
- Upload portals for rushes and camera originals
- Checksums on every file; receipts and branded pages on Scale and above