Capacity
AEC — Active Entity Capacity
AEC is how ECZ-ID counts the entities you actively manage in production. It is not a limit on how many Passports you may hold, and it never makes an identity more verified.
Definition
One AEC is one actively managed production entity
One AEC is one actively managed production entity with live bindings and current state.
What counts for the SDK family
An SDK or package you actively manage in production, with live bindings and current state.
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 boundary
Four things AEC never does
AEC is a count of what you actively manage. It is not a tier, not an assurance level and not a property of any identity.
- 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 IoT device instances are counted separately, in IoT Fleet Capacity, and never consume AEC.
Where the numbers live
This site publishes no allowances and no prices
Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
