Skip to content
ECZ-IDService & Workload
Free Passport: Get a FREE Service & Workload Passport

Professional services · ECZ-ID Service & Workload

Expert help

Fixed-scope engagements when you would rather not do it yourself.

Professional services for Service & Workload estates and for ECZ-ID integration generally: one-off engagements TrustOps lists with their scope and price, and pilots arranged directly by enquiry. Buying one starts an engagement and its written intake; it never creates or changes an ECZ-ID, a Business Passport tier or a plan.

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

The problem

Why it matters.

Mapping an estate of services and workloads, setting up bindings and integrating ECZ-ID with the systems you already run takes time a team may not have. A fixed-scope engagement gets it done without guessing at the scope.

Built for

  • Platform teams who want their services, workloads and the credentials each one uses mapped by people who do it regularly.
  • Teams piloting multi-cloud or SPIFFE federation with ECZ-ID bindings.
  • Organisations integrating ECZ-ID with the systems they already run.

What changes

  • A defined scope before work starts.
  • Work delivered as an engagement, not an open-ended subscription.
  • Identities and records untouched by the purchase itself.

What you receive

Concrete deliverables, not a vague trust score.

  • One-off engagements, with the scope and price TrustOps publishes.
  • Engagements arranged directly by enquiry, where TrustOps lists them that way.
  • A written intake when an engagement starts.
An engagement
Scope
As TrustOps lists the engagement, or as agreed with you by enquiry
Starts
With the purchase or the agreement, then a written intake
Delivers
Work to that scope, as a one-off engagement
Never
A new or changed ECZ-ID, Business Passport tier or plan
Boundary
Never a certification

Illustrative structure. Each engagement's scope and price are TrustOps' own, listed below.

How it works

A short path from need to something usable.

  1. Choose the engagement that fits.

  2. Start it in TrustOps, or enquire where it is arranged directly.

  3. Complete the written intake.

  4. The engagement is delivered to its scope.

How it relates to your Passport

An engagement works with the Passports, bindings and records you already hold and changes none of them by being bought. The Resolver keeps publishing each record exactly as before.

Use cases

  • Mapping every service and workload you operate, its owner and the workload identity it runs as.
  • Piloting multi-cloud or SPIFFE federation and ECZ-ID bindings before rolling them out.
  • An integration sprint for the systems you already run.

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.

  • Payment starts your engagement and written intake; it is not proof.
  • Buying an engagement changes no ECZ-ID, Business Passport tier or plan.
  • An engagement is never a certification.

Boundaries

The claims stop here.

  • Buying an engagement never creates or changes an ECZ-ID, a Business Passport tier or a plan.
  • Payment starts the intake; it is not proof of anything on the record.
  • An engagement is never a certification.
  • A purchase reserves no start date.

Integrations and questions

Works with what you already run.

  • Your free Service & Workload Passports, bindings and Dashboard.
  • The systems you already run, integrated where the engagement's scope says so.
  • TrustOps: where each engagement is started or arranged.

Build and integrate it from code: APIs, AI, Data & Software(opens in a new tab — developers.ecocitizenz.com)

Does an engagement verify my service or workload?
No. Payment starts the intake; it is not proof of anything, and an engagement is never a certification.
When does the work start?
After the written intake. A purchase reserves no start date.
What if no listed engagement fits?
The pilots arranged by enquiry are scoped with you directly through TrustOps.

Related

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

Your Service & Workload Passport stays free. Expert help sits above it and is acquired in TrustOps.

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