Deliver inbound AS2 messages into an on-premise folder
Receive AS2 messages from trading partners and have each verified payload written into a folder on your own server by the Filerouter agent. AS2, certificates and MDN receipts are handled in the cloud; the agent connects outbound over HTTPS, so no inbound ports are opened.
From
AS2
To
Filerouter (on-premise)
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
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
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 AS2 to Filerouter (on-premise) routing works
Source
AS2
Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.
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 AS2
A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
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 AS2 → Filerouter (on-premise) channel.
- Land partner EDI in the folder your on-site translator already scans
- Keep AS2 in the cloud and the documents on your own hardware
- Feed an air-gapped-by-default internal system with no inbound ports
- Replace an on-premise AS2 server but keep the same output directory
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the AS2 or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
AS2
A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.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 AS2
Other sources to Filerouter (on-premise)
- Amazon S3 → Filerouter (on-premise)
- HTTP Upload → Filerouter (on-premise)
- Email → Filerouter (on-premise)
- Filerouter (on-premise) → Filerouter (on-premise)
- FTP Pull → Filerouter (on-premise)
- SFTP Pull → Filerouter (on-premise)
- S3 Compatible (pull) → Filerouter (on-premise)
- GCS Blob Pull → Filerouter (on-premise)
- Azure Blob Pull → Filerouter (on-premise)
- Azure Data Lake Pull → Filerouter (on-premise)
- Azure Files Pull → Filerouter (on-premise)
- SharePoint → Filerouter (on-premise)
- DocEvent Agent (on-prem) → Filerouter (on-premise)