General Notes

This page captures the most common non-technical expectations around the gateway during initial onboarding.

What OpenFrog is good for

• A unified AI model gateway
• Centralized key and quota management for teams
• One access layer for Codex, Claude Code, Gemini CLI, and similar tools

Common misunderstandings

• Assuming a gateway switch requires a full application rewrite
• Assuming every agent needs its own standalone provider account
• Assuming model routing has to be handled inside each client

Recommended approach

Keep model access, routing, and billing policies inside the gateway. Let clients carry only the minimum configuration required to run.