| Estate size | How many logical agents you operate, how many of them you actively manage in production today, and the direction of travel over the next twelve months. Versions, replicas, regions and deployments of one agent are still one agent. | Capacity is AEC — Active Entity Capacity, pooled across the organisation. Bindings, versions, replicas, endpoints and deployments never consume AEC and never become a second Passport. If what TrustOps already offers covers your estate there is nothing to negotiate, and that is the answer you should get. |
|---|
| Identity families | Agent only, or Agent plus MCP, Plugin, API, SDK, IoT, or Service and Workload. | Each family is a separate subject with its own FREE Passport, while AEC is one pool across them. An estate that is small in one family and large in another is a different conversation from one that is uniformly large. |
|---|
| Monitoring cadence | How often published identity state must be re-evaluated, which changes must raise something, and who or what has to receive it. | Free identities get current state on demand, when someone actually asks. Scheduled evaluation and change notification are separate capabilities with a different shape, and the cadence you need decides which of them, if either, fits. |
|---|
| Evidence volume and retention | The rough volume of identity events you expect, how long the record of them must remain retrievable, and in what form you have to hand it to someone else. | Retention and export are the two requirements that most often come from your own obligations rather than from ours, so we need yours rather than a general answer. |
|---|
| Integrations | Where an identity has to appear: a vendor or supplier register, a CMDB, a policy engine, an API gateway, a catalogue, a marketplace listing. And which way the data has to flow. | Reading a public record needs nothing from us — it is unauthenticated and open. Writing into your systems, or receiving from them, is the part that has to be designed. |
|---|
| SLA | The availability and response expectations you are contractually required to meet, and whether you have to pass them through to your own customers. | We publish no service-level number on this site, because we would be inventing it. Tell us the one you are held to and we will answer against that rather than around it. |
|---|
| Data handling | Residency constraints, sub-processing constraints, anything that may not leave a jurisdiction, and whether anything you would send us is personal data. | ECZ-ID records are public by design, which removes most of this question and sharpens what is left. The part that matters is the material that is not the public record. |
|---|
| Procurement route | Vendor onboarding, the security questionnaire you use, the contract vehicle, purchase order and invoicing arrangements, and who signs. | This is usually the longest part of the timeline and the easiest to start early. Telling us the route at the beginning is the single biggest thing you can do to shorten it. |
|---|
