Skip to content
ECZ-IDIoT
Free Passport: Get a FREE IoT Passport

ECZ-ID IoT Device Passport™

Give connected products an identity that survives their operational lifecycle.

For manufacturers and operators of connected products, device models and fleets. One public ECZ-ID per device connects the product, the organisation accountable for it, its bindings and its current proof — through deployment, service, software change, change of owner or custodian, and retirement. Safe to print: never a raw serial number, MAC address or location.

Get a FREE IoT PassportVerify an ECZ-IDBuild and integrate(opens in a new tab — developers.ecocitizenz.com)

£0 · No card required · Permanent, not a trial.

Everything included with one FREE IoT Passport

Identity
ECZ-XX-XXXXXX::IOT_DEVICE-XXXXXX
Operator
Your organisation's ECZ-ID Business Passport — Declared — FREE, created if you do not have one
Public proof
Resolver page + machine-readable JSON, open to anyone
Share
Live website badge + QR code + share link
Connections
Basic bindings + Digital Entity Graph participation
Operate
Lifecycle/current state on demand + claim/recovery + essential LedgerCore evidence
Price
£0 — no card required — permanent, not a trial

The website badge is the same live-proof pattern EcoCitizenz uses in every site footer: click it to reach current Resolver proof. DECLARED information is self-declared; re-check the live record before relying on it.

Free IoT Passport

What your free IoT Passport establishes.

One IoT Passport is one physical device, or one device identity module, operated by your organisation. A fleet is many Passports. Firmware versions, MAC and IP addresses, and the gateways and hubs a device registers with are not separate Passports.

Free · Permanent · No card

The ECZ-ID launch model

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.

ECZ-ID Business Passport — Declared — FREEParent · created with your first family Passport

Other free starts

  • Free WatchFollow up to three ECZ-IDs on this device and see what changed, with no account and no email.Use Free Watch
  • Free Trust CheckCheck a public URL: we read its public signals and match them to the free Passport families by fixed rules. Advisory; nothing is created.Run the free check

Included, at £0

  • A persistent ECZ-ID for the connected device.
  • Your organisation on the record as its operator. Its ECZ-ID Business Passport — Declared — FREE is created if you do not already have one. About the Parent
  • A public Resolver record anyone can open, and the same record as machine-readable JSON. About the Resolver
  • A badge, a QR code and a share link. About badges and QR
  • Basic bindings to the public places where your connected device already appears. About bindings
  • Lifecycle and current public state, evaluated on demand. About PulseGuard
  • Claim and recovery.
  • Basic participation in the Digital Entity Graph. About the Graph
  • Essential lifecycle evidence, kept in LedgerCore. About LedgerCore
  • Publish Kit for a device-label QR and your fleet manifest.
  • 25 actively managed devices included for your organisation.
  • Manage from your ECZ-ID account.

Publishing the record is your decision. Nothing becomes public until you consent, and you can withdraw publication later.

One device, one Passport

For example, each smart meter in a fleet has its own Passport; a firmware update, a new IP address or a new gateway is not a new one.

A new MAC address, IP address, firmware version, gateway or hub registration is not a new Passport.

What the record never blurs

DECLARED ≠ VERIFIED
A DECLARED record states what your organisation says about itself, with the date it said it. It is not the outcome of an independent check.
Passport ≠ Binding
The Passport identifies the connected device. A binding records a public place where it already appears. Adding a binding never creates a second identity.
Binding ≠ Authority
A binding shows that a relationship has been declared. It does not grant, prove or imply authority to act.
Parent verification ≠ IoT verification
A VERIFIED or ASSURED Parent verifies your organisation. It does not verify the connected device.
Get a FREE IoT PassportRead everything included

Why, and how it works

From Passport to verified binding.

Why your connected device needs an ECZ-ID, and exactly what happens between taking the Passport and relying on a verified binding.

  • One identity for the device's whole life

    One IoT Passport is one physical device, or one device identity module, operated by your organisation. A fleet is many Passports. Firmware updates, new gateways, a change of operator — the ECZ-ID stays the same.

  • Accountability anyone can re-check

    A public Resolver record and its JSON name the organisation that answers for the device — for installers, buyers and software, with no account and no key.

  • Beside the device identity you already run

    £0, permanently. Platform identities and certificates keep authenticating the device; ECZ-ID stays outside the execution path and never connects to it.

Lifecycle continuity

One device, one ECZ-ID — from the factory floor to retirement.

Everything around a connected product changes over its life: where it is installed, who services it, what software it runs, who operates it. The identity — and the record of who answers for the device — stays the same, and stays resolvable.

Same ECZ-ID at every stage

ECZ-XX-XXXXXX::IOT_DEVICE-XXXXXX

