Skip to content
ECZ-IDAPI
Free Passport: Get a FREE API Passport

Workflow bundle · ECZ-ID API

ECZ-ID Machine Identity Assurance Bundle

Create one assurance workflow across machine identities that live in different environments.

A bundle for organisations operating services, workloads and the APIs they expose under one machine-identity programme.

Configure in TrustOps(opens in a new tab — trustops.ecocitizenz.com)See the tiers and pricesAll API products
Type
Bundle
Price
Tiers and prices below, read from TrustOps
Acquired and paid in
TrustOps
Operated in · proved by
Dashboard · Resolver

The problem

Why it matters.

Machine identities multiply across environments: services and workloads in clusters and clouds, and the APIs they expose. Each class has its own native identity system and its own review questions, so an organisation ends up with several disconnected programmes and no single account of the logical subjects it operates.

Built for

  • Platform engineering
  • Machine-identity programmes
  • Connected estates

What changes

  • One operating model across machine identity classes
  • Reusable evidence
  • Clearer entity separation

What you receive

Concrete deliverables, not a vague trust score.

  • Relevant specialist kits
  • Cross-entity identity mapping
  • Machine-identity review artefacts
A machine-identity programme view
Estate
The machine-identity classes you operate — services and workloads, and the APIs they expose
Subjects
Each logical subject, with its own ECZ-ID
Native identities
The runtime identity system each class already uses, left where it is
Operator
The organisation that answers for each subject, with its Parent tier
Boundary
Each subject stays distinct — no universal credential is created

Illustrative structure. Native identifiers stay private; the Resolver shows only published records.

How it works

A short path from need to something usable.

  1. Define the machine estate.

  2. Map each logical subject.

  3. Complete the relevant evidence.

  4. Assemble the programme view.

How it relates to your Passport

Each subject keeps its own free Passport. For API Passport holders the bundle brings the ECZ-ID API Enterprise Security Review & Customer Assurance Kit together with the specialist products for the services, workloads and APIs you operate, in one programme.

Use cases

  • Organisations running more than one class of machine identity — services, workloads and the APIs they expose — that want one programme for all of them.
  • An organisation answering one machine-identity review instead of one per class.
  • Keeping a service, the workload running it and the API it exposes as three distinct, related subjects.

Tiers and price

What it costs, and where you buy it.

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. Read from the TrustOps projection generated . All pricing

After purchase

  1. TrustOps acquires

    Configure and buy in TrustOps, which owns payment and entitlement.

  2. Dashboard operates

    The entitlement appears in your Dashboard, where you operate it.

  3. Resolver proves

    Public facts stay on the Resolver; buying never changes what a record proves.

Privacy, security and evidence

What is collected, published and kept.

  • Each subject keeps its own identity and record; the bundle creates no shared or universal credential.
  • Native identifiers and account details stay private, and no provider IAM is changed.
  • Publication of each record stays your decision.

Boundaries

The claims stop here.

  • The bundle keeps each subject distinct; it does not create a universal credential.

Integrations and questions

Works with what you already run.

  • Service & Workload and API Passports, as relevant.
  • The workload identity systems and API gateways you already run, unchanged.
  • Graph Intelligence for the relationships between subjects.

Build and integrate it from code: API binding(opens in a new tab — developers.ecocitizenz.com)

Does the bundle create one identity for all my machines?
No. Each logical subject keeps its own Passport. The bundle organises the programme; it never merges identities or creates a universal credential.
Do I need every family's Passport?
Only for the subjects you actually operate. Each Passport is free.

Related

Keep the identity free. Add this when the outcome is worth it.

Your API Passport stays free. ECZ-ID Machine Identity Assurance Bundle sits above it and is acquired in TrustOps.

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