The assembly breaks if one file is missing
Mechanical, plant and product engineering teams exchange assemblies of thousands of part files that reference each other by relative path; a supplier who receives them flattened, or with one part dropped by a failed upload, opens a broken model. Point-cloud scans run to hundreds of gigabytes, CFD and FEA results to tens of gigabytes per case, and BIM coordination means a federated model going to every discipline weekly, with external references that only resolve if the folder layout survives.
Consumer sharing tools and browser uploads run over TCP, slow down with distance and stall at the last percent of a big folder; an FTP server keeps the structure but leaves no record of what arrived or who fetched it.
Whole trees, structure intact, verified
Boita moves a folder as a folder. Sub-folders, relative paths and file names arrive as they left, over an accelerated transfer engine that uses UDP with its own rate control to hold your line rate whatever the distance, in parallel sessions sized to your plan. Transfers checkpoint as they run and resume after any interruption; completed files are never re-sent.
The server records a checksum for every file, so a truncated part is caught at ingest rather than when the assembly fails to open. When an upload replaces a file, the previous copy is kept for the retention window and can be restored from Files. Numbered sets such as scan tiles or result frames show as one row with a gap warning, and move, copy and rename at scale are sequence-aware and verified before anything is deleted.
Fits the file server, the suppliers and the project
Point a watch folder on the file server, through the desktop app or the headless Linux agent, at the issue folder: whatever engineers drop there uploads on its own once it has stopped changing, and a download watch folder pulls returned parts back onto the server within a minute. Each supplier gets an upload portal with a form for job number, revision and required fields, so parts arrive labelled in their own dated inbox folder.
Projects group a job’s links, portals and deliveries with dates and status; search finds any file by name, tag, size, date or your own custom fields, and weekly searches can be saved. Folder permissions per member or group (Studio and above) let a supplier’s contact see one folder and nothing else.
A worked example
A 50 GB assembly of 4,000 parts goes to a supplier on Pro, over a 1 Gbps office line, in about fifteen minutes; the plan ceiling of 450 Mbps is the limit. A 400 GB plant scan on the same plan and line takes about two hours, plan-limited again. What the supplier sees on the way down depends on distance and loss on their side; the calculator on the home page models it.
- Folder trees with relative paths and names intact; nothing flattened
- Checksum on every file; version history when a file is replaced
- Watch folders up and down on the file server, desktop or Linux agent
- Upload portals with forms for suppliers; projects and custom fields
- Receipts that show who collected which revision, and when
Proof of issue
Every share link has an expiry, an optional password and a download limit, and the delivery receipt records who downloaded which file and when, with per-file checksums and a CSV verification report (PDF on Studio and above), which settles which revision a partner was working from. Recipient verification by email code names the person, and a revoked link stops resumed downloads within minutes.