---
title: "Control Plane for Multi-region Architecture (Enterprise)"
description: "import Image from '@theme/IdealImage'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';"
type: skill
canonical_url: https://claudary.paisolsolutions.com/skills/control-plane-and-data-plane
source: "Claudary"
difficulty: intermediate
author: "Claude Code Knowledge Pack"
date: 2026-07-10T11:19:01.628Z
license: CC-BY-4.0
attribution: "Control Plane for Multi-region Architecture (Enterprise) — Claudary (https://claudary.paisolsolutions.com/skills/control-plane-and-data-plane)"
---

# Control Plane for Multi-region Architecture (Enterprise)
import Image from '@theme/IdealImage'; import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem';

## Overview

import Image from '@theme/IdealImage';
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

# Control Plane for Multi-region Architecture (Enterprise)

Learn how to deploy LiteLLM across multiple regions while maintaining centralized administration and avoiding duplication of management overhead.

:::info

✨ This requires LiteLLM Enterprise features.

[Enterprise Pricing](https://www.litellm.ai/#pricing)

[Get free 7-day trial key](https://www.litellm.ai/enterprise#trial)

:::

## Overview

When scaling LiteLLM for production use, you may want to deploy multiple instances across different regions or availability zones while maintaining a single point of administration. This guide covers how to set up a distributed LiteLLM deployment with:

- **Regional Worker Instances**: Handle LLM requests for users in specific regions
- **Centralized Admin Instance**: Manages configuration, users, keys, and monitoring

## Architecture Pattern: Regional + Admin Instances

### Typical Deployment Scenario

<Image img={require('../../img/scaling_architecture.png')} />  

### Benefits of This Architecture

1. **Reduced Management Overhead**: Only one instance needs admin capabilities
2. **Regional Performance**: Users get low-latency access from their region
3. **Centralized Control**: All administration happens from a single interface
4. **Security**: Limit admin access to designated instances only
5. **Cost Efficiency**: Avoid duplicating admin infrastructure

## Configuration

### Admin Instance Configuration

The admin instance handles all management operations and provides the UI.

**Environment Variables for Admin Instance:**
```bash
# Keep admin capabilities enabled (default behavior)
# DISABLE_ADMIN_UI=false          # Admin UI available
# DISABLE_ADMIN_ENDPOINTS=false   # Management APIs available
DISABLE_LLM_API_ENDPOINTS=true      # LLM APIs disabled
DATABASE_URL=postgresql://user:pass@global-db:5432/litellm
LITELLM_MASTER_KEY=your-master-key
```

### Worker Instance Configuration

Worker instances handle LLM requests but have admin capabilities disabled.

**Environment Variables for Worker Instances:**
```bash
# Disable admin capabilities
DISABLE_ADMIN_UI=true           # No admin UI
DISABLE_ADMIN_ENDPOINTS=true    # No management endpoints

DATABASE_URL=postgresql://user:pass@global-db:5432/litellm
LITELLM_MASTER_KEY=your-master-key
```

## Environment Variables Reference

### `DISABLE_ADMIN_UI`

Disables the LiteLLM Admin UI interface.

- **Default**: `false`
- **Worker Instances**: Set to `true`
- **Admin Instance**: Leave as `false` (or don't set)

```bash
# Worker instances
DISABLE_ADMIN_UI=true
```

**Effect**: When enabled, the web UI at `/ui` becomes unavailable.

### `DISABLE_ADMIN_ENDPOINTS`

:::info

✨ This is an Enterprise feature.

[Enterprise Pricing](https://www.litellm.ai/#pricing)

[Get free 7-day trial key](https://www.litellm.ai/enterprise#trial)

:::

Disables all management/admin API endpoints.

- **Default**: `false`  
- **Worker Instances**: Set to `true`
- **Admin Instance**: Leave as `false` (or don't set)

```bash
# Worker instances  
DISABLE_ADMIN_ENDPOINTS=true
```

**Disabled Endpoints Include**:
- `/key/*` - Key management
- `/user/*` - User management  
- `/team/*` - Team management
- `/config/*` - Configuration updates
- All other administrative endpoints

**Available Endpoints** (when disabled):
- `/chat/completions` - LLM requests
- `/v1/*` - OpenAI-compatible APIs
- `/vertex_ai/*` - Vertex AI pass-through APIs
- `/bedrock/*` - Bedrock pass-through APIs
- `/health` - Basic health check
- `/metrics` - Prometheus metrics
- All other LLM API endpoints


### `DISABLE_LLM_API_ENDPOINTS`

:::info

✨ This is an Enterprise feature.

[Enterprise Pricing](https://www.litellm.ai/#pricing)

[Get free 7-day trial key](https://www.litellm.ai/enterprise#trial)

:::

Disables all LLM API endpoints.

- **Default**: `false`
- **Worker Instances**: Leave as `false` (or don't set)
- **Admin Instance**: Set to `true`

```bash
# Admin instance
DISABLE_LLM_API_ENDPOINTS=true
```


**Disabled Endpoints Include**:
- `/chat/completions` - LLM requests
- `/v1/*` - OpenAI-compatible APIs
- `/vertex_ai/*` - Vertex AI pass-through APIs
- `/bedrock/*` - Bedrock pass-through APIs
- All other LLM API endpoints


**Available Endpoints** (when disabled):
- `/key/*` - Key management
- `/user/*` - User management  
- `/team/*` - Team management
- `/config/*` - Configuration updates
- All other administrative endpoints

### `LITELLM_UI_API_DOC_BASE_URL`

Optional override for the API Reference base URL (used in sample code/docs) when the admin UI runs on a different host than the proxy.


## Usage Patterns

### Client Usage

**For LLM Requests** (use regional endpoints):
```python
import openai

# US users
client_us = openai.OpenAI(
    base_url="https://us.company.com/v1",
    api_key="your-litellm-key"
)

# EU users  
client_eu = openai.OpenAI(
    base_url="https://eu.company.com/v1", 
    api_key="your-litellm-key"
)

response = client_us.chat.completions.create(
    model="gpt-4",
    messages=[{"role": "user", "content": "Hello!"}]
)
```

**For Administration** (use admin endpoint):
```python
import requests

# Create a new API key
response = requests.post(
    "https://admin.company.com/key/generate",
    headers={"Authorization": "Bearer sk-1234"},
    json={"duration": "30d"}
)
```

## Related Documentation

- [Virtual Keys](./virtual_keys.md) - Managing API keys and users
- [Health Checks](./health.md) - Monitoring instance health  
- [Prometheus Metrics](./logging.md#prometheus-metrics) - Collecting metrics
- [Production Deployment](./prod.md) - Production best practices

---

Source: [Claudary](https://claudary.paisolsolutions.com/skills/control-plane-and-data-plane) · https://claudary.paisolsolutions.com