Collect files from S3-compatible buckets into an on-premise folder
DocEvent polls any S3-compatible bucket — Cloudflare R2, MinIO, Backblaze B2, Wasabi or Amazon S3 — and delivers every new file into a folder on your own server via the Filerouter agent. Outbound HTTPS only — no VPN, no scripts, fully audited.
From
S3 Compatible (pull)
To
Filerouter (on-premise)
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
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 S3 Compatible (pull) to Filerouter (on-premise) routing works
Source
S3 Compatible
DocEvent checks your S3 or S3-compatible bucket on a schedule and collects new files — Cloudflare R2, MinIO, Backblaze B2, Wasabi and more.
DocEvent Channel
routes · retries · logs
Destination
Filerouter
Files are delivered into a local folder on your own server by the Filerouter agent.
1
File arrives via S3 Compatible (pull)
Scheduled polling of any bucket that speaks the S3 API — Amazon S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, Supabase Storage and friends (custom endpoint URL and path-style addressing supported). Collects from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No bucket notifications or event plumbing needed.
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 Filerouter (on-premise)
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Common use cases
Real workflows that teams automate with a S3 Compatible (pull) → Filerouter (on-premise) channel.
- Pull partner bucket drops into the folder your ERP already watches
- Land R2, B2 or Wasabi files on your own server without download scripts
- Collect from MinIO or hosted object storage into a local processing directory
- Distribute files published in a central bucket to branch-office servers
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the S3 Compatible (pull) or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
S3 Compatible
Scheduled polling of any bucket that speaks the S3 API — Amazon S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, Supabase Storage and friends (custom endpoint URL and path-style addressing supported). Collects from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No bucket notifications or event plumbing needed.
DocEvent checks your S3 or S3-compatible bucket on a schedule and collects new files — Cloudflare R2, MinIO, Backblaze B2, Wasabi and more.Destination:
Filerouter
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Files are delivered into a local folder on your own server by the Filerouter 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 S3 Compatible (pull)
Other sources to Filerouter (on-premise)