From an Agent-watched folder to a Filerouter folder
The DocEvent Agent watches a folder on one machine; DocEvent delivers each new file into a folder on another server running the Filerouter agent. Site-to-site, folder-to-folder transfer over outbound connections only — no VPN, fully audited.
From
DocEvent Agent (on-prem)
To
Filerouter (on-premise)
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
FTP / FTPS
SFTP
Webhook
Email
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How DocEvent Agent (on-prem) to Filerouter (on-premise) routing works
DocEvent Agent
A DocEvent Agent running on your own machine watches a folder and sends new files 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 DocEvent Agent (on-prem)
Enroll the agent once and manage everything from the web console — browse the machine remotely to pick the watched folder, with no local config files. It connects outbound over TLS (no inbound ports) and confirms every transfer.
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 DocEvent Agent (on-prem) → Filerouter (on-premise) channel.
- Move files between two sites when each runs a different DocEvent connector
- Send files from a console-managed Agent machine to a partner running Filerouter
- Feed a Filerouter delivery folder from an Agent-watched source folder
- Bridge machines across companies without VPNs or port-forwarding
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the DocEvent Agent (on-prem) or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
DocEvent Agent
Enroll the agent once and manage everything from the web console — browse the machine remotely to pick the watched folder, with no local config files. It connects outbound over TLS (no inbound ports) and confirms every transfer.
A DocEvent Agent running on your own machine watches a folder and sends new files 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 DocEvent Agent (on-prem)