Capacity
AEC — Active Entity Capacity
IoT is the one family with two separate counts. AEC counts logical identities. IoT Fleet Capacity counts individual device instances. They are not interchangeable and one never consumes the other.
Definition
One AEC is one actively managed production entity
What counts for the IoT family
An IoT product, model or fleet identity you actively manage in production.
One pool, not one per family
AEC is one pool shared across your Agent, MCP, Plugin, API, SDK and logical Service & Workload identities, and your IoT product, model and fleet identities.
A free Passport exists and resolves whether or not you use any AEC.
The distinction that matters most here
AEC and IoT Fleet Capacity are two different counts
AEC — Active Entity Capacity
A pooled count of the eligible logical identities you actively manage, shared across your Agent, MCP, Plugin, API, SDK and Service & Workload identities and your IoT product, model and fleet identities.
IoT Fleet Capacity
A separate count of individual device instances under active management. It is counted on its own meter, and it never consumes AEC.
Holding a Passport consumes neither. Retired and historical devices consume neither. Public reads of your records — human or machine — consume neither, at any scale. Message and telemetry volume is outside both meters entirely.
The boundary
Four things AEC never does
- AEC never makes an identity more verified.
- AEC never replaces a Passport.
- AEC never changes an ECZ-ID. Your ECZ-ID does not change.
- Running out of AEC never deletes, revokes or unpublishes an identity.
Individual device instances are counted in IoT Fleet Capacity, which is separate from AEC and never consumes it.
Where the numbers live