Migrate from Multi-Key Setup

Replace multiple provider API keys scattered across your team with a single VibeCC key.

The Problem

Typical setup before VibeCC:

  • Developer A has sk-openai-xxx in their .env
  • Developer B has a different key
  • CI/CD pipeline has its own keys
  • No unified usage visibility or budget controls
  • Key rotation requires updating every developer's environment

The Solution

  1. Create one VibeCC workspace key in the Console
  2. Each developer sets OPENAI_API_KEY=vcc_team_key
  3. All usage flows through VibeCC with org-level tracking and budget enforcement

Migration Steps

  1. Create API key in Console → Settings
  2. Share key via your team's secret manager (1Password, Vault, Anthropic Secrets Manager)
  3. Update environments — each developer's .env and CI/CD secrets
  4. Verify traffic — check the Console usage dashboard after a few requests
  5. Revoke direct keys — once all traffic is through VibeCC, revoke old provider keys

Benefits

| Before | After | |--------|-------| | Keys scattered across team | One key per workspace | | No usage visibility | Per-developer usage tracking | | Manual key rotation | Rotate in one place | | No budget controls | Workspace-level limits | | Individual provider rate limits | Aggregated via routing |