Do I need a gateway for internal and external model providers?

Not always, but often yes for external providers.

Short answer

• Internal model providers: usually no gateway is required if they’re already inside your trusted network or application environment.
• External model providers: a gateway is commonly recommended to handle security, policy, routing, logging, and abstraction.

When you do want a gateway

A gateway is useful if you need any of these:

• Central auth / access control
• Rate limiting / quota enforcement
• Audit logging
• Request/response filtering
• Provider abstraction so your app can switch between OpenAI, Anthropic, Azure, local models, etc.
• Cost tracking and usage governance
• Data loss prevention or prompt/response redaction
• A single endpoint for multiple internal/external providers

When you may not need one

You can skip a gateway if:

• Your app only talks to one provider
• The provider is internal and already trusted
• You don’t need centralized policy, observability, or routing
• You’re okay with the app integrating directly with each provider’s API

Common pattern

• Internal providers: direct access or lightweight service wrapper
• External providers: route through a gateway

If you want, I can also give you:

1. a decision tree for whether you need a gateway, or
2. a reference architecture for internal + external model providers.