Skip to content
ECZ-IDIoT

Scale · ECZ-ID IoT

IoT Fleet Capacity

Scale the fleet of devices you actively manage, without turning capacity into identity.

IoT Fleet Capacity is how ECZ-ID counts the individual devices your organisation actively manages. Every device keeps its free IoT Passport; capacity packs of +1,000, +10,000 and +100,000 devices, and an Enterprise contract, add to the devices included free. It never consumes AEC, and AEC never counts IoT.

Type
Universal platform
Price
Tiers and prices below, read from TrustOps
Acquired and paid in
TrustOps
Operated in · proved by
Dashboard · Resolver

The problem

Why it matters.

A fleet grows device by device. Without a count of the devices you actively manage that is separate from identity, growth either becomes a new identity tier or an unpredictable bill — and an IoT fleet is counted in devices, never in AEC.

Built for

  • Manufacturers and operators moving from a pilot batch to a production fleet.
  • Teams that need headroom before a roll-out without touching any device's identity.
  • Organisations that want the device count kept apart from the Passports it never changes.

What changes

  • More actively managed devices under one organisation.
  • Capacity packs that add up, monthly or annual, or an Enterprise contract at fleet scale.
  • Identity, the Resolver record and the free baseline untouched by capacity.

What you receive

Concrete deliverables, not a vague trust score.

  • Device capacity packs of +1,000, +10,000 and +100,000, each monthly or annual, as TrustOps publishes them.
  • An Enterprise contract, negotiated to your operating scale.
  • The devices included free with your organisation, underneath any pack.
Capacity, as the Dashboard shows it
Counts
Individual devices under active management
Included
The devices included free with your organisation
Added
Capacity packs bought in TrustOps; packs add up
Separate from
AEC, which never counts IoT
Never
A change to any ECZ-ID, tier or verification state

Illustrative structure. Your own figures appear in the Dashboard, read from your entitlement.

How it works

A short path from need to something usable.

  1. Issue a free IoT Passport for each device you operate.

  2. Use the devices included free with your organisation first.

  3. Add IoT Fleet Capacity when the actively managed fleet grows beyond them; packs add up.

  4. Buying, cancelling, refunding or exhausting capacity never changes an identity, the Resolver record or the free baseline.

How it relates to your Passport

IoT Fleet Capacity sits beside the Passport, never inside it. It counts the individual devices you actively manage; every device Passport stays free and resolvable whatever capacity you hold.

Use cases

  • Planning headroom before a product launch or a fleet roll-out without touching any identity.
  • Counting the devices you actively manage — never the Passports you hold, which stay free.

Tiers and price

What it costs, and where you buy it.

IoT Device Fleet Capacity +1,000 (annual)

Paid · Open

£199 per year

  • One payment for 12 months (annual prepaid; it does not renew)

IoT Device Fleet Capacity +1,000. One payment for exactly 12 months. It does not renew.

IoT device instances
1,000 IoT device instances

IoT Device Fleet Capacity +10,000 (annual)

Paid · Open

£799 per year

  • One payment for 12 months (annual prepaid; it does not renew)

IoT Device Fleet Capacity +10,000. One payment for exactly 12 months. It does not renew.

IoT device instances
10,000 IoT device instances

IoT Device Fleet Capacity +100,000 (annual)

Paid · Open

£2999 per year

  • One payment for 12 months (annual prepaid; it does not renew)

IoT Device Fleet Capacity +100,000. One payment for exactly 12 months. It does not renew.

IoT device instances
100,000 IoT device instances

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.

  • Capacity is an entitlement held in TrustOps, not a property published on the public record.
  • Running out of capacity never deletes, revokes or unpublishes an identity.
  • Public reads of a device's record are free and never counted.

Boundaries

The claims stop here.

  • IoT Fleet Capacity is a commercial entitlement only. It is not verification, certification or trust status.
  • Running out of capacity never revokes an identity; a device beyond it becomes unmanaged, never deleted.
  • IoT Fleet Capacity never consumes AEC, and AEC never counts IoT.

Integrations and questions

Works with what you already run.

  • Dashboard: devices under active management against your capacity.
  • TrustOps: the only place capacity is added, changed or renewed.
  • IoT Fleet Identity & Lifecycle, for operating the fleet itself.

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

Do my devices consume AEC?
No. IoT never consumes AEC: the devices you actively manage are counted in IoT Fleet Capacity, IoT's own capacity.
Do I need IoT Fleet Capacity to hold a free IoT Passport?
No. A free Passport exists and resolves whether or not its device is inside paid capacity.
Does IoT use AEC?
No. IoT devices are counted in IoT Fleet Capacity. AEC is the pool for the other six Passport families, and IoT is never in it.
What happens when the fleet outgrows its capacity?
Devices beyond it become unmanaged, not deleted, and every identity keeps resolving. You add a pack, or arrange an Enterprise contract, when you need more.