Trust tiers and limits
Your trust tier is an account state derived from your paid history, account age and verification. It does not reserve capacity. GET /limits gives your current limits, can_create and the reasons; inspect that response before provisioning.
Tier conditions
| Tier | Unlocked by | Running (kept) | Sizes | Previews / share links / hooks |
|---|---|---|---|---|
| 0 | Sign-up | 0 | none | No previews, share links or hooks; 403 tier_limit |
| 1 | First credited top-up and a verified email | 2 (10) | ac-2, ac-4 | 20 live private previews; 100 live links and credentials; share links up to 24 h and 10 uses, 5 active; 10 hooks |
| 2 | At least $50 net paid, account at least 14 days old, and a passed account review | 6 (30) | adds ac-8, ac-16 | 100 live previews; 500 live links and credentials; share links up to 7 days, 25 active; 50 hooks |
| 3 | By agreement | By agreement | By agreement | By agreement; no outbound mail exception |
Live links and credentials count access and share origins (including exhausted links), cpt_ preview tokens and browser grants together. Creating beyond any live cap returns 403 tier_limit. A downgrade changes new issuance limits, not existing authority before it expires or is revoked.
Tier 0 inherits the general request limits of Tier 1 but only 2 top-ups per day; this confers no resource entitlement. Snapshots and private images are separate quotas: 6 snapshots per hour and 2 private images per day on Tier 1 (20 per hour and 10 per day on Tier 2). Outbound bandwidth and connection limits per tier are on the Networking page, and request rates on Rate limits.
Key quotas at every tier
Tiers 0, 1 and 2 share the same key quotas: 100 active API keys, and 100 successful key creations plus rotations per rolling 24 hours. Console and child-key issuance use the same budgets. Hitting the active-key cap returns 403 tier_limit; the rolling budget returns 429 rate_limited with Retry-After. An exact replay does not issue again, and revocation always remains available.
A key's restrictions allow at most 100 distinct computer IDs and 100 private-image IDs, 32 CIDRs of at most 64 characters, and 16 metadata keys (64-character keys, 256-character values). The canonical restriction JSON may be at most 16,384 UTF-8 bytes. Duplicate or oversized values return 400 invalid_request before anything is written. Metadata for expired or revoked keys is kept for 30 days. See Keys and limits for agents and the key-limit fields of the API reference.
Dory is in development; these pages describe the planned service and may change. Questions: support@computeengines.com.