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

Authority · Intent and runtime decisions · ECZ-ID IoT

ECZ-ID Intent + Intent Control

Both services in one plan: the authorised boundary and its runtime control.

ECZ-ID Intent + Intent Control is one plan for both services: ECZ-ID Intent, which records the authorised objective, constraints and validity of what a Passport may do, and ECZ-ID Intent Control, which evaluates a proposed action against that authority, the Intent, your policy and optional counterparty context. Decisions are EVALUATED, never ENFORCED by ECZ-ID, and payment authorises nothing.

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

The problem

Why it matters.

An authorised boundary is only useful if proposed actions are checked against it, and a runtime check needs a boundary to check against. Buying the two separately leaves a gap in between; one plan for both keeps them together for your connected devices.

Built for

  • Teams that want the authorised Intent and its runtime evaluation under one plan.
  • Operators of connected devices whose actions are checked against authority and policy before their own systems act.
  • Organisations that would otherwise hold an ECZ-ID Intent plan and an ECZ-ID Intent Control plan side by side.

What changes

  • The authorised objective, constraints and validity, and the evaluation of proposed actions against them, in one plan.
  • Decisions recorded as EVALUATED, with their basis.
  • Your own enforcement points left in charge of what happens next.

What you receive

Concrete deliverables, not a vague trust score.

  • ECZ-ID Intent: authorised Intents, each with its objective, constraints and validity, authorised only by an owner or administrator of your organisation.
  • ECZ-ID Intent Control: protected entities, hosted decisions and policy syncs for runtime control.
  • Essential, Pro and Business plans, monthly or annual, as TrustOps publishes them.
One plan, two services
Subject
ECZ-XX-XXXXXX::IOT_DEVICE-XXXXXX
Intent
The authorised objective, constraints and validity
Intent Control
A proposed action evaluated against authority, the Intent, policy and optional counterparty context
Decision
EVALUATED — with its basis
Next step
Your enforcement point decides

Illustrative structure with placeholder values.

How it works

A short path from need to something usable.

  1. Define and authorise an Intent for the Passport.

  2. Keep your policy in step through policy syncs.

  3. A proposed action is evaluated against authority, the Intent, policy and any counterparty context you supply.

  4. Your own enforcement point decides whether the action goes ahead.

How it relates to your Passport

The plan reads the Passport and never changes it: the ECZ-ID, its Resolver record and your Parent tier stay as they are. Identity is not authority, and evaluation is not enforcement.

Use cases

  • Authorising what one of your connected devices may do and checking each proposed action against it, under one plan.
  • Applying the same policy to every evaluation through policy syncs.
  • Answering a reviewer who asks what an entity was authorised to do and how its actions were evaluated.

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.

  • Every decision is EVALUATED, never ENFORCED by ECZ-ID.
  • Payment authorises nothing; only an owner or administrator of your organisation authorises an Intent.
  • Counterparty context is used only where you supply it.

Boundaries

The claims stop here.

  • Decisions are EVALUATED, never ENFORCED by ECZ-ID; an action is stopped only by an enforcement point you run.
  • Payment authorises nothing, and a Passport is not an Intent authorisation.
  • An Intent is authorised only by an owner or administrator of your organisation.
  • Intent and protected-entity coverage is not AEC capacity.

Integrations and questions

Works with what you already run.

  • ECZ-ID Intent and ECZ-ID Intent Control, each also available on its own.
  • The enforcement points and policy engines you already run.
  • Dashboard: Intents, protected entities and decisions.

Build and integrate it from code: IoT & Connected Systems(opens in a new tab — developers.ecocitizenz.com)

Is this different from buying Intent and Intent Control separately?
It carries both services in one plan. Each is also available on its own, with its own plans.
Does the plan block actions?
No. Decisions are EVALUATED, never ENFORCED by ECZ-ID. An action is stopped only by an enforcement point you run.
Does buying it authorise anything?
No. Payment authorises nothing. An Intent is authorised only by an owner or administrator of your organisation.

Related

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

Your IoT Passport stays free. ECZ-ID Intent + Intent Control sits above it and is acquired in TrustOps.

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