Move files between your machines, folder to folder
Run the DocEvent Agent on two machines and files move folder-to-folder between them automatically. Both agents connect outbound over TLS and are managed entirely from the web console — no VPN, no port-forwarding, every file acknowledged and audited.
From
DocEvent Agent (on-prem)
To
DocEvent Agent (on-prem)
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 DocEvent Agent (on-prem) routing works
DocEvent Agent
A DocEvent Agent running on your own machine watches a folder and sends new files into the channel.
DocEvent Channel
DocEvent Agent
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Common use cases
Real workflows that teams automate with a DocEvent Agent (on-prem) → DocEvent Agent (on-prem) channel.
- Sync output folders between two offices, plants or data centres — no VPN
- Send files from your server to a customer's or partner's machine, folder to folder
- Feed a head-office ingest folder from many branch-office drop folders
- Manage both ends centrally from the web console — no local config anywhere
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 DocEvent Agent (on-prem) 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:
DocEvent Agent
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Files are delivered into a local folder on your own machine by the DocEvent 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)