Never a raw serial number, MAC address or location.

  1. Make

    Manufacture and commission

    What changes: The device is built, its model and documentation are published, and it gets its platform credentials.

    The record: The device's ECZ-ID is issued with your organisation on the record as the accountable operator, bound to its product page and documentation.

  2. Deploy

    Deploy and install

    What changes: It joins a site, a customer estate or a cloud IoT platform, under that platform's own device identity.

    The record: Same ECZ-ID. The platform identity stays where it is; the public record says who answers for the device.

  3. Service

    Operate and service

    What changes: Support contracts, field service and repairs come and go around it.

    The record: Same ECZ-ID. Its current state and evidence stay resolvable for anyone who needs to check.

  4. Update

    Software and firmware change

    What changes: Firmware versions, components and dependencies change with every release.

    The record: Same ECZ-ID. A firmware version is never a new Passport; release and SBOM evidence attach to the enduring identity.

  5. Transfer

    Ownership or custody change

    What changes: It is sold, handed over to a customer, or moved to a new operator or service provider.

    The record: Same ECZ-ID. A change of operator is an authority change on the identity, kept as lifecycle evidence — never a new identity.

  6. Retire

    Decommission and retire

    What changes: It leaves service, is replaced or is recycled.

    The record: Same ECZ-ID. Its lifecycle state changes on the record, and the essential evidence of its life is kept.

How the pieces connect

  1. Manufacturer or operatorThe organisation that answers for the device, on the record as its Parent.
  2. IoT PassportOne free ECZ-ID per device. A fleet is many Passports.
  3. Device and product bindingsProduct pages and documentation, bound to the one identity.
  4. Software and firmware contextRelease, SBOM and provenance evidence you supply.
  5. LifecycleDeployment, service, updates, transfer and retirement — same ECZ-ID.
  6. ResolverPublic, read-only proof for people and software.
  7. Evidence · Graph · WatchLedgerCore evidence, relationship views and change awareness, when you need them.

Operating a fleet? A fleet is many Passports, all free. Device instances under active management are counted in IoT Fleet Capacity, which is separate from AEC and never consumes it.

How the two counts differ

  1. Take the Passport

    Start in TrustOps with one sign-in. Your organisation's ECZ-ID Business Passport — Declared — FREE is reused or created, and your connected device gets its free IoT Passport — one ECZ-ID that does not change.

  2. Bind an asset

    Name an asset your connected device is known by — for example a manufacturer product page. Binding never creates a second identity. Each binding records where it was learned.

  3. Choose and prepare a proof method

    Choose the live proof method that fits the asset: Domain /.well-known file or DNS TXT record. Places no live method reaches are marked Planned. Your ECZ-ID console gives you the exact value to publish for that method.

  4. Complete the proof and review

    Publish it on the asset you control, then tell ECZ-ID the proof is in place. The binding is reviewed before anything about it is published as verified.

  5. ECZ-ID verification, then the Resolver

    ECZ-ID checks the published proof and records the outcome with the time it checked. The Resolver then shows the binding with its proof method, its Last verified date and its Re-check due date — to anyone, with no account and no API key.

  6. Operate — re-check before reliance

    Keep the proof in place. A binding is verified as of a time, not indefinitely: ECZ-ID does not renew a bound binding, and after its method's freshness window a new binding is the fresh proof — re-check before reliance. Publish the ECZ-ID where people and machines already look. Strengthen only if it is useful: Parent verification, monitoring, evidence and authority are optional, and none is needed to hold a Passport.

The binding law

  1. Passport
  2. Bind asset
  3. Proof method
  4. Prepare
  5. Complete proof
  6. Review
  7. ECZ-ID verification
  8. Resolver
  9. Operate

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.

Use cases

What IoT teams use ECZ-ID for.

Real situations, each served by one product of the ECZ-ID IoT domain. Every product starts from the same free IoT Passport; none of them changes what it proves.

Operate this Passport

Operate your IoT estate.

When one free IoT Passport becomes many, these are the products TrustOps lists for the IoT family. Each is optional and separate, and none changes what a Passport proves.

Universal platform

Five universal capabilities. One job each.

Scale → Monitor → Evidence → Understand relationships → Know when something changes.Five ECZ-ID capabilities sit behind every Passport family. All are optional, none changes what a Passport proves, and each is arranged through TrustOps.

IoT Fleet Capacity: The devices you actively manage are counted in IoT Fleet Capacity, which is separate from AEC: IoT never consumes AEC, and AEC never counts IoT.

A free IoT Passport exists and resolves whatever IoT Fleet Capacity you hold.

Authority & evidence, your estate plan and expert help

What a Passport may do and how a proposed action is evaluated, where receipts are kept, how the estate is operated and who can help — each optional, none of them changing what a Passport proves.

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.

Parent assurance

Strengthen the organisation, not the identity.

