Managed file transfer, actually managed
DocEvent is a managed file transfer operator. We run the secure endpoints your customers connect to and the channels your files move through — you own the storage, set the rules, and watch the audit trail. No MFT software to install, no servers to babysit.
Get started for free — our basic plan is free forever.
Any source to any destination
Every receive endpoint on the left can feed every send endpoint on the right — DocEvent sits in the middle, routing, retrying and logging each file. Rewire a flow whenever you like; nothing to redeploy.
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
FTP / FTPS
SFTP
Webhook
Email
Filerouterlocal filesystem
Agentlocal filesystem
We operate the transfer layer
Servers, protocols, patching, scaling, monitoring — that's our job. You configure users and routes in a dashboard; nothing for you to host.
Files land where you want
Everything is delivered into cloud buckets you own — S3, Azure Blob, Google Cloud Storage or any S3-compatible store. Your data never lives on our servers.
Partners manage themselves
Invite a customer to a channel and they attach their own endpoint, with their own credentials, and decide where their files go. Your only job is the invite.
What is managed file transfer?
Managed file transfer (MFT) is the reliable, audited movement of files between companies and systems — the invoices, statements, orders and data feeds that businesses exchange every day. Traditional MFT means buying software, hosting servers and managing every partner's credentials yourself.
DocEvent turns that into a service: we operate the transfer infrastructure, your files live in cloud storage you own, and the people you exchange files with manage their own side. You keep the control and the audit trail — and lose the servers.
Two ways your files move
Some transfers are people uploading and downloading. Some are systems talking to systems. DocEvent covers both, from one account.
People exchanging files: Simple FTP Service
A managed SFTP, FTPS and FTP endpoint on top of your own bucket. Give every customer their own account, folder and permissions — they connect with any FTP client, or straight from the browser with SFS Drive. IP firewall, SSH keys and a full audit log included.
Systems exchanging files: Channels
Event-driven routing between companies. Files arrive from S3, HTTPS uploads, email, an on-premise folder, or a scheduled pull from FTP, SFTP or cloud storage (S3-compatible, GCS, Azure) and are delivered to FTP, SFTP, webhooks, inboxes or another on-premise folder — automatically, with retries and deduplication. Invite partners onto either end of a channel; each party runs its own side.
Your customers pick where their files go
This is what makes DocEvent different from a classic MFT hub: a channel is shared. You don't collect anyone's FTP credentials or reconfigure anything when a partner changes systems — they own their end.
1
Create a channel and invite them
Set up a channel for the files you exchange and invite each customer or trading partner by email or DocEvent username. That's the whole setup on your side.
2
They choose their own target
Each member attaches their own endpoint under their own account — their FTP or SFTP server, their webhook, their inbox, their bucket — and can change it whenever they like, without asking you.
3
Files flow, hands-free
Every file is queued, deduplicated and delivered with automatic retries, and both sides see the delivery status and audit trail. No credential swapping, no support tickets, no finger lifted.
Every endpoint your partners already use
A managed file transfer platform is only as useful as the places it can reach. Files enter and leave DocEvent any of these ways — mix and match per user and per channel.
SFTP / FTPS / FTP
Managed protocol endpoints for people and legacy systems, backed by your own bucket.
Web browser
SFS Drive gives the same accounts file access from any browser — no client software.
Cloud buckets
Amazon S3, Azure Blob, Google Cloud Storage and S3-compatible stores like R2, Backblaze, Wasabi and MinIO — as SFS storage, or polled on a schedule as a channel source (S3-compatible, GCS Blob, Azure Data Lake Gen2, Azure Files).
HTTPS & webhooks
POST files in over HTTPS with an API key; deliver files out to any HTTP webhook.
Receive files as inbound email attachments and deliver files out as email, straight from a channel.
On-premise folders
The DocEvent filerouter is a small agent that connects a directory on your own server to a channel — files dropped in are sent, deliveries arrive as plain files.
Why hand file transfer to an operator
File transfer is critical, repetitive and thankless — exactly the kind of thing to run as a service.
- No file transfer servers to build, patch, monitor or scale — we operate them across three regions
- Every transfer is logged end-to-end: who, what, when, where it went and whether it arrived
- Failed deliveries retry automatically with back-off — no file is ever silently dropped
- Per-user accounts, IP firewalling, SSH keys and read-only permissions out of the box
- Partners and customers never share your credentials — everyone connects as themselves
- Your files stay in storage you own; leave any time and your data is already in your bucket
Every transfer, on every protocol, lands in one audit log.