Move files on-premise with Filerouter
Filerouter moves files between a folder on your own server and DocEvent, automatically. It's a small, self-contained program your users run on their own server — Windows, macOS or Linux — that watches a folder and moves files to and from a channel automatically. It's the on-prem companion to channels: alongside cloud storage, HTTP, FTP/SFTP and email, it adds "just watch a folder on my own computer." No server to host and nothing to install alongside it — download it, paste in an api-key, point it at a folder, and it just runs.
Set up Filerouter by creating a new channel →
Moves files both ways
- Send into a channel — Filerouter watches a local folder and, whenever a new file lands, sends it into your channel automatically. Once it's safely delivered the file is removed, or moved to an archive folder you choose.
- Receive from a channel — files coming out of a channel are saved straight into a local folder on that same machine.
- One simple setup per direction — each bridge is just a source, a destination and an api-key in one small settings file (
filerouter.yaml).
Only the right files, only when ready
- Pick just what you want — send only the files you name, by extension or prefix, and leave the rest alone.
- Wait for the whole file — Filerouter holds off until a file is fully written before sending it, so nothing half-finished goes through.
- Fit your schedule — restrict transfers to certain times of day.
- Stay within limits — cap how much bandwidth the agent uses.
Getting started
- Create an endpoint — under Channels in the console, create a Filerouter endpoint. The console generates a region and id, plus an api-key.
- Download the agent — grab the build for your operating system from the new Downloads tab under Channels.
- Point it at a folder — paste the region/id and api-key into
filerouter.yaml, choose your local folder, and start it.
Reliable and secure by design
Filerouter reaches out to DocEvent, so there are no ports to open on your network. It keeps track of what it has already handled and waits for DocEvent to confirm each file, so restarts, crashes and dropped connections never lose a file or send the same one twice. Each endpoint is protected by the api-key the console issues for it, and files move over encrypted HTTPS. The agent runs entirely inside your own environment, and nothing about your existing channels changes — this is simply one more way to feed and drain them.