Every IoT Passport hangs from your organisation's Parent, the ECZ-ID Business Passport. DECLARED is free and enough to start; VERIFIED and ASSURED strengthen confidence in who is answering for your connected device — never the connected device itself.

  1. DECLARED

    ECZ-ID Business Passport — Declared — FREE

    Free · created with your first Passport

    Self-declared organisation identity, published with the date it was declared. Not independently verified.

    Suits: Holding every free Passport in every family, publishing records, adding bindings and being resolved by anyone.

    Never presented as verified.

  2. VERIFIED

    ECZ-ID Business Passport — Verified

    Optional · arranged through TrustOps

    Independent verification of the organisation behind your Passports. Paying opens ECZ-ID's checks; the record shows VERIFIED only after they pass.

    Suits: Production use, and reviewers who need to know who is answering for what they approve.

    Never verifies a child Passport's subject, and never changes an ECZ-ID.

  3. ASSURED

    ECZ-ID Business Passport — Assured

    Optional · arranged through TrustOps

    The higher-assurance organisation posture. Paying opens ECZ-ID's checks; the record shows ASSURED only after they pass.

    Suits: Larger or more sensitive estates, and enterprise procurement.

    Never verifies a child Passport's subject, and never changes an ECZ-ID.

Compare the Parent tiersConfigure in TrustOps(opens in a new tab — trustops.ecocitizenz.com)

Solutions

Solve the review, procurement and supply-chain problem above the identity.

Each solution uses the same free IoT identity foundation. None is a certification, a score or an approval.

Where it applies — DORA ICT-vendor evidence. Prepare reusable ICT-vendor evidence for financial-sector customer review workflows. ECZ-ID supports evidence preparation; it does not certify DORA compliance.

DORA details

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. All solutions

Flagship digital product

ECZ-ID Connected Product Cybersecurity Evidence & CRA/PSTI Readiness Kit

Organise connected-product cybersecurity evidence for CRA/PSTI readiness and buyer review.

Connected-product regulation and buyer review now ask lifecycle questions: who is accountable for the product, what software it runs, how vulnerabilities are reported and handled, how long it receives security updates and whether universal default passwords are gone. The answers sit in engineering, product-security, support and compliance systems that were never joined up, so every retailer, enterprise buyer and reviewer is answered from scratch.

What you receive

  • Connected-product identity evidence
  • Cybersecurity evidence structure
  • CRA/PSTI readiness prompts
  • Buyer-facing review artefacts

Boundary: The kit supports readiness work; it does not certify legal compliance. It is not a conformity assessment, a declaration of conformity, CE marking or a PSTI statement of compliance, and it replaces neither a notified body nor legal advice.

See the full productConfigure in TrustOps(opens in a new tab — trustops.ecocitizenz.com)
The readiness evidence kit
Product
The connected product, its device Passports and its accountable operator
Software
Firmware and software releases, with the SBOM and provenance evidence you supply
Updates
The security-update support period you state, and where it is published
Vulnerabilities
Your reporting route and handling process, as evidenced
Defaults
Password and secure-by-default evidence, where supplied
Gaps
Open items against the CRA and PSTI readiness prompts, stated plainly

Illustrative structure. The kit is assembled from your evidence; it is not a conformity assessment, and the Resolver remains the live proof.

Relevant bundles

When the problem spans more than one kind of entity.

Bundles connect the specialist products across a real workflow. Each identity stays distinct; a bundle never merges them.

How the estate fits together

TrustOps acquires. Dashboard operates. Resolver proves.

ECZ-ID Core writes the canonical identity, state and evidence. This website explains and hands off; it never issues, edits or stores an identity.

  1. TrustOps acquires

    Owns acquisition, payment and entitlement. Every free door and every purchase happens there, and nowhere else.

    Open TrustOps(opens in a new tab — trustops.ecocitizenz.com)About TrustOps

  2. Dashboard operates

    The signed-in estate console where you manage Passports, bindings, capacity and the capabilities you hold.

    Sign in — manage from your ECZ-ID account(opens in a new tab — trustops.ecocitizenz.com)About Dashboard

  3. Resolver proves

    Public, read-only proof. Anyone can open the current record and its JSON with no account, and re-check it before relying on it.

    Verify an ECZ-IDAbout Resolver

Developer Gateway documents and integrates. Schemas, client guidance and install routes for resolving ECZ-IDs from your own code.

Open the Developer Gateway(opens in a new tab — developers.ecocitizenz.com)

Live proof

Don't take our word for it. Resolve us.

EcoCitizenz Ltd runs this site and holds its own ECZ-ID. Everything below is read from the public record, by anyone, with no account and no key — including the parts that are empty.

ECZ-ID

active

EcoCitizenz

ECZ-GB-RBS1NW

Operated by
ECOCITIZENZ LTD
Organisation tier
VERIFIED
Bound representations
None published
Public relationships
None published

