The problem with ordinary uploads
Consumer file-sharing tools and browser uploads run over TCP. Every lost packet halves the rate, and the further the far end is, the longer it takes to recover. A 2 TB delivery from Pune to a client in Los Angeles can take days that way, and a dropped connection at hour nine often means starting again.
Studios have worked around this with couriers, hard drives and late nights. The Founder ran a 3D rendering business where deliveries of 10 to 20 TB per job were normal, and a transfer tool that held line rate over distance was the difference between hitting a deadline and missing it.
What Boita does differently
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 other end is across town or across an ocean. Big jobs run as several parallel sessions, the number set by your plan, so a single delivery can fill a fat office pipe.
In the desktop app, a dropped link, a closed laptop or a reboot picks up where it stopped by itself, and completed files are never re-sent. The server records a checksum for every file at transfer time and shows it in the file details, so a delivery is checked rather than assumed.
Frames leave the farm as they finish
Point a watch folder in the desktop app at your render output and a folder in your workspace. New and changed files upload on their own, and a file is only sent once it has stopped changing, so a half-written frame never ships. State is kept locally, so reopening the app does not re-upload the whole sequence. Two watch folders come with Pro; Scale has no limit.
When the render finishes, the last frames are already on the server. Send the client a share link with an expiry, an optional password and a download limit; they open a clean page, see the file list and download without creating an account.
Receiving plates and camera originals
Half of a post house’s traffic is inbound. An upload portal is a request link that lets a DIT, a client or a vendor upload straight into a folder you choose. Each upload lands in its own dated inbox folder on an upload-only token scoped to exactly that folder, and both sides get an email when it completes. Clients never see the rest of your workspace.
Built for sequences
Drive understands image sequences: shot_010.####.exr is one row with the frame range, count, size and a gap warning, in Files, on the phone and on share pages, with codec, resolution and frame rate in the details panel. Previews render for images, PDFs and video, and delivery receipts carry per-file checksums with a CSV verification report, as a PDF on Scale and above.
A 2 TB shot delivery on Scale, over a 1 Gbps line, takes about four and a half hours, line-limited; on a 2.5 Gbps line about two hours, plan-limited at 2.25 Gbps. The calculator on the home page models your own line and distance.
- UDP-based acceleration at your line rate, parallel sessions sized to your plan
- Automatic resume in the desktop app; completed files never re-sent
- Watch folders with a stability wait, restart-safe, batched sends
- Share links with expiry, password and download limits; no recipient account
- Upload portals with per-upload inbox folders
- Checksums recorded on arrival; receipts with a verification report