Operate the estate · ECZ-ID SDK
Dashboard
Where you operate everything you hold.
The Dashboard is the signed-in ECZ-ID console. It is where you manage your SDK Passports, bindings, publication, capacity and the capabilities you have added — for the whole organisation.
- Type
- Estate
- Price
- No charge to use; purchases happen in TrustOps
- Acquired and paid in
- TrustOps
- Operated in · proved by
- Dashboard · Resolver
The problem
Why it matters.
Identity work spread across emails, spreadsheets and several vendor portals is hard to keep current and harder to hand over.
Built for
- Owners of one or many Passports.
- Teams sharing an organisation's estate.
- Anyone who has added capacity or a paid capability.
What changes
- One place to operate the estate.
- Clear used-versus-available capacity.
- Badges, QR and share links to hand.
What you receive
Concrete deliverables, not a vague trust score.
- Every Passport your organisation holds.
- Bindings, their proof methods, publication and consent.
- Capacity and entitlements, as TrustOps holds them.
- Access to the capabilities you have added.
- Passports
- Your SDKs and libraries and other entities
- Bindings
- Per Passport, with sources, proof method and Last verified date
- Capacity
- AEC used versus available
- Capabilities
- What your entitlement includes
Illustrative structure. Your own estate appears after sign-in.
How it works
A short path from need to something usable.
Sign in.
Choose the Passport or estate view you need.
Make the change; Core writes it.
The Resolver projects what is public.
How it relates to your Passport
TrustOps acquires, the Dashboard operates, the Resolver proves, and Core writes the canonical truth. The Dashboard is the operating surface in that chain.
Use cases
- Recording a new registry channel as a declared binding when the SDK ships to another ecosystem.
- Checking capacity before onboarding a portfolio of client libraries.
- Copying the README badge for a newly published package.
Tiers and price
Nothing to buy here — this is where things are operated or bought.
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
Where it sits
TrustOps acquires
TrustOps holds the door, the purchase and the entitlement.
Dashboard operates
The Dashboard reads the entitlement and operates the estate.
Resolver proves
The Resolver publishes the current, public record.
Privacy, security and evidence
What is collected, published and kept.
- Access requires sign-in.
- Changes are written by Core and, where eligible, kept as LedgerCore evidence.
Boundaries
The claims stop here.
- The Dashboard operates what you hold; TrustOps owns what you buy.
- Nothing in the Dashboard changes what the public record proves beyond what Core writes.
Integrations and questions
Works with what you already run.
- TrustOps for purchases and entitlements.
- Resolver for the public projection.
- Developer Gateway for programmatic integration.
- Do I need to pay to use the Dashboard?
- No. Every free Passport holder operates their estate there.
- Can I buy things in the Dashboard?
- Purchases, payment and entitlement belong to TrustOps. The Dashboard shows and operates what you hold.
Related
- AcquireTrustOpsWhere every free Passport starts and every purchase happens.Read more
- Included free · Public proofResolverPublic, read-only proof of identity for your SDK or library, for anyone who asks.Read more
- ScaleAEC — Active Entity CapacityScale the estate you actively operate without turning capacity into identity.Read more
Start with a free SDK Passport.
£0 · No card required · Permanent, not a trial.