Sync files between on-premise folders across sites
Folder-to-folder file transfer between servers at different sites — or different companies. Each side runs the small Filerouter agent over outbound HTTPS; DocEvent queues, audits and delivers every file with no VPN, port-forwarding or custom sync scripts.
From
Filerouter (on-premise)
To
Filerouter (on-premise)
Get started for free — our basic plan is free forever.
How Filerouter (on-premise) to Filerouter (on-premise) routing works
Filerouter
Files are picked up from a watched folder on your own server by the Filerouter agent and sent into the channel.
DocEvent Channel
Filerouter
Files are delivered into a local folder on your own server by the Filerouter agent.
1
File arrives via Filerouter (on-premise)
A small self-contained agent for Windows, macOS and Linux watches a local directory and sends each new file over HTTPS with an api-key. It waits for files to be fully written, filters by name or extension, and confirms every transfer — nothing is lost or sent twice.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to Filerouter (on-premise)
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Common use cases
Real workflows that teams automate with a Filerouter (on-premise) → Filerouter (on-premise) channel.
- Move files between two offices, plants or data centres without a VPN
- Send files from your server to a customer's or partner's server, folder to folder
- Replace ad-hoc site-to-site FTP links with one managed, audited channel
- Feed a head-office ingest folder from many branch-office drop folders
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Filerouter (on-premise) or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Filerouter
A small self-contained agent for Windows, macOS and Linux watches a local directory and sends each new file over HTTPS with an api-key. It waits for files to be fully written, filters by name or extension, and confirms every transfer — nothing is lost or sent twice.
Files are picked up from a watched folder on your own server by the Filerouter agent and sent into the channel.Destination:
Filerouter
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Files are delivered into a local folder on your own server by the Filerouter agent.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages
Related channel integrations
Other destinations from Filerouter (on-premise)
Other sources to Filerouter (on-premise)