Route files from anywhere to anywhere
Connect a source — S3, HTTP, email, or an on-premise folder — to any destination — FTP, SFTP, HTTP webhook, email, or an on-premise folder. Configure once. Every file is delivered automatically, with retries, audit logs, and zero code. Send and receive yourself, or invite customers and partners to either end of the channel.
From
Amazon S3
To
FTP
Get started for free — our basic plan is free forever.
How channels work
A channel is a named route from a receive endpoint to a send endpoint. Files flow through automatically.
1
File arrives
A file lands in your S3 bucket, is POSTed to an HTTP endpoint, arrives as an email attachment, or is dropped in an on-premise folder watched by the Filerouter agent. The channel receives it instantly.
2
Channel routes it
DocEvent's channel server matches the file to your configured route. Files are queued, deduplicated, and prepared for delivery.
3
Delivered reliably
The file is pushed to your destination — FTP, SFTP, HTTP, email, or a folder on your own server — with automatic retries on failure and a full audit trail.
One channel, many parties
The sender and the receiver don't have to be the same account. A channel is a shared route: you can put yourself on both ends, or invite another company to one end while you keep the other.
Sending in
You, a customer, or a trading partner — dropping files into S3, POSTing over HTTPS, sending an email, or saving into a local folder watched by the Filerouter agent.
Shared channel
Receiving out
You, a customer, or a partner — delivered to their FTP or SFTP server, their webhook, their inbox, or a folder on their own server.
- Invite anyone by email or DocEvent username — they join the channel on their own account
- Each member manages their own endpoint and credentials; you never exchange passwords or keys
- Per-member permissions control who may send into and who may receive out of the channel
- Both sides see the delivery status and audit trail for the files they exchange
Learn how shared channels work — invites, permissions, fan-out to every member, and migration/replication patterns.
All channel integrations
Pick a source and destination to see exactly how that integration works, what teams use it for, and how to get started.
Built for reliability
Automatic retries
Failed deliveries are automatically retried with exponential back-off. No file is ever silently dropped.
Full audit trail
Every file that enters a channel is logged end-to-end — source, timestamp, size, destination, and delivery status.
No code required
Configure sources and destinations through the UI. No custom Lambda functions, no glue scripts, no infrastructure to manage.
Share with partners
Invite a customer or trading partner into your channel. They connect their own endpoint under their own account — no credential swapping.