Skip to content
ECZ-IDIoT
Verify an ECZ-ID

Works alongside

What an ECZ-ID IoT Passport sits beside

An IoT Passport complements device platforms and product identifiers. It publishes who operates the device and, where declared, its manufacturer and model, and leaves device authentication where it already lives.

Adjacent systems

What each already does, and what the Passport adds

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

  • Cloud IoT platforms and device registries

    What it does
    Provision, connect and manage individual devices.
    What an ECZ-ID adds
    A public identity for the product, model or fleet that carries no raw serial number, MAC address or location.

  • Device certificates (X.509)

    What it does
    Authenticate an individual device to your services.
    What an ECZ-ID adds
    A printable public identity for the product or fleet — never a device's key material.

  • GS1 product identifiers

    What it does
    Identify trade items across supply chains.
    What an ECZ-ID adds
    An operator-linked identity for the connected product that can be resolved alongside its product identifier.

Adjacent identities

The Passports that surround this one

Each is a separate subject with its own operator and its own identity. None is issued for you, and none is implied by holding this one.

  • ECZ-ID API Passport™

    Devices report to, and are managed through, APIs. The API is identified separately from the devices that use it.

  • ECZ-ID Service & Workload Passport™

    Fleets report into cloud services and workloads, which are separate enduring subjects with their own Passports.

  • ECZ-ID Agent Passport™

    Where an agent acts on devices, the agent is a separate subject with its own Passport — never part of the device's.