Skip to content
ECZ-IDIoT

IoT Fleet Capacity

What IoT Fleet Capacity counts

One count, for devices. It measures the devices you actively manage — never how many Passports you hold — so this page keeps the two numbers apart, deliberately and at length.

One count

IoT Fleet Capacity is IoT's own capacity

The devices you actively manage are counted in IoT Fleet Capacity, which is separate from AEC: IoT never consumes AEC, and AEC never counts IoT.

Devices under active management

IoT Fleet Capacity

A count of individual device instances under active management. It is the only meter this family has for devices, and it is IoT’s alone.

It is a level, not a flow. Nothing about it resets at the end of a month, so a “per month” framing would describe a billing cadence and never a consumption period.

Not a count of Passports

Every device Passport stays free

A Passport is a property of the identity, not of any envelope. The free IoT Passport is £0, is never sold, and keeps resolving whatever capacity you hold.

Holding a Passport consumes nothing: the count moves only with the devices under active management.

The rule that generates the confusion

The meter counts devices under active management

It counts them — never the number of Passports you hold. Those are two independent numbers, and only one of them is bounded.

A Passport can exist and occupy nothing. Holding an identity consumes no capacity of any kind. The count moves when a device is under active management, and it moves back when it is not.

So a fleet larger than your envelope is a supported condition rather than an error. Devices beyond it become unmanaged, not deleted — and you decide which ones those are.

  • Holding a Passport

    Consumes nothing. The number of IoT identities your organisation holds is not bounded by IoT Fleet Capacity.

  • Retired and historical devices

    Consume nothing. A device that is shelved, returned or decommissioned stops occupying anything. History is free.

  • Public reads

    Consume nothing, at any scale. Every read of a record — by a person, an auditor, an insurer or a machine — is free and unmetered.

  • Message and telemetry volume

    Consumes nothing. This is not billed by traffic. Payload sizes, message counts and reporting intervals sit outside the count entirely.

Reaching a limit

What running out never does

Capacity is a count of what is actively managed. It is not a property of any identity, and it cannot reach back and change one.
  • IoT Fleet Capacity never makes an identity more verified.
  • IoT Fleet Capacity never replaces a Passport, and never changes an ECZ-ID.
  • Reducing or cancelling capacity never deletes a device, a record or a Passport. Bindings above the envelope become unmanaged, and nothing is destroyed.
  • Your ECZ-ID, its Resolver page and its machine JSON keep working, whatever your capacity.
  • Your organisation's tier and every Passport's assurance state are unaffected in both directions.

IoT Fleet Capacity tiers and prices

Read from the TrustOps projection generated 2026-10-14. Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal. A price is a billing cadence, never a consumption period: the count itself is a level.

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