Active Entity Capacity for growing client estates
Capacity for the number of active managed machine entities — agents, MCP servers, plugins, APIs, SDKs and workloads — an organisation operates beyond the free pooled allowance that comes with its Business Passport. Packs stack and are pooled across those families.
In an MSP client estate
Why Active Entity Capacity matters for a managed estate
Who it is for
The MSP problem it addresses
The client problem it addresses
When to attach it to a client
What the MSP receives
- More active managed entities for the organisation that holds the capacity.
What the client receives
- Room to keep operating more machine entities, with existing identities unchanged.
How it fits the recurring Machine Trust service
Options, prices and state
Each option, as TrustOps lists it
Bought in TrustOps as packs (monthly or annual prepaid); the largest estates are arranged as an enterprise contract. Prices and what can be bought today come from TrustOps, which owns every purchase, entitlement and renewal.
Active Entity Capacity
Active Entity Capacity +25
Annual prepaid£99 — one payment for 12 months; it does not renewPaid · OpenBuy annualIncludes 25 more active entities.Active Entity Capacity +100
Annual prepaid£299 — one payment for 12 months; it does not renewPaid · OpenBuy annualIncludes 100 more active entities.Active Entity Capacity +500
Annual prepaid£999 — one payment for 12 months; it does not renewPaid · OpenBuy annualIncludes 500 more active entities.Active Entity Capacity +2,000
Annual prepaid£2,999 — one payment for 12 months; it does not renewPaid · OpenBuy annualIncludes 2,000 more active entities.Active Entity Capacity 10,000+ (contract)
By arrangementPrice agreed with youBy arrangement · EnquiryConfigure enterprise planArranged directly, so the scope and the price are agreed with you.
States and prices from the TrustOps catalogue snapshot of 2026-10-14; TrustOps shows the current state. Buying a capability changes what you can operate. It never changes what the public record proves, and no paid tier is a verification outcome.
What you get
In TrustOps' own words
Active Entity Capacity +25
Active Entity Capacity +25
Includes 25 more active entities.
Active Entity Capacity +100
Active Entity Capacity +100
Includes 100 more active entities.
Active Entity Capacity +500
Active Entity Capacity +500
Includes 500 more active entities.
Active Entity Capacity +2,000
Active Entity Capacity +2,000
Includes 2,000 more active entities.
How it works
In plain English
- 1Every Business Passport includes a free pooled allowance of active entities.
- 2When an estate needs more, add a pack; packs stack and add up.
- 3IoT device instances use IoT Device Fleet Capacity instead.
- 4If capacity runs out, nothing is revoked, destroyed or detached.
Inputs
- The organisation's active managed entities beyond its free allowance.
Outputs and evidence
- A larger pooled allowance for that organisation.
With your existing stack
Boundaries
What it does not do
- It does not change any ECZ-ID, tier or Resolver record.
- It does not verify or authorise anything.
TrustOps terms for Active Entity Capacity +25 (monthly)
- Packs stack and add up.
- Capacity is pooled across the logical entity families.
- IoT device instances use IoT Device Fleet Capacity instead.
- Running out of capacity never revokes an identity; nothing is destroyed or detached at a limit.
- Usage is cost-governed.
What buying it never changes
- the ECZ-ID of the Parent or of any child Passport
- the Parent organisation tier
- any child Passport assurance
- any Resolver record or public projection
- the existing managed estate (nothing is destroyed or detached at a limit)
Proof and integration
Resolver and Developer Gateway
Resolver relationship
Developer Gateway route
In the MSP journey
What comes before and after
Usually comes before
Usually comes after
Questions
Active Entity Capacity: questions MSPs ask
What happens if a client runs out of capacity?
Do packs replace each other?
Next step