Logistics data your auditors can verify.
EPCIS 2.0 capture, per-field PII encryption, multi-party attestations and a public Merkle transparency log — supply-chain truth that does not depend on trusting us.
EPCIS 2.0 repository
Capture and query supply-chain events in the GS1 EPCIS 2.0 shape (implemented subset documented honestly). API-key scoped, audit-logged.
EPCIS docs →Teams, roles & SSO
Multi-org workspaces with owner / admin / member roles enforced server-side, single-use email invites, and a client-visible audit log. Bring your own identity provider over OpenID Connect (OIDC) — configure it in the panel.
Set up your team →Cryptographic transparency
Every shipment timeline is hash-chain sealed; all seals anchor into a public, append-only Merkle log. Verify any proof offline with the open-source tjverify CLI — no TrackJet trust required.
The tjvt2 / tjmt1 specs →Multi-party attestations
Ed25519-signed statements (picked up, received OK, damaged, handover) bound to the sealed timeline — a tamper-evident chain of custody.
Verification surface →PII vault & crypto-shredding
Third-party email metadata is encrypted per-field (XSalsa20-Poly1305); account deletion shreds keys so data becomes unreadable, with a receipt.
Privacy engineering →Operational fortress
Owner-togglable read-only degradation, weekly restore drills against real backups, integrity-sealed audit logs, self-hosted cookieless analytics.
How we operate →Open standards
tjvt2 (verifiable timeline), tjmt1 (transparency log) and the status ontology are published specs — implement them, audit them, or hold us to them.
Read the standards →