Solutions
The business problem above the identity.
Software-composition review, regulated-supplier evidence and counterparty lookup all start from the same free SDK Passport. None of them is a certification, a score or an approval.
Solutions for SDK Passport holders
Software supply chain
SBOM & software-composition evidence
Turn software composition and provenance into evidence a buyer can actually review.
Boundary: An SBOM describes composition; it is not a declaration that software is secure.
Full pageRegulated finance
DORA ICT-vendor evidence
Prepare reusable ICT-vendor evidence for customers operating under DORA.
Boundary: ECZ-ID supports evidence preparation; it does not certify DORA compliance.
Full pageContextual · Counterparty
DCI — Digital Counterparty Infrastructure
Make a digital counterparty easier for people and machines to identify, inspect and re-check.
Boundary: DCI is identity and evidence infrastructure, not a counterparty risk score or approval.
Full page
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
SDK problems
Start from the problem you already have.
- One library across every registryRegistry channels and the source repository recorded as bindings, releases as history — never a second identity.Read more
- Publisher identity and provenanceWho publishes an SDK, and whether that is the same publisher as the last release — never a security audit of the code.Read more
- A customer's supply-chain reviewRelease provenance, SBOM and publisher evidence, organised into one buyer-ready pack.Read more
- Enterprise and procurementEstate, partner and procurement arrangements, agreed directly.Read more
