Before a team rollout

1. Create provider profiles without saving raw provider keys in the browser.
2. Run route simulation for production aliases, fallback, and budget policy.
3. Create draft virtual key scopes with model allowlists, RPM, TPM, and budget limits.
4. Confirm retention is metrics only unless the team has approved a broader policy.
5. Export the profile and send deployment requirements to the support address.

Production boundary

A production gateway needs server-side authentication, encrypted provider-key storage, backup and rollback policy, provider billing ownership, and incident controls. Do not send real production traffic through an unreviewed public setup profile.