Land inbound AS2 documents in a folder on your own machine
Receive AS2 messages from your trading partners and have the DocEvent Agent write each decrypted, verified payload into a folder on your own machine — the folder chosen from the web console. Outbound TLS only, every file acknowledged, full audit trail.
From
AS2
To
DocEvent Agent (on-prem)
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 DocEvent Agent (on-prem) 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
DocEvent Agent
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Common use cases
Real workflows that teams automate with a AS2 → DocEvent Agent (on-prem) channel.
- Deliver partner EDI into the directory your ERP polls
- Pick the destination folder remotely from the web console
- Run AS2 as a managed service with on-premise file delivery
- Keep trading-partner documents inside your own network
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 DocEvent Agent (on-prem) 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:
DocEvent Agent
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
- Amazon S3 → DocEvent Agent (on-prem)
- HTTP Upload → DocEvent Agent (on-prem)
- Email → DocEvent Agent (on-prem)
- Filerouter (on-premise) → DocEvent Agent (on-prem)
- FTP Pull → DocEvent Agent (on-prem)
- SFTP Pull → DocEvent Agent (on-prem)
- S3 Compatible (pull) → DocEvent Agent (on-prem)
- GCS Blob Pull → DocEvent Agent (on-prem)
- Azure Blob Pull → DocEvent Agent (on-prem)
- Azure Data Lake Pull → DocEvent Agent (on-prem)
- Azure Files Pull → DocEvent Agent (on-prem)
- SharePoint → DocEvent Agent (on-prem)
- DocEvent Agent (on-prem) → DocEvent Agent (on-prem)