FAQ
Questions, answered plainly.
What a free Plugin Passport costs, what it identifies, who can check it, what you would ever pay for — and what an ECZ-ID is not.
Getting started
- What does a free Plugin Passport cost?
- £0. It is permanent, not a trial, and no card is required. You pay only if you later add scale, assurance or specialist products.
- What does one Plugin Passport identify?
- One Plugin Passport is one logical plugin, extension, action or store app your organisation publishes. Releases, versions and individual store listings of that plugin are not separate Passports.
- Where do I get one?
- In TrustOps, which owns every free door and every purchase. Each family's free door opens there when TrustOps publishes it as open; this site explains the Passport and never issues an identity itself.
- Do I need an organisation record first?
- No. Your organisation's ECZ-ID Business Passport — Declared — FREE is reused if you have one, or created with your first Passport. It is the Parent every Passport hangs from.
- What can every organisation hold, free?
- Every organisation starts with one ECZ-ID Business Passport — Declared — FREE. Each of the seven family Passports — Agent, MCP, Plugin, API, IoT, SDK and Service & Workload — is free, and is taken in TrustOps once TrustOps publishes that family's door as open. Historical and specialist Passport products remain honoured for the organisations that hold them. They are not the launch acquisition model, and no family site offers them as a door.
Proof and publication
- Who can check the record for my plugin?
- Anyone. Once you consent to publication, the Resolver serves the record as a page and as JSON, with no account and no key.
- What does the badge prove?
- It is a route to current proof: one click opens the live Resolver record. It is not a safety, quality, approval or certification mark.
- Is publication automatic?
- No. Nothing becomes public until you consent, and you can withdraw publication later.
- Is a verified binding verified for good?
- No. A binding is verified as of its Last verified time, and the record shows its Freshness. ECZ-ID does not renew a bound binding: once its proof method's freshness window has passed, the result is history and a new binding is the fresh proof. Re-check before reliance.
Paid capabilities
- What would I ever pay for?
- Capacity to operate more entities (AEC), a stronger organisation tier (Parent VERIFIED or ASSURED), monitoring, evidence, relationship intelligence, change awareness, business solutions and specialist digital products. All are optional.
- Where do prices come from?
- From the commerce projection TrustOps publishes. This site shows what that projection says on the date it was built, and TrustOps decides what can be bought at the moment of purchase.
- Does paying make my plugin more verified?
- No. Payment ≠ proof. A paid capability changes what you can operate. A paid Parent tier opens ECZ-ID's checks on your organisation — never on the plugin — and the record shows VERIFIED or ASSURED only after they pass; payment alone changes nothing on the public record.
What a Passport is not
- Does the Plugin Passport verify the plugin?
- A DECLARED record states what your organisation says. A VERIFIED or ASSURED Parent verifies your organisation, not the plugin. A binding completed through a live proof method shows control of the bound asset as of when it was last verified; it certifies nothing about the plugin itself.
- Does ECZ-ID replace my existing identity systems?
- No. It complements your frameworks, protocols, OAuth, cloud IAM and workload identity, and stays outside the execution path.
- Does ECZ-ID enforce anything at runtime?
- No. OBSERVED ≠ ENFORCED. ECZ-ID records and publishes; it does not block, allow or approve anything in your runtime.
Six distinctions the estate keeps
- OBSERVED ≠ ENFORCED
- An observed state records what was seen, and when. ECZ-ID does not sit in your execution path and enforces nothing at runtime.
- Passport ≠ Binding
- The Passport is the one enduring identity. A binding records an asset it is known by; adding one never creates a second identity.
- Binding ≠ Authority
- A binding records that a relationship was declared or evidenced. It does not grant, prove or imply authority to act.
- Binding ≠ Certification
- A verified binding shows control of an asset when it was last verified. It certifies nothing about the asset's safety, quality or compliance.
- Payment ≠ Proof
- Buying a capability changes what you can operate. Payment alone never changes what the public record proves: a paid Parent tier opens ECZ-ID's checks on your organisation, and the record shows VERIFIED or ASSURED only after they pass.
- Badge = route to proof
- A badge is a link to the current Resolver record. It is not a certification mark, a safety rating or an approval.