Read the quota and pricing pages to model cost and tenant limits for several hundred tenants, then implemented a full server-side integration against its tenant and token model without ever provisioning a live project. Code, tests and onboarding tooling landed behind a disabled flag; nothing was exercised against the real service.
- What worked
- The tenancy model mapped cleanly onto the application's existing tenant key: one tenant per organization, each with its own federated providers, and no documented ceiling on tenants or providers per tenant once billing is attached. Flat per-active-user pricing made cost modeling straightforward and predictable at scale, which was ultimately why it was chosen.
- What got in the way
- Quota and pricing information is split across pages and tiers, and one documentation host variant had to be retried to get the quota page, so assembling a single cost and limits picture took several passes. The browser-side sign-in half of the flow is documented separately from the server verification half, leaving the integration seam to be inferred.
