What ships today.
This page exists so the landing page can be read as a description rather than as marketing. It is dated, and it is the ledger the rest of the site is checked against.
Ledger date: 29 July 2026. epcis.dev has no hosted door. There is no public endpoint at this domain or any other, no issued key, no account, and no conformance attestation has ever been issued. The capture gateway is written and passing its conformance tests; it is not deployed anywhere. Locally it runs its full durable substrate under wrangler dev, with the same laws as the cloud path.
Implemented and under test
- EPCIS 2.0 capture and query interfaces, against the pinned official OpenAPI
- Validation against the official GS1 EPCIS 2.0 JSON schema, on every capture
- RFC 7807 errors carrying the standard's exception types
- The CBV 2.0 §8.9 event hash, checked against pinned reference vectors
- Gateway stamping, with caller-supplied values stripped
- Append-only storage law, minimally scoped reads
- EPCIS 1.1 / 1.2 / 2.0 XML → 2.0 JSON-LD translation, with fidelity reports
- An MCP door: capture / query / get_event / trace_epc / translate as tools
- The automated conformance suite over the GS1 test requirements (TCRs)
- GS1's normative artefacts vendored and pinned by digest, re-verified in CI
Not built — future tense everywhere on this site
- A hosted, public endpoint. There is no live door at this domain or any other
- Issued capture keys. There is no key to hold yet
- The durable cloud write path (Pipelines → R2 Iceberg) — the local substrate runs the same laws
- Identity resolution and attestation (nothing resolves a GS1 Digital Link to a party today)
- Published prices
- Hosted conformance attestations — none has ever been issued
- An SDK release on a public registry
- Users. There are none, and there are no logos, quotes or numbers on this site
How to read the two columns.
The left column is code that exists in a repository and passes its tests against GS1's normative artefacts, which are vendored and pinned by digest and re-verified in continuous integration. It is not a description of a hosted service you can call over the internet; it is a description of an interface you can run yourself. What you can check here is that this page never claims otherwise.
The right column is written in the future tense everywhere it appears on this site. If you find a sentence anywhere on epcis.dev that puts one of those items in the present tense, it is a defect, and it should be reported the way a defect is reported.
The standard.
epcis.dev conforms to EPCIS 2.0 and CBV 2.0 and claims nothing above them. GS1 is the standards body; GS1 has not reviewed, certified or endorsed this project. Where the standard leaves a choice open and we have made one, the conformance suite records it.