Skip to content
ECZ-IDSDK

Included free · Relationships · ECZ-ID SDK

Digital Entity Graph

See how your SDK or library relates to the entities around it.

Every free Passport takes part in the Digital Entity Graph: the operator behind the SDK or library, the places it is bound and the ECZ-ID subjects it is published as related to.

Type
Included free
Price
£0 — included with every free Passport
Acquired and paid in
TrustOps
Operated in · proved by
Dashboard · Resolver

The problem

Why it matters.

Your SDK or library depends on other things and is depended on in turn. Without a shared model, those relationships live in diagrams nobody else can check.

Built for

  • Anyone tracing who operates what.
  • Reviewers mapping dependencies across a supplier's products.
  • Organisations with several related Passports.

What changes

  • Relationships that resolve, not just diagrams.
  • One model across every entity family.
  • A path from any node to its own current record.

What you receive

Concrete deliverables, not a vague trust score.

  • Basic participation in the Digital Entity Graph with every free Passport.
  • Operator and binding relationships on the public record.
  • Links from each related subject to its own record.
Your SDK or library in the graph
Node
ECZ-XX-XXXXXX::SDK_PASSPORT-XXXXXX
Operated by
Your organisation's ECZ-ID Business Passport — the Parent
Bound to
The public places where it appears
Related to
API Passports, where published

Illustrative structure with placeholder values.

How it works

A short path from need to something usable.

  1. Every Passport names its operator.

  2. Bindings and published relationships join the graph.

  3. Each node resolves to its own record.

  4. Graph Intelligence adds estate views; ECZ-ID Watch tells followers when something changes.

How it relates to your Passport

The Graph is built from records Core writes. Graph Intelligence (paid) turns it into estate views in the Dashboard; ECZ-ID Watch can follow changes to it.

Use cases

  • Most SDKs wrap an API. The API keeps its own identity, whichever SDKs call it.
  • SDKs are the building blocks of plugins, and each plugin is identified in its own right.
  • Libraries run inside services and workloads, which are separate enduring subjects.

Price

Included free, with every Passport.

£0. It is part of the free SDK Passport — permanent, not a trial, and no card is required.

After you take it

  1. TrustOps acquires

    Take the free Passport in TrustOps; your organisation's ECZ-ID Business Passport — Declared — FREE is reused or created.

  2. Dashboard operates

    Operate it in the Dashboard: publish, bind and copy your proof links.

  3. Resolver proves

    Anyone resolves the current record on the Resolver.

Privacy, security and evidence

What is collected, published and kept.

  • Only eligible, published relationships are public.
  • Private operating context stays private.

Boundaries

The claims stop here.

  • A published relationship is not an endorsement.
  • Related Passports are suggested, never issued for you.

Integrations and questions

Works with what you already run.

  • Every ECZ-ID Passport family.
  • Graph Intelligence for estate views, and ECZ-ID Watch for change.
Is the Graph a paid product?
Basic participation is free with every Passport. Graph Intelligence adds estate views and is configured in TrustOps.
Will related Passports be created for me?
No. Each is its own free identity, taken with its own deliberate click.