Signup and production

The proposed pilot uses managed signup and operator-approved capacity. Your organization represents the paying customer; its application users have separate identities and permissions.

Signup that can resume

1. Sign in through managed Universal Login and verify your email. Accounts are bound to identity issuer and subject; sharing an email domain never joins an organization automatically.
2. Create one organization per account in the pilot. Repeated submissions with the same idempotency key resolve to the same organization and draft application.
3. Submit your use case, integration context, and requested limits. The application moves from draft to submitted, then approved or rejected.
4. An approved environment moves through provisioning to ready, or failed with a safe error code and request ID. An operator can retry the same provisioning job without creating duplicate cells.
5. Complete MFA and issue your first key only after readiness checks pass.

The console derives its checklist from stored facts. A refresh, lost response, or worker restart must not reset progress. Polling backs off from five seconds; errors never create substitute success screens.

Team roles

Role	Key issuance	Product content access
Owner	Tenant keys, including explicit privileged delegation templates	No automatic access to end-user content
Developer	Their own ordinary sandbox keys	No automatic access to other actors
Operator	No key issuance	Operational metadata only
Billing	No key issuance	Billing metadata only

Invitations are single-use, expire after seven days, and must match the exact verified email. MFA is required before the first key. Privileged issuance and production requests require trusted reauthentication within five minutes; a browser checkbox cannot satisfy it.

Request production

An owner supplies legal billing contact/address, requested budget, and accepted price and terms versions. An operator verifies billing readiness and the integration acceptance suite, then provisions a separate production cell. No production keys exist before it is ready. Sandbox keys, connected accounts, credentials, and user data are not copied to production.

Production billing begins with manual invoices backed by measured usage. There is no card-data collection in the pilot console. No numeric price is validated in this documentation.