AS2 and an EDI VAN are not exact alternatives. AS2 is a communication protocol for sending secured messages directly between configured endpoints. A Value-Added Network (VAN) is a managed network service that can provide mailboxes, routing, partner connectivity, monitoring and sometimes translation or managed EDI operations.
The real decision is often whether to operate direct AS2 relationships, use a network intermediary, or combine both for different partners.
AS2 vs VAN at a glance
| Decision factor | Direct AS2 | EDI VAN |
|---|---|---|
| Model | Endpoint-to-endpoint protocol connection | Provider network and mailbox/routing service |
| Partner setup | Bilateral parameters and testing | Onboarding through provider capabilities |
| Message security | AS2 signing, encryption and MDN | Depends on protocol and service used by VAN |
| Routing | One configured partner profile per relationship | Provider may route among many participants |
| Translation | Separate EDI/integration function | May be included or sold as a managed service |
| Visibility | Your AS2 platform and partner evidence | Provider portal, reports and support |
| Commercial model | Infrastructure/service plus operations | Often subscription, mailbox, document or volume charges |
| Control | High control of endpoint and certificates | More operational responsibility delegated |
Compare actual provider proposals rather than treating every VAN or hosted AS2 service as identical.
What a direct AS2 connection provides
Direct AS2 creates a partner profile with endpoint URL, AS2 IDs, certificates, algorithms and MDN policy. Messages are addressed to the partner’s endpoint and receipts return between the AS2 systems.
This can provide:
- direct visibility of message and MDN status;
- control over certificates and partner settings;
- predictable integration with internal APIs or folders;
- fewer routing layers for partners that already support AS2;
- the ability to retain your own AS2 identity and endpoint design.
It also creates an operational responsibility. Someone must maintain availability, security updates, keys, certificate changes, alerts, retries, evidence and partner support. A managed AS2 service can operate that layer while preserving the direct AS2 protocol relationship.
What a VAN provides
A VAN typically receives documents into a managed network or mailbox and routes them to other participants using supported protocols. Services may include mapping, format conversion, partner onboarding, compliance reporting, archival and support.
A VAN can be valuable when:
- many partners already participate in the same network;
- partners use heterogeneous protocols;
- the business wants one provider to coordinate mapping and operations;
- mailbox and store-and-forward behavior fits the process;
- outsourced onboarding and support are more important than direct control.
Capabilities and fees vary widely. Ask which functions are included, which are additional managed services and what happens when the receiving partner uses a different network.
Security and evidence
AS2 defines message signing, optional encryption and MDN receipts. A signed MDN with a matching MIC gives protocol-level evidence linked to the specific AS2 message.
A VAN may use AS2 for one leg, SFTP for another or proprietary routing internally. Its portal can provide strong operational evidence, but the meaning depends on the service contract and each hop. Ask:
- which protocol protects each leg;
- where messages are decrypted or transformed;
- who controls private keys;
- which receipt is exposed to you;
- how end-to-end identity and integrity are demonstrated;
- how long raw evidence and payloads are retained.
Neither model removes the need for access control, certificate management, audit logs and incident response.
Onboarding and partner reach
Direct AS2 onboarding is bilateral. Both parties exchange parameters, test messages and coordinate production. This is efficient when the partner already publishes a mature AS2 process, but every new relationship still needs a profile and acceptance.
A VAN may simplify reach when it already connects to the partner. However, “the partner is on the network” does not guarantee that your required document type, business entity and routing relationship are ready. Confirm setup fees, partner lead times, testing and any interconnect dependency.
Use the AS2 trading-partner onboarding checklist to compare the work that remains in either model.
Cost comparison
Direct AS2 costs can include:
- hosted or self-managed AS2 platform;
- high availability and backups;
- certificates and key management;
- monitoring, logging and storage;
- staff time for onboarding and incidents;
- integration with ERP and EDI systems.
VAN costs can include:
- subscription or mailbox fee;
- document, kilocharacter or data-volume fees;
- partner setup and testing;
- mapping or translation;
- archival, support and premium SLA;
- interconnect charges or special routes.
Model a representative year with partner count, messages, average size, growth, support workload and change frequency. A low headline transport price can be outweighed by mapping work, while a higher managed fee can be economical if it replaces real operational effort.
Integration and data ownership
With direct AS2, your gateway commonly exposes an API, webhook, SFTP or watched-folder boundary to internal systems. You can design correlation and retention around your own architecture.
With a VAN, integration may use a provider mailbox, API, agent or managed mapping output. Review data export, audit access and termination terms. Ensure you can recover partner configuration, message evidence and business data in usable formats if the service changes.
When direct AS2 is a strong fit
Choose direct AS2 when:
- the trading partner mandates or strongly supports AS2;
- you want control of identity, certificates and transport evidence;
- partner count and onboarding workload are manageable;
- you already have EDI translation or do not need it;
- an API or file integration to a managed AS2 gateway fits your systems;
- predictable pricing and direct troubleshooting matter.
Direct does not require self-hosting. A cloud AS2 gateway can operate the endpoint and certificates while the protocol message still travels between the configured AS2 parties.
When a VAN is a strong fit
Choose a VAN when:
- it materially reduces onboarding across a large partner community;
- you need multiple protocols and routing models behind one service;
- managed mapping, translation and partner support are part of the need;
- mailbox/store-and-forward operation fits the business;
- the SLA and evidence model satisfy your requirements;
- the total proposal is better than assembling and operating separate components.
A hybrid model
Many organizations use direct AS2 for high-volume strategic partners and a VAN for smaller or heterogeneous relationships. Others connect their own AS2 endpoint to a VAN when a particular partner route requires it.
The integration layer should hide those transport choices from the ERP. Route by stable partner and document identifiers, then normalize technical and business states into one monitoring model.
Questions for a decision workshop
- Which partners mandate AS2, a named VAN or another protocol?
- How many new relationships are added each year?
- Do we already own EDI mapping and business validation?
- What transport and business evidence must we retain?
- Who will rotate certificates and respond to missing receipts?
- How are pricing and support affected by volume growth?
- Can we export configuration and evidence if we change provider?
- Which failure layer will each provider support?
The answer does not need to be universal. Choose the simplest supported route per partner while preserving consistent governance, correlation and monitoring.
Read how the AS2 protocol works and what an AS2 connection is before comparing implementation proposals. For a managed direct option, review AS2Connection pricing.