The parent organisation's identity is verified. This machine is not.

Evidence available

  • Not revoked
  • Anchor recorded · not publicly retrievable
  • No live PulseGuard monitor
  • No receipts in 30 days
Resolve(opens in a new tab — resolver.ecocitizenz.org)JSON(opens in a new tab — api.ecocitizenz.com)View Graph
Last read from the public record 2026-10-14. The Resolver is the authority. Re-check before reliance.

Check it yourself

The same record answers for humans and machines. One is a page, the other is JSON with no authentication in front of it.

curl -s https://api.ecocitizenz.com/api/p/ECZ-GB-RBS1NW.json | jq .

What each field means is documented on the Developer Gateway: Resolver projection(opens in a new tab — developers.ecocitizenz.com)

What it does not prove

That this company is safe to deal with, that its software is correct, or that anyone has audited it. A record establishes who an entity is and who operates it. Everything else is your decision, and you should re-check before you rely on it.

Open the record(opens in a new tab — resolver.ecocitizenz.org)Resolve any ECZ-IDGet the same badge for your organisation

Interoperability

Works alongside what you already run.

An IoT Passport complements the device identities, platforms, certificates and supply-chain records you already run. It publishes who is accountable for the device and, where declared, its manufacturer and model, and leaves provisioning, authentication and updates where they already live.

Native where you operate. ECZ-ID where you interoperate.Keep the identities your platforms need. Add the identity everyone else can resolve.

Related family Passports

  • Cloud IoT platforms and device registries

    What it does: Provision, connect and manage individual devices.

    What ECZ-ID adds beside it: A public, operator-linked identity for each device that anyone can resolve, carrying no raw serial number, MAC address or location. The platform's own device identity stays where it is.

  • Device certificates (X.509)

    What it does: Authenticate an individual device to your services.

    What ECZ-ID adds beside it: A printable public identity for the device that points to its accountable operator — never its key material, and never a replacement for its certificate.

  • GS1 product identifiers

    What it does: Identify trade items across supply chains.

    What ECZ-ID adds beside it: An operator-linked device identity that can be resolved alongside the product's trade identifier. It never replaces the GTIN.

Platforms, standards and providers are named to show where ECZ-ID sits alongside them. Naming them implies no endorsement by, or partnership with, their owners.

ECZ-ID complements your frameworks, protocols, OAuth, cloud IAM and workload identity. It replaces none of them and stays outside the execution path.

Read the interoperability boundaries in full

Across the connected-product supply chain and lifecycle

  • Firmware and software supply-chain tooling

    What it does: Build, sign, describe and ship the firmware and software a device runs, including the SBOM and provenance records for each release.

    What ECZ-ID adds beside it: One enduring device identity those release, SBOM and provenance records can be organised around, so evidence follows the product through updates instead of living in detached files.

  • Manufacturing, device-management and field-service systems

    What it does: Provision, enrol, update, service and decommission devices, and hold the manufacturer's and operator's own records about them.

    What ECZ-ID adds beside it: A public record of which organisation answers for the device at each stage, which those systems can link to without exposing their internal identifiers.

Naming a kind of system here states what it does and what ECZ-ID adds beside it. It implies no partnership, endorsement, certified integration or joint product.

Read this as carefully as the rest

An ECZ-ID does not replace any of these

An ECZ-ID IoT Device Passport is a persistent, resolver-verifiable identity for something you operate. It records who operates it, what has been declared and bound, and what the current public state is. It is not a substitute for, and must never be presented as replacing:

  • device security
  • network security
  • authentication
  • firmware security
  • safety engineering
  • device-management platforms

An ECZ-ID does not make a device safe, secure or correct, and it is not a certification, approval or test result. Your policy decides what to do with what the record says.

Enterprise and questions

Larger estates, and the questions people ask first.

Enterprise, partners and expert help

Estate-wide capacity, procurement terms, partner arrangements and fixed-scope expert engagements are agreed directly rather than bought online. The IoT Passport itself stays free at any scale.

EnterpriseTalk to us
What does a free IoT 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 IoT Passport identify?
One IoT Passport is one physical device, or one device identity module, operated by your organisation. A fleet is many Passports. Firmware versions, MAC and IP addresses, and the gateways and hubs a device registers with are not separate Passports.
Who can check the record for my connected device?
Anyone. Once you consent to publication, the Resolver serves the record as a page and as JSON, with no account and no key.
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.
Does the IoT Passport verify the connected device?
A DECLARED record states what your organisation says. A VERIFIED or ASSURED Parent verifies your organisation, not the connected device. 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 connected device itself.

Every question, answered

Start with the identity. Everything else is optional.

£0 · No card required · Permanent, not a trial.

Get a FREE IoT PassportVerify an ECZ-ID