Integration & Gateways
AS2 gateway for EDI partners, cloud storage, file service, natural-language AI assistant.
These modules form the perimeter where OpenEPCIS meets the rest of the enterprise. Trading partners send EDI over AS2, older systems drop files into an S3-compatible bucket or Azure Blob, and operators ask the AI assistant natural-language questions about what is in the event store. All of this is part of the Business edition.
In practice the AS2 gateway carries the most traffic. Partners send EPCIS-XML envelopes, and the gateway validates them and hands them to /capture. The MDN response that goes back includes the EPCIS capture-job ID, so AS2-level acknowledgement and EPCIS-level processing stay reconciled and nobody has to chase a correlation by email. Partner certificates and trading-relationship metadata are stored in a database, so onboarding a new partner is a REST call, and partners who prefer not to wait for a manual setup can use a self-service enrollment flow.
Object storage is pluggable. Any S3-compatible store and Azure Blob are first-class options, so a captured EPCIS document can be archived to whatever the customer's environment already uses (AWS S3, on-prem object storage, Azure) without a separate bucket or changes to the capture pipeline.
The AI assistant routes each prompt by intent. It classifies the prompt into one of a small set of intents (EPCIS query, Digital Link resolution, vocabulary lookup, general chat) and dispatches it to a typed handler that returns structured data, such as a translated query, a resolved URL or a vocabulary record, together with the natural-language answer. The default model runs locally on Ollama, so there is no third-party LLM dependency unless the customer explicitly connects one.
The rules of the rest of the platform apply here too. An AS2 envelope, an S3 file backfill and an AI-translated query all pass through the same validation, hashing, Digital Link normalisation, tenant scoping and role enforcement as direct REST traffic. Integrations are additional ways into the conformance contract and are bound by it.
Capabilities by edition
| Capability | OSS | Business |
|---|---|---|
| AS2 gateway for EDI partners | — | ✓ |
| S3-compatible storage | ✓ lib | ✓ |
| Azure Blob storage | — | ✓ |
| File upload / download service | — | ✓ |
| AI assistant (Ollama-backed, intent-routed) | — | ✓ |
See also
- Architecture → Authentication: how partner-facing services plug into the platform's identity model.
- Modules → EPCIS Events: what AS2 inbound documents end up as.