Builds get bigger; the deadline does not move
Game studios move a lot of large files on a schedule: nightly builds to an external QA team, milestone builds to a publisher, submission packages to platform holders, and asset packs and source art to and from outsourcing partners. A modern build runs to tens of gigabytes; a milestone with symbols runs to hundreds, and the publisher is usually on another continent.
Consumer file-sharing tools and browser uploads run over TCP, which slows with distance and halves its rate at every lost packet, so the nightly build lands in the morning, or fails at 95 percent and needs a producer to restart it.
Nightly builds that ship themselves
Point a watch folder in the Boita desktop app at the build server’s output folder and a folder in your workspace. Each new build uploads on its own once the build system has finished writing it; a file is sent only after it has stopped changing for a set time, so a half-written package never ships. State is kept locally, so a restart does not re-upload last week’s builds. Two watch folders come with Pro; Scale has no limit.
Uploads run through an accelerated transfer engine over UDP with its own rate control, at your line rate regardless of distance, as parallel sessions sized to your plan. After a sleep or reboot, the watch folder sends what is left once the desktop app is open. Allowed hours per watch folder are live; include and exclude patterns, so a watch folder skips intermediate files, are coming.
A 60 GB nightly build on Pro, over a 1 Gbps office line, is on the server in about eighteen minutes, plan-limited at 450 Mbps; a 200 GB milestone with symbols takes about an hour. The calculator on the home page models your own line.
One link per QA vendor or publisher
Send each build as a share link with an expiry, an optional password and a download limit, by email from Boita with the build notes as the message. The QA lead opens a page and downloads without an account; the sender dashboard shows who downloaded which build and when. Revoke a link the moment a build is superseded: download tokens expire in minutes, so a pulled build stops being downloadable immediately.
Assets coming back from an outsourcing partner arrive through an upload portal, a request link into a folder you choose; each delivery lands in its own dated inbox folder with the sender’s name attached and an email to both sides.
Verified builds, flat pricing, pipeline hooks
The server records a checksum for every file at transfer time and shows it in the file details, so QA can confirm the package they are testing matches the one the build server produced. Two-factor authentication and a per-workspace audit log are on every plan, and recipient verification by one-time email code names who downloaded. Plans are flat monthly amounts with no per-GB fees and free re-downloads, so ten testers fetching the same 60 GB build costs nothing extra.
Scoped API keys and signed webhooks (Pro and above) let the build pipeline create the share and learn when the publisher downloads it; the headless Linux agent and the boita CLI run the upload from the build server itself.
- Watch folder on the build server output; nightly builds ship on their own
- Line-rate transfers over distance; automatic resume in the desktop app
- One link per vendor with expiry, password, download limit and instant revocation
- Checksums on every file; audit log and recipient verification
- API keys, webhooks, the Linux agent and the boita CLI