Workflow bundle · ECZ-ID API

ECZ-ID Connected Platform Assurance Bundle

Connect API and device evidence around the platform customers actually use.

A cross-family bundle for connected platforms where APIs, apps and devices form one customer experience.

Type: Bundle
Price: Not restated on this site; TrustOps publishes the current price and availability
Acquired and paid in: TrustOps
Operated in · proved by: Dashboard · Resolver

The problem

Why it matters.

For a connected platform, the API is the part customers integrate — but behind it sit devices, apps and backend services, each with its own evidence. Buyers get a separate story for each and cannot see how they fit together.

Built for

Connected platforms
IoT SaaS
API-led products

What changes

One platform review story
Less duplicated evidence
Clearer dependency context

What you receive

Concrete deliverables, not a vague trust score.

Relevant specialist kits
Cross-entity relationship context
Customer-facing platform artefacts

A connected-platform view

Platform: The customer-facing platform and its boundary
Components: APIs and devices — each with its own ECZ-ID
Operator: The organisation accountable for each component
Dependencies: Which component depends on which, where published
Boundary: A graph of distinct identities — never one merged Passport

Illustrative structure.

How it works

A short path from need to something usable.

Define the platform boundary.
Map the component identities.
Complete the evidence.
Package the connected view.

How it relates to your Passport

Each component keeps its own free Passport — APIs and devices alike. The bundle uses the Digital Entity Graph to show how they relate, and brings the ECZ-ID API Enterprise Security Review & Customer Assurance Kit together with the evidence for the platform's other components.

Use cases

An IoT SaaS provider whose customers integrate its platform API.
An API-led product whose API fronts the devices and apps customers use.

Tiers and price

Price and availability

Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. This site does not restate this product's price; TrustOps publishes its current tiers, price and availability, and shows them before anything is bought.

How it is arranged

TrustOps acquires
TrustOps publishes the tiers and holds payment and entitlement whenever it is offered.
Dashboard operates
Once you hold it, it appears in your Dashboard, where you operate it.
Resolver proves
Public facts stay on the Resolver; holding it never changes what a record proves.

Privacy, security and evidence

What is collected, published and kept.

Each component keeps its own identity and record.
Only published relationships appear in public views.
A platform view is not a certification of the platform.

Boundaries

The claims stop here.

A connected platform remains a graph of distinct identities, not one merged Passport.

Integrations and questions

Works with what you already run.

API and IoT Passports, as relevant.
Graph Intelligence for the platform's dependency view.
The device platforms and API gateways you already run, unchanged.

Does the platform get one Passport?: No. A connected platform remains a graph of distinct identities. Each component keeps its own free Passport.
Is this a certification of the platform?: No. It organises evidence around the platform. It does not certify it as secure, compliant or approved.

Keep the identity free. Everything above it is optional.

Your API Passport stays free. ECZ-ID Connected Platform Assurance Bundle sits above it; TrustOps shows its current state.

Open in TrustOps