Not yet.
Here is exactly where it stands.

epcis.dev has no hosted door. The capture gateway is written and passing its conformance tests; the durable cloud write path is being provisioned. Nothing is deployed, so there is no key to hold and no endpoint to call over the internet.

Two things you can do today, both real:

Get on the list for a capture key.

There is no hosted door to open yet. This is the one thing you can leave: an address and what you mean to point at the door, so that when the first hosted capture is live, you are the first to get a key.

What will you capture? Capturing from my own systemsYou POST EPCIS 2.0 events from a WMS, an ERP, or a line. You want a key and the schema. An agent captures for meA logistics agent captures and queries over MCP, with the same key a person would use. Migrating legacy XMLYou have EPCIS 1.1 / 1.2 / 2.0 XML and want 2.0 JSON-LD out, with a fidelity report per job. Evaluating conformanceYou want to check capture against GS1's official schema and the CBV 2.0 event hash. Building on the SDKYou want the library over the interface — the epcis2.js lineage — not raw HTTP. Reading events backYou query the standard interfaces and want minimally-scoped, append-only reads.

One address, one row. The people on the list are told first, and told once — no newsletter, no sequence, no call. The list lives on this origin and goes nowhere else.

Run the interface yourself.

The gateway runs locally under wrangler dev with its full durable substrate — the same capture, validation, event hash and error bodies as the hosted door will carry. It is the honest version of a demo: the part that is actually written. The dated ledger says exactly how much of it exists.

Validated. Stamped. Hashed. Appended. When the hosted door opens, the people on the list are told first, and told once.

The dated ledger →

Not yet.Here is exactly where it stands.

Get on the list for a capture key.

Run the interface yourself.

Not yet.
Here is exactly where it stands.