Skip to content

Use case

Off-site archives and project close-out backups

Boita for archives and close-outs is a way to push project close-outs, CCTV retention sets and off-site copies at line rate, verify every file by checksum, and move cold data to an archive tier with a manifest and restore on demand — one use of Boita, the large-file transfer workspace for anyone who moves a lot of data.

An archive that arrives corrupt is not an archive. Boita moves close-out copies and CCTV retention sets at the speed of your connection, records a checksum for every file, and offers an archive tier with a manifest and restore on demand for data you must keep but rarely open.

Boita Agents: counts of agents, online, active jobs and errors, then a fleet table — a Docker sequencing node, a Windows render server, a Synology NAS, a macOS playout machine and a field kit — with host facts, the watch or sync job each runs, when it last reported and its error.
Agents: every server, container and NAS, what it runs and what went wrong.

Copies that need to arrive intact, not fast-ish

A finished production, a quarter of CCTV footage or a closed engineering project is a large, mostly static set of files that has to exist somewhere other than the office. Ordinary uploads of that size fail midway and silently deliver truncated files. Boita’s accelerated transfer engine holds your line rate over UDP, runs the job as parallel sessions, resumes by itself in the desktop app after a drop, sleep or restart, and never re-sends what is already on the server.

The server records a checksum for every file as part of the transfer and shows it in the file details. Compare it with your local copy and the archive is verified, not assumed.

A 5 TB project close-out on Scale, over a 1 Gbps office line, takes about eleven hours, line-limited: an overnight window. A 1 TB CCTV quarter on Pro over the same line takes about five hours, plan-limited at 450 Mbps. The calculator on the home page models your own line and distance.

Standing off-site copy with a watch folder

Point a watch folder at the archive share on your NAS and a folder in your workspace, from the desktop app or the headless Linux agent. New and changed files upload on their own once they have stopped changing, the queue runs in the background, and state is kept locally so a restart does not re-scan the whole tree. Allowed hours per folder and a workspace bandwidth window, enforced by the transfer server, keep the copy to overnight. Watch folders never mirror deletions: a Boita-side deletion is not applied to your NAS and a local deletion is not applied to Boita.

Trash, versions and quotas you can see

Deleted files and folders sit in the trash for a recovery window before the retention worker purges them, so a mis-click does not lose a close-out. When an upload replaces a file, the previous copy is kept as a version for the retention window. Storage usage is on every page with an email before you reach your quota. Plans include 10 GB to 10 TB of storage, custom above that, with no per-GB transfer fees on the way in or out.

An archive tier with a manifest

Aged deliveries and archive sets can be moved out of hot storage to the archive tier with a manifest, and restored on demand with the restore time shown (Scale and above); Enterprise adds retention rules per folder and legal hold. The archive tier is only ever a destination for cold data; transfers never run through it. A variant on decentralised storage with proof-of-storage is coming, on request; India-residency workspaces keep a domestic object-storage archive.

  • Line-rate transfers; desktop-app resume; nothing re-sent
  • Checksum on every file, visible in the details panel
  • Watch folders from a NAS share; allowed hours and bandwidth windows
  • Trash with a recovery window; versions when a file is replaced
  • Archive tier with manifest and restore (Scale and above)

Questions people ask

Boita for archives and close-outs, in answers.

Written the way people ask an assistant, and published the same way in products.json and llms.txt. More in the full FAQ.

How do I archive a finished project so I can prove it is intact?

Upload it with the desktop app or agent (checksum per file), then move it to the archive tier with a manifest; restore on demand verifies each file on return.

Can retention be enforced per folder?

Yes. Enterprise workspaces set retention rules per folder, and legal hold keeps a folder from being changed until the hold is lifted.

Is there a verifiable tier?

A verifiable archive with proof of storage is coming and available on request.

Is Boita a backup product?

Boita is a transfer and storage workspace. It is a good destination for off-site copies and close-out archives, with checksums, versions and a trash window, but it does not do snapshots, deduplication or bare-metal restore.

How do I know the archive copy is identical?

Every file shows the checksum the server recorded when it arrived. Compare it with the checksum of your local copy, or use the CSV verification report on a delivery receipt.

What is proof-of-storage?

A cryptographic proof, produced by a decentralised storage provider, that the data is still being held as agreed. Boita will record it on archived items when that archive backend ships.

Can archived data stay in India?

Yes. The archive tier is domestic object storage; a decentralised backend is optional and coming.

Next step

Try it, or ask first.

Start free with 10 GB and no card, book a demo, or talk to a person on WhatsApp. Leads from this page reach us with the page name attached, so the reply already knows what you read.

Tell us what you move

Sizes, where it goes, and what is slow today. A person replies with the plan and the setup that fit — no drip sequence.

Or write to hello@boita.io. Your details go to our team only; see the privacy policy.

Try it on your next transfer.

Create a free workspace with 10 GB, move one thing and watch it fill your line. Plans are flat and in your currency.

Chat on WhatsApp