One gateway. Every protocol your trading partners require.
Archr.Hermod exchanges business documents with your trading partners over ebMS, AS2, or large-file SFRM — signed, encrypted, and delivered end-to-end — and gives them a secured papiNet REST API too, so you stop maintaining a different tool for every partner's required standard.
Your system → Archr.Hermod → Trading partner
- Create the business document
- Create the cryptographic signature
- Encrypt the message using the partner's certificate
- Transmit over to the partner's required protocol
- Partner decrypts and verifies
- Delivery acknowledgement sent back to you, so you have proof of delivery
Every trading partner has their own rules
One partner requires ebMS with a signed CPA. Another only accepts AS2 with a specific MDN configuration. A third needs large files moved reliably, in chunks, over a proprietary protocol. Without a gateway, that's a separate integration — and a separate place your security posture can drift — per partner.
Without a gateway
- A separate integration built and maintained per trading partner
- Signing and encryption implemented (and re-verified) once per integration
- No single place to see traffic across partners or protocols
- Onboarding a new partner means starting a new project
- A partner who wants a REST API means building and securing one against your internal systems
With Archr.Hermod
- One gateway speaking ebMS, AS2, and SFRM
- Signing and encryption handled consistently, in one place, for every partner
- One dashboard showing message traffic and partner activity across protocols
- Onboarding a new partner means adding a partnership record
- A papiNet REST API for your partners, served from the same gateway and carried over your message queue
Speak whatever protocol your partner requires
Configure a partnership once — endpoint, certificate, protocol-specific settings — and Archr.Hermod handles the rest: envelope construction, signing, encryption, delivery confirmation, and retry.
ebMS 2.0
The ebXML Messaging Service — SOAP-based, CPA-driven, with built-in reliable delivery.
Read the technical reference →AS2 (RFC 4130)
MIME-based messaging over HTTP/HTTPS with S/MIME security and MDN receipts.
Read the technical reference →SFRM
Large files cut into segments, each checked with a checksum, optionally signed and encrypted, and acknowledged when the whole file has arrived.
Read the technical reference →A modern API for your trading partners — without exposing your systems
papiNet is the paper and forest-products industry's standard for supply-chain messages. Archr.Hermod publishes the papiNet REST API as a secured HTTPS front door, and carries each call over your message queue to the system that holds the data. Your back end never faces the internet, and it does not have to speak HTTP to anyone.
Partners call you
One endpoint for every operation in the papiNet document, with the exact version in the address. Each partner has its own API key and attributes. Requests are validated against the specification before your system sees them, and several versions can run side by side.
How the API works →You call partners
Your applications send a request naming the partner and the operation. Archr.Hermod chooses the endpoint, attaches the credentials, makes the call and returns the answer. The partner's URL and key stay in Archr.Hermod, not in every application.
The outbound hub →Connect your back end
Plain JSON messages on NATS or Kafka, with typed contracts for .NET, TypeScript, Java and Python, and ready-made adapters and clients for .NET Framework, Java, Node.js and Python applications. A development responder lets partners start before your back end is ready.
Connecting a system →One call, step by step
- A partner calls
GET /papinet/4.0.0/supplier-orderswith its API key. - Archr.Hermod checks the key, the caller's attributes and the request against the papiNet document.
- The request is published on your message queue, with a correlation id and a deadline.
- Your back end answers on the reply topic with the data its own rules allow that caller.
- Archr.Hermod returns the answer — or
504if none arrives in time — and records the call.
Everything is switched on and off by an administrator: versions, individual operations, and the whole API.
Works with your ERP & Back-end systems
If your ERP or warehouse system is written in Java, you do not have to build the integration yourself. The Java toolkit is part of Archr.Hermod and runs on Java 8 and later. We also include toolkits for .NET, TypeScript and Python. It uses Kafka as its message queue today, and we plan to include NATS JetStream into the toolkit in the very near future. In any case, the integration with your ERP and back-end systems is handled by the toolkit, in what ever language you wish to use, The choice is yours.
Answer the papiNet API
Serve each papiNet operation with a handler in your own code. The toolkit does the queue, the deadline and the reply, and tells you who is calling and what the administrator set up for them.
Call your partners
Name the partner and the operation, and Archr.Hermod makes the call. Your code never holds a partner's address or key, and every outcome (delivered, refused, timed out) is a value, not an exception.
papiNet classes, ready to use
Request and response classes for every papiNet version, generated from the standard's own documents with the same names as the .NET, TypeScript and Python ones.
The Java toolkit →Developer guides, with code in C#, Java, TypeScript and Python: what the SDK holds for each language, serving the API from your back end and calling trading partners.
Signed and encrypted, by default — not by discipline
Every outbound message is signed with your private key and, where the partnership calls for it, encrypted to the partner's certificate. Every inbound message has its signature verified before it's accepted. The same guarantee holds across all three protocols, even though the wire format differs underneath.
Sign
Outbound messages are signed with your private key — proof they came from you.
Encrypt
Messages are encrypted to the partner's certificate, so only they can read the contents.
Verify
Inbound signatures are checked before a message is ever accepted as valid.
See your traffic, not just trust that it moved
An operator dashboard tracks message rates and trading-partner activity per protocol, so a stalled transfer or an unexpected drop in traffic from a partner is something you notice, not something you find out about later.
Message rate per hour
Messages by remote partner
Illustrative sample data — this page has no connection to a running Archr.Hermod instance.
Modern, inspectable, actively developed
Archr.Hermod is built on .NET, with source you can read rather than a black box you have to trust. Standards compliance — ebXML 2.0, RFC 4130, CMS/PKCS#7, and the papiNet REST API — is handled once, centrally, instead of re-implemented per integration.
Ready to see it in action?
Read the technical reference for the protocol your next partner requires, or reach out to talk through your integration.