Skip to main content

Team Management and Operations

Team adoption connects model onboarding, application credentials, cost attribution, and production maintenance. This page offers operational guidance using existing platform capabilities.

Assign responsibilities​

RoleTasks
Platform administratorConnect upstreams, configure services and checks, monitor platform health
Organization administratorManage membership and organization credentials, review consumption
Application ownerUse the correct key and model name, handle failures and key replacement
Operations teamCheck instances and dependencies, follow deployment maintenance procedures

Actual permissions depend on deployment configuration. See Organizations and Custom User Systems.

Onboard a team​

  1. Identify required models and whether costs belong to a person or organization.
  2. Have an administrator connect models and verify availability.
  3. Create recognizable API keys with appropriate allowances and expiry.
  4. Complete the Quickstart, checking usage and attribution.
  5. Assign owners for credentials, incident handling, and spending reviews.

Create separate development and production keys with recognizable names, spending allowances, and expiry dates. Configure deployment resources separately when environments require dedicated networks or compute resources.

Maintain configuration​

Before changing upstreams, routing, or content checks, save the current configuration and validate a test service. Afterwards check responses, success rates, latency, and charges. If problems occur, restore the service using the saved configuration.

Follow Endpoint Settings when changing resources, runtimes, or replicas. Schedule maintenance for changes requiring the instance to stop.

Upgrades and support​

See Kubernetes Configuration for installation and TLS settings, and follow the Upgrade Guide for upgrades and recovery. Rolling back a deployment version is different from reverting an individual gateway policy.

Use Troubleshooting to distinguish client, gateway, and provider failures. Commercial support channels, response times, and maintenance arrangements follow the purchased service agreement.