ANY SOURCE. ANY DESTINATION. NO SCRIPTS.
Route files from anywhere to anywhere
Connect a source — S3, HTTP, email, an SFTP or FTPS server DocEvent hosts for your partners to upload to, AS2, SharePoint, a scheduled pull from your own FTP or SFTP server or cloud storage (S3-compatible, GCS, Azure), or an on-premise folder — to any destination — an S3 or S3-compatible, Google Cloud Storage or Azure Blob bucket, FTP, SFTP, HTTP webhook, email, AS2, SharePoint, 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
Choose
To
Choose
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
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 uploaded to your DocEvent-hosted SFTP or FTPS server, is POSTed to an HTTP endpoint, arrives as an email attachment or as an AS2 message from a trading partner, is collected on a schedule from your FTP or SFTP server, a SharePoint document library or cloud storage (any S3-compatible bucket, Google Cloud Storage, Azure Blob, Azure Data Lake Gen2 or Azure Files), or is dropped in an on-premise folder watched by the Filerouter or DocEvent 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 — an S3 or S3-compatible, Google Cloud Storage or Azure Blob bucket, FTP, SFTP, HTTP, email, AS2, a SharePoint library, or a folder on your own server — with automatic retries on failure and a full audit trail.
Two ways in over SFTP and FTP
Either DocEvent hosts the server and your senders upload to it, or DocEvent connects to a server you already run and collects the files. Pick whichever side should hold the credentials.
PUSH - DOCEVENT HOSTS THE SERVER
Your senders upload to an SFTP / FTPS server we run
Create the source and DocEvent stands up an SFTP, SCP and FTPS server for it. Hand out logins to customers, partners or your own systems; every completed upload enters the channel and leaves the server straight away.
- SFTP and SCP on port 22, explicit and implicit FTPS - cleartext FTP refused
- Per-user passwords or SSH keys, an IP firewall, and a browser uploader
- Upload-only by design: nothing is stored on the server, nothing to poll
PULL - YOU RUN THE SERVER
DocEvent collects from an FTP or SFTP server you already have
Already receiving files on your own server, or a partner's? DocEvent connects to it on a schedule, collects the files that match a pattern, and deletes or moves each one once it is safely in the channel.
- Connects from static IP addresses you can allowlist - nothing to install
- Host-key verification for SFTP, TLS for FTPS, filename pattern filtering
- Minimum-age and size-stability checks skip files still being written
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, uploading to the SFTP or FTPS server DocEvent hosts for the channel, POSTing over HTTPS, sending an email, transmitting over AS2, saving into a SharePoint library, publishing to an FTP or SFTP server or cloud bucket DocEvent polls, or saving into a local folder watched by the Filerouter or DocEvent Agent.
Shared channel
invites · permissions · audit
Receiving out
You, a customer, or a partner — delivered to their S3, GCS or Azure Blob bucket, their FTP or SFTP server, their webhook, their inbox, their AS2 station, their SharePoint library, 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.
Two integrations worth a closer look
AS2 and SharePoint each carry more setup than a source and a destination box can explain — so they have their own pages.
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.