PrincipalNew, messages, attachments, MDN, analytics and bulk actions over real stations.
One AS2 platform
to operate, integrate and scale without losing context
The public entry point today is Free. You can create an account, receive an initial station with an echo partner, test send and return with MDN, and validate documentation, apiDocs and basic technical access over a real operating surface.
Certificates, signature, encryption, compression, firewall rules and technical governance without leaving the product.
Public API, webhooks and scoped SFTP so other systems fit in without losing control.
What Free makes visible from day one
Pending receipts, acknowledgements and traceability in the same message context.
Certificates, CSR, import and renewal without leaving the product.
SFTP, API and webhooks with visible scope, tokens and audit trail.
Console, health, analytics and support over real stations.
Start with Free and validate the product today
Right now the only public plan is Free. It is designed to validate real operations, not to browse a static demo: signup, initial station, echo partner, sending, MDN and a basic technical surface from day one.
Instant signup, two stations, self-signed certificate, echo partner, operations console and public documentation.
Free already lets a team verify the full use case without waiting for other plans or for an assisted demo.
If you want to validate the product before exploring everything, follow the short path and jump straight into stations, partners, certificates and sending.
Evaluate AS2Expert today without getting lost in the page
If you are here to decide whether Free fits, use these shortcuts and jump straight to signup, flow, evidence and apiDocs.
Open public signup and activate the initial environment with a station, echo partner and real operating surface.
Open signupSee the short path with onboarding, sending, MDN return and first operating steps.
View flowJump to screenshots, docs and verifiable points before entering the app.
Go to evidenceCheck contracts and routes if you are coming from integration or from a technical team.
Open apiDocsValidate AS2Expert Free in under an hour
If you just need to know whether the platform fits, you do not need to read the whole site first. This is the short path: signup, initial station, echo partner, send with MDN, then open the technical surface.
Create identity and station
Activate the account, enter the app, review the initial station and understand the operating context from PrincipalNew and Settings.
Test sending and return
Use the echo partner, send a document, inspect attachments, raw.eml and verify the real message flow behavior.
Validate AS2 security
Review certificates, signature and encryption policy, and confirm how MDN is presented inside daily operations.
Open the technical surface
Walk apiDocs, functional docs and access paths like SFTP to validate that the technical side shares the same model.
Everything needed to operate AS2 without dropping to SQL
The platform is built for the daily work of an operator and for the automation required by an integrator. It does not split configuration, operations and technical access into unrelated products.
Station-centered context
Each AS2 identity gets health, partners, certificates, analytics, technical access and related messages inside the same operating frame.
Real message operations
Dense grids, bulk actions, sending, export, attachment download, raw EML and protocol context from PrincipalNew.
Unified configuration
Partners, endpoints, MDN, signature, encryption, compression, FTP/SFTP, webhooks, firewall controls and certificates live where they belong, without arbitrary jumps between screens.
Integration-ready surface
Bearer token API, outbound webhooks, SFTP VirtualFS and WebDAV VirtualFS to fit other systems without inventing external gateways or losing the security model.
MDN, signature, encryption and access control inside the same product
AS2Expert lets the team govern PKI, transport, receipts, technical access and observability from the same operational backend.
MDN and traceability
Set the MDN mode per partner, detect pending receipts in analytics and keep the receipt context attached to the real message.
Signature, encryption and compression
Each B2B relationship can define digital signature, partner-certificate encryption and zlib compression from the UI or the public API.
Certificate lifecycle
Generate self-signed certificates, import existing ones, work with CSR and renew without pushing PKI outside the product.
Firewall, scopes and audit trail
Partners with firewall controls, station-scoped SFTP access, webhook secrets, API tokens and auditable technical actions in one place.
AS2 security that operators can see and integrators can actually use
This is not a black box. The platform exposes the elements that matter when a B2B exchange fails or must be audited.
Operable MDN
Receipts do not disappear into transport logs: they are monitored, listed and used to detect real pending exchanges.
Integrated PKI
Certificates, CSR, renewal, import and binding to stations and partners inside the same product.
Scoped technical access
Per-station SFTP, rotatable credentials, visible scopes and audit trail for sensitive actions.
Transport controls
Signature, encryption, compression, endpoint, firewall, webhook and API routes are defined where the team actually operates.
What the Free plan includes today
This is the real public offer right now. The other plans belong to the roadmap, but today the question is whether Free is enough to validate your AS2 operation.
AS2Expert Free
The current public entry point is meant to validate the full operational flow over a bounded environment.
- 2 visible stations
- 100 MB storage
- 100 messages per month
- echo partner included
- MDN, signature and encryption
- apiDocs, API and base SFTP
Plan roadmap
Pro and Enterprise will come later. They are not public signup options yet, so the site should present them as future evolution rather than current offers.
- more volume and more stations
- more governance, observability and rollout
- more automation and assisted support
What teams usually ask before putting AS2 into production
The decision is not only about whether a message goes out. It is about receipts, certificates, firewall rules, technical access and support capacity when something drifts.
Can MDN be operated visibly?
Yes. AS2Expert brings together the message, protocol detail, MDN pending items and station context so receipts do not stay hidden outside daily operations.
What about signature, encryption and certificates?
The product covers certificate creation, import, CSR, rotation and binding, plus signature and encryption policy per partner.
How are firewall rules and technical access governed?
Webhooks, API, SFTP and partner transport settings live with visible scope, audit trail and operable station and partner configuration.
How does support scale during incidents?
Operations, integration and support share the same context for messages, health, analytics and access, reducing bounce between teams.
The same platform serves operations, integration and support
AS2Expert does not force each team into a different tool. Operators, integrators and technical owners start from the same context.
AS2 operator
Work from PrincipalNew, review messages, attachments, MDN, errors and bulk actions without dropping into backend tooling or SQL.
Integrator / IT
Open API, webhooks, SFTP or WebDAV over the same data model, permissions and traceability layer.
Security / PKI
Control certificates, signature, encryption, renewal, CSR and B2B bindings from one operable surface.
Support / observability
Use health, analytics, MDN pending items, logs and station context to reach the real fault faster.
Why launch AS2 with AS2Expert instead of loose scripts
The real cost is not sending a payload. It is sustaining certificates, receipts, visibility, technical access and support when something breaks.
Less fragmentation
Stations, partners, certificates, messages and automation live together. No more splitting context across spreadsheets, scripts and shells.
More visible security
MDN, signature, encryption, firewall, secrets and tokens are not hidden in scattered config: they are part of daily operations.
Less dependence on single experts
The platform reduces reliance on the one person who knows the right script or exact table when an urgent incident appears.
More room to scale
You can start on Free and grow into Pro or Enterprise without rebuilding the operating model or changing technical channels.
AS2Expert versus manual AS2 operations
Sending a payload is the easy part. Sustaining certificates, MDN, visibility, technical access and support under load or during an incident is the real cost.
| Area | Manual ops / loose scripts | AS2Expert |
|---|---|---|
| Station context | Split across scripts, spreadsheets and shells | Station, partners, messages and health in one surface |
| Certificate lifecycle | Ad hoc import and rotation, expert-dependent | Operable creation, import, CSR, renewal and binding |
| MDN and traceability | Receipts and pending items scattered or invisible | MDN, pending items and detail attached to the real message |
| Technical access | Credentials and scripts without visible scope | API, SFTP and webhooks with scope, tokens and audit trail |
| Support and incidents | Manual hunting across logs and tables | Console, analytics, health and ready operational context |
| Scalability | Each new partner adds more friction | Same operating model from Free to Enterprise |
The return does not come only from sending messages, but from sustaining operations with less friction
When AS2 stops depending on scattered scripts, the benefit appears in incidents, onboarding, configuration changes and support continuity.
Less time to the real fault
Health, analytics, MDN, message detail and station context reduce diagnosis time when a delivery fails.
Shorter onboarding
A new station does not force you to rebuild the operating model. Certificates, partners, sending and technical access start from a common base.
Less fragile changes
Rotating a certificate, changing an endpoint or reviewing a webhook stops being a handcrafted operation dependent on shell work and tribal memory.
Shareable support
Operations, integration and support read the same context. The incident stops bouncing between teams without traceability or visible proof.
Each area covers a concrete operational concern
AS2Expert is no longer just a message inbox. The product exposes dedicated modules for identity, transport, security, operations and integration.
Stations
CoreAS2 ID, technical email, security defaults, health and operating context for each identity.
Partners
B2BDefine how you talk to each third party: remote AS2 ID, endpoint, MDN, signature, encryption, transport and automation.
Certificates
PKICreate, import, rotate and use certificates inside the same product, then attach them to stations and partners.
PrincipalNew
OpsMain console to operate inbound and outbound messages with bulk actions, detail, attachments and manual sending.
Analytics
ObservabilityMetrics, pending items, volume and ranking so teams can detect anomalies and decide where to drill down.
SFTP VirtualFS
Technical accessTechnical access to messages and controlled upload with station scope, audit trail and delegated management from the UI.
WebDAV VirtualFS
HTTP accessHTTP/WebDAV access to the same virtual model, useful for lighter integrations and clients that fit DAV better than SSH.
Webhooks
Outbound eventsOutbound callbacks to push events to other systems with test, logs and traceability from the partner sheet.
Public API
DeveloperPublic routes for stations, partners, certificates, messages, send and webhooks with Bearer token.
How an operator enters and sends an AS2 message
The short route starts in PrincipalNew: choose the station, open Send, select the partner, attach the document and deliver it with the agreed security policy.
How a team works with AS2Expert
The product supports the real cycle: onboarding, configuration, testing, daily operations, automation and support.
Complete flow of an AS2 operation
The same platform covers the route from initial signup to automated integration and later observability.
1. Create station
Set up the AS2 identity, technical email, base certificate and security defaults.
2. Configure partners
Each partner defines remote AS2 ID, endpoint, MDN, signature, encryption, webhook and extra transport when needed.
3. Prepare certificates
Certificates are created or imported, attached to stations, and reused in specific B2B relationships.
4. Send and receive
PrincipalNew concentrates manual sending, download, review, bulk actions and traffic visibility.
5. Open technical channels
SFTP, WebDAV, webhooks or API are enabled depending on what the third party or internal team needs.
6. Monitor and adjust
Analytics, dashboard and logs help detect bottlenecks, MDN pending items, partner failures and support needs.
Five access surfaces over the same backend
Each channel solves a different use case, but all of them share the same data model, station, partner, permissions and traceability.
Operational UI
Rich screens for human operations and guided support.
API
Programmatic integration with Bearer token and public routes aligned with apiDocs.
SFTP
Virtual filesystem with station scope, audit trail and controlled upload.
WebDAV
A similar virtual model, useful for clients and automations that fit HTTP/DAV better.
Webhooks
Outbound HTTP events to push changes into other systems.
The same platform serves operators and integrators
AS2Expert lets one team work from the console and another one consume API, webhooks, SFTP or WebDAV over the same backend.
Quick API example
import requests
API_TOKEN = "<token>"
headers = {
"Authorization": f"Bearer {API_TOKEN}",
"Content-Type": "application/json"
}
response = requests.post(
"https://www.as2expert.com/api/v1/messages",
headers=headers,
json={"limit": 25}
)
print(response.json())
Navigable documentation
The public site already links functional docs and apiDocs so human operations and technical integration are documented separately.
Traceability, scope and governance
The platform does not treat technical access as an external add-on: station scope, audit, certificates, MDN and automation are part of the same model.
You do not have to trust the promise: you can walk the product and technical surface today
The public site already exposes real operational evidence: navigable documentation, public apiDocs, Free access and functional flows to validate how AS2Expert is operated.
Operational docs
Walk through stations, partners, certificates, SFTP, webhooks and analytics with real screenshots and module-based navigation.
Open DocsPublic apiDocs
Review routes, payloads and API contracts to integrate messages, partners, certificates and automation.
Open apiDocsFree entry point
Create an account and test the real surface with stations, echo partner, sending, security and day-to-day operations.
Enter FreeComplete flow
Follow onboarding, configuration, sending, MDN, technical access and support from the documentation itself.
View flowHow the same model evolves from Free into serious operations
The point is not to rebuild operations when volume grows. The point is to keep the same surface and harden governance, automation and support in layers when those plans become available.
Free: validate the model
Account, station, echo partner, sending, certificates, MDN and first technical routes over a contained operation.
Pro: expand automation
More throughput, more stations, more operational governance and more integration surface without changing tools.
Enterprise: govern at scale
Observability, governed technical access, controlled rollout and priority support when AS2 is already critical infrastructure.
Start today on Free and turn AS2 into a governed operation
Activate your environment, create stations, test against echo, validate MDN, signature and encryption, then open API, SFTP or webhooks without leaving the same operational backend.
Crea tu cuenta Free
Activa tu entorno AS2 real: estacion inicial, partner ECHO, envio con MDN y acceso a la consola. Sin tarjeta, sin compromiso.
Tu entorno Free incluye 2 estaciones, 100 MB, 100 mensajes al mes, un certificado autofirmado y un partner ECHO para pruebas. Para interoperar con partners externos, importa un certificado CA-signed desde la consola.