Skip to content

Solution

Transfer files between offices with a watch folder at each site

Boita for transfers between offices is a watch folder at each site — new files at the sending office upload on their own, a download watch folder at the receiving office fills itself — over an engine that holds line rate across whatever distance separates the two — a job Boita, the large-file transfer workspace, is built for.

Two offices, one project. Boita’s desktop app runs a watch folder at the sending site so new files upload on their own, holds line rate across the distance between the two, and lets the receiving office pull from a workspace folder that both sides can see.

Boita Watch folders: presets for editing suites, and three folders — sequencer output, render farm finals and approved masters to playout — with destination, device, files and bytes sent, and last activity; below, auto-delivery rules to the workspace’s own buckets.
Watch folders: files leave the machine on their own, in either direction.

The inter-office problem

A studio with a Pune office and a Mumbai office, a practice with a head office and a site cabin, a company with a production unit in one country and a finishing unit in another: work moves between locations every day, and the tools usually in place were designed for one building. A VPN and a shared drive over TCP crawl over any real distance; cloud sync tools designed for documents choke on multi-gigabyte files and thousands of frames; and the manual answer, someone uploading a folder at the end of the day, depends on that someone.

A watch folder at the sending end

Install the Boita desktop app on a machine at the sending office and point a watch folder at the folder where finished work lands, mapped to a folder in your workspace. New and changed files upload on their own; a file is sent only after it has stopped changing for a set time, so something still being written never ships. New files are grouped into transfers rather than one session per file, state is kept locally so a restart does not re-scan the tree, and the queue runs from the menu bar or tray with the window closed.

Transfers run through an accelerated transfer engine over UDP with its own rate control, at your line rate regardless of the distance between offices, as parallel sessions sized to your plan. The desktop app resumes a dropped link where it stopped and completed files are never re-sent. Two watch folders come with Pro; Scale has no limit.

The receiving end

Members at the receiving office sign in to the same workspace and see the folder fill up in the Drive, with each file’s size, uploader and the checksum the server recorded on arrival. They download what they need through the desktop app at full speed, with the same resume. A download watch folder at the receiving office, on a desktop or through the headless Linux agent on the NAS, makes anything landing in the workspace folder appear locally within a minute, hands-free in both directions.

Each watch folder is one-way and the pair is not a two-way sync: a deletion at one office is not mirrored to the other.

Fits a company, not just a project

Both offices are members of one workspace with owner, admin and member roles, two-factor authentication and an audit log of who uploaded, downloaded and deleted what. Storage usage is shown on every page with an email before you reach your quota. Allowed hours per watch folder and a workspace bandwidth window, enforced by the transfer server, let the inter-office copy run overnight; include and exclude patterns are coming. Folder permissions on Scale and above keep each site to its own folders.

Plans are flat monthly amounts sized by storage, retention and seats, with no per-GB fees, so a daily flow between two sites costs the same on a busy week as a quiet one. Enterprise workspaces can auto-deliver from a workspace folder to their own transfer server or S3-compatible bucket.

  • Watch folder at the sending office; files ship as they finish
  • Line-rate transfers between sites; desktop-app resume; nothing re-sent
  • Download watch folder or Linux agent fills the receiving NAS
  • Allowed hours and bandwidth windows; two-way sync coming
  • Flat plans; roles, two-factor authentication and audit log for the whole company

Questions people ask

Boita for transfers between offices, 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.

Who uses this: a company with a design office and a manufacturing plant; a hospital group sharing imaging between sites; a research institute with two campuses; a firm with a DR site that must hold the day’s files; a survey company with a field office and a processing centre; a studio with two locations on one project.

How do I move files between two offices automatically?

Run Boita Desktop or the agent at each site: an upload watch folder at the sender and a download watch folder at the receiver, or `boita sync` for two-way mirroring on a schedule. Transfers hold line rate across the distance, and the desktop app resumes after drops.

Can both offices edit the same folder?

Yes, with the agent’s two-way sync: conflicts become conflict copies rather than overwrites, and a delete guard keeps a mistaken deletion from spreading.

Can we limit the bandwidth during office hours?

Yes. Bandwidth windows set allowed hours and rates per watch folder or sync, enforced by the server.

Do we need a VPN or a server of our own?

No. Both sites talk to Boita; nothing is exposed on either office network.

Is this a two-way sync between the offices?

No. An upload watch folder at one office and a download watch folder at the other move files in one direction each; nothing is deleted on either side. Two-way sync is on the roadmap.

Can both offices run watch folders into the same workspace?

Yes. Each machine with the desktop app can run watch folders into folders you choose. Pro includes two watch folders and Scale has no limit.

What about a site with a poor connection?

The desktop app holds whatever line rate the site has and resumes after every drop. Limit the watch folder to chosen hours and cap daytime transfers with a workspace bandwidth window, so the site connection stays free during the day.

Can it push straight to the other office’s server?

Yes, on Enterprise: pair a workspace folder with your own transfer server or S3-compatible bucket and every file that lands is pushed there within minutes, retried on failure. On other plans a download watch folder does the job from the receiving machine.

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