Send files from an on-premise folder to SFTP servers securely
Watch a folder on your own server and deliver every new file to an SFTP server automatically. The Filerouter agent sends completed files into a DocEvent channel over HTTPS, and DocEvent pushes them on over SFTP with SSH-key or password auth.
From
Filerouter (on-premise)
To
SFTP
Get started for free — our basic plan is free forever.
How Filerouter (on-premise) to SFTP 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
SFTP Server
Files are pushed securely to an SFTP server over SSH.
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 SFTP
SSH key or password authentication. Standard port 22. Configurable remote path.
Common use cases
Real workflows that teams automate with a Filerouter (on-premise) → SFTP channel.
- Deliver files written by on-premise systems to bank or insurer SFTP portals
- Automate regulated file submissions straight from a local output directory
- Replace cron-and-script SFTP uploads with a reliable watched folder
- Send point-of-sale or plant-floor data to partner SFTP servers overnight
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 SFTP 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:
SFTP Server
SSH key or password authentication. Standard port 22. Configurable remote path.
Files are pushed securely to an SFTP server over SSH.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 SFTP