2 2
3> Learn how Claude Code can integrate with various third-party services and infrastructure to meet enterprise deployment requirements.3> Learn how Claude Code can integrate with various third-party services and infrastructure to meet enterprise deployment requirements.
4 4
5This page provides an overview of available deployment options and helps you choose the right configuration for your organization.5Organizations can deploy Claude Code through Anthropic directly or through a cloud provider. This page helps you choose the right configuration.
6 6
7## Provider comparison7## Compare deployment options
8
9For most organizations, Claude for Teams or Claude for Enterprise provides the best experience. Team members get access to both Claude Code and Claude on the web with a single subscription, centralized billing, and no infrastructure setup required.
10
11**Claude for Teams** is self-service and includes collaboration features, admin tools, and billing management. Best for smaller teams that need to get started quickly.
12
13**Claude for Enterprise** adds SSO and domain capture, role-based permissions, compliance API access, and managed policy settings for deploying organization-wide Claude Code configurations. Best for larger organizations with security and compliance requirements.
14
15Learn more about [Team plans](https://support.claude.com/en/articles/9266767-what-is-the-team-plan) and [Enterprise plans](https://support.claude.com/en/articles/9797531-what-is-the-enterprise-plan).
16
17If your organization has specific infrastructure requirements, compare the options below:
8 18
9<table>19<table>
10 <thead>20 <thead>
11 <tr>21 <tr>
12 <th>Feature</th>22 <th>Feature</th>
13 <th>Anthropic</th>23 <th>Claude for Teams/Enterprise</th>
24 <th>Anthropic Console</th>
14 <th>Amazon Bedrock</th>25 <th>Amazon Bedrock</th>
15 <th>Google Vertex AI</th>26 <th>Google Vertex AI</th>
16 <th>Microsoft Foundry</th>27 <th>Microsoft Foundry</th>
18 </thead>29 </thead>
19 30
20 <tbody>31 <tbody>
32 <tr>
33 <td>Best for</td>
34 <td>Most organizations (recommended)</td>
35 <td>Individual developers</td>
36 <td>AWS-native deployments</td>
37 <td>GCP-native deployments</td>
38 <td>Azure-native deployments</td>
39 </tr>
40
41 <tr>
42 <td>Billing</td>
43 <td><strong>Teams:</strong> \$150/seat (Premium) with PAYG available<br /><strong>Enterprise:</strong> <a href="https://claude.com/contact-sales">Contact Sales</a></td>
44 <td>PAYG</td>
45 <td>PAYG through AWS</td>
46 <td>PAYG through GCP</td>
47 <td>PAYG through Azure</td>
48 </tr>
49
21 <tr>50 <tr>
22 <td>Regions</td>51 <td>Regions</td>
23 <td>Supported [countries](https://www.anthropic.com/supported-countries)</td>52 <td>Supported [countries](https://www.anthropic.com/supported-countries)</td>
53 <td>Supported [countries](https://www.anthropic.com/supported-countries)</td>
24 <td>Multiple AWS [regions](https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html)</td>54 <td>Multiple AWS [regions](https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html)</td>
25 <td>Multiple GCP [regions](https://cloud.google.com/vertex-ai/generative-ai/docs/learn/locations)</td>55 <td>Multiple GCP [regions](https://cloud.google.com/vertex-ai/generative-ai/docs/learn/locations)</td>
26 <td>Multiple Azure [regions](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/)</td>56 <td>Multiple Azure [regions](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/)</td>
32 <td>Enabled by default</td>62 <td>Enabled by default</td>
33 <td>Enabled by default</td>63 <td>Enabled by default</td>
34 <td>Enabled by default</td>64 <td>Enabled by default</td>
65 <td>Enabled by default</td>
35 </tr>66 </tr>
36 67
37 <tr>68 <tr>
38 <td>Authentication</td>69 <td>Authentication</td>
70 <td>Claude.ai SSO or email</td>
39 <td>API key</td>71 <td>API key</td>
40 <td>API key or AWS credentials</td>72 <td>API key or AWS credentials</td>
41 <td>GCP credentials</td>73 <td>GCP credentials</td>
44 76
45 <tr>77 <tr>
46 <td>Cost tracking</td>78 <td>Cost tracking</td>
47 <td>Dashboard</td>79 <td>Usage dashboard</td>
80 <td>Usage dashboard</td>
48 <td>AWS Cost Explorer</td>81 <td>AWS Cost Explorer</td>
49 <td>GCP Billing</td>82 <td>GCP Billing</td>
50 <td>Azure Cost Management</td>83 <td>Azure Cost Management</td>
51 </tr>84 </tr>
52 85
86 <tr>
87 <td>Includes Claude on web</td>
88 <td>Yes</td>
89 <td>No</td>
90 <td>No</td>
91 <td>No</td>
92 <td>No</td>
93 </tr>
94
53 <tr>95 <tr>
54 <td>Enterprise features</td>96 <td>Enterprise features</td>
55 <td>Teams, usage monitoring</td>97 <td>Team management, SSO, usage monitoring</td>
98 <td>None</td>
56 <td>IAM policies, CloudTrail</td>99 <td>IAM policies, CloudTrail</td>
57 <td>IAM roles, Cloud Audit Logs</td>100 <td>IAM roles, Cloud Audit Logs</td>
58 <td>RBAC policies, Azure Monitor</td>101 <td>RBAC policies, Azure Monitor</td>
60 </tbody>103 </tbody>
61</table>104</table>
62 105
63## Cloud providers106Select a deployment option to view setup instructions:
64
65<CardGroup cols={3}>
66 <Card title="Amazon Bedrock" icon="aws" href="/en/amazon-bedrock">
67 Use Claude models through AWS infrastructure with API key or IAM-based authentication and AWS-native monitoring
68 </Card>
69
70 <Card title="Google Vertex AI" icon="google" href="/en/google-vertex-ai">
71 Access Claude models via Google Cloud Platform with enterprise-grade security and compliance
72 </Card>
73
74 <Card title="Microsoft Foundry" icon="microsoft" href="/en/microsoft-foundry">
75 Access Claude through Azure with API key or Microsoft Entra ID authentication and Azure billing
76 </Card>
77</CardGroup>
78
79## Corporate infrastructure
80
81<CardGroup cols={2}>
82 <Card title="Enterprise Network" icon="shield" href="/en/network-config">
83 Configure Claude Code to work with your organization's proxy servers and SSL/TLS requirements
84 </Card>
85 107
86 <Card title="LLM Gateway" icon="server" href="/en/llm-gateway">108* [Claude for Teams or Enterprise](/en/iam#claude-for-teams-or-enterprise-recommended)
87 Deploy centralized model access with usage tracking, budgeting, and audit logging109* [Anthropic Console](/en/iam#claude-console-authentication)
88 </Card>110* [Amazon Bedrock](/en/amazon-bedrock)
89</CardGroup>111* [Google Vertex AI](/en/google-vertex-ai)
112* [Microsoft Foundry](/en/microsoft-foundry)
90 113
91## Configuration overview114## Configure proxies and gateways
92 115
93Claude Code supports flexible configuration options that allow you to combine different providers and infrastructure:116Most organizations can use a cloud provider directly without additional configuration. However, you may need to configure a corporate proxy or LLM gateway if your organization has specific network or management requirements. These are different configurations that can be used together:
94 117
95<Note>118* **Corporate proxy**: Routes traffic through an HTTP/HTTPS proxy. Use this if your organization requires all outbound traffic to pass through a proxy server for security monitoring, compliance, or network policy enforcement. Configure with the `HTTPS_PROXY` or `HTTP_PROXY` environment variables. Learn more in [Enterprise network configuration](/en/network-config).
96 Understand the difference between:119* **LLM Gateway**: A service that sits between Claude Code and the cloud provider to handle authentication and routing. Use this if you need centralized usage tracking across teams, custom rate limiting or budgets, or centralized authentication management. Configure with the `ANTHROPIC_BASE_URL`, `ANTHROPIC_BEDROCK_BASE_URL`, or `ANTHROPIC_VERTEX_BASE_URL` environment variables. Learn more in [LLM gateway configuration](/en/llm-gateway).
97 120
98 * **Corporate proxy**: An HTTP/HTTPS proxy for routing traffic (set via `HTTPS_PROXY` or `HTTP_PROXY`)121The following examples show the environment variables to set in your shell or shell profile (`.bashrc`, `.zshrc`). See [Settings](/en/settings) for other configuration methods.
99 * **LLM Gateway**: A service that handles authentication and provides provider-compatible endpoints (set via `ANTHROPIC_BASE_URL`, `ANTHROPIC_BEDROCK_BASE_URL`, or `ANTHROPIC_VERTEX_BASE_URL`)
100 122
101 Both configurations can be used in tandem.123### Amazon Bedrock
102</Note>
103 124
104### Using Bedrock with corporate proxy125<Tabs>
126 <Tab title="Corporate proxy">
127 Route Bedrock traffic through your corporate proxy by setting the following [environment variables](/en/settings#environment-variables):
105 128
106Route Bedrock traffic through a corporate HTTP/HTTPS proxy:129 ```bash theme={null}
130 # Enable Bedrock
131 export CLAUDE_CODE_USE_BEDROCK=1
132 export AWS_REGION=us-east-1
107 133
108```bash theme={null}134 # Configure corporate proxy
109# Enable Bedrock135 export HTTPS_PROXY='https://proxy.example.com:8080'
110export CLAUDE_CODE_USE_BEDROCK=1136 ```
111export AWS_REGION=us-east-1137 </Tab>
112 138
113# Configure corporate proxy139 <Tab title="LLM Gateway">
114export HTTPS_PROXY='https://proxy.example.com:8080'140 Route Bedrock traffic through your LLM gateway by setting the following [environment variables](/en/settings#environment-variables):
115```
116 141
117### Using Bedrock with LLM Gateway142 ```bash theme={null}
143 # Enable Bedrock
144 export CLAUDE_CODE_USE_BEDROCK=1
118 145
119Use a gateway service that provides Bedrock-compatible endpoints:146 # Configure LLM gateway
147 export ANTHROPIC_BEDROCK_BASE_URL='https://your-llm-gateway.com/bedrock'
148 export CLAUDE_CODE_SKIP_BEDROCK_AUTH=1 # If gateway handles AWS auth
149 ```
150 </Tab>
151</Tabs>
120 152
121```bash theme={null}153### Microsoft Foundry
122# Enable Bedrock
123export CLAUDE_CODE_USE_BEDROCK=1
124 154
125# Configure LLM gateway155<Tabs>
126export ANTHROPIC_BEDROCK_BASE_URL='https://your-llm-gateway.com/bedrock'156 <Tab title="Corporate proxy">
127export CLAUDE_CODE_SKIP_BEDROCK_AUTH=1 # If gateway handles AWS auth157 Route Foundry traffic through your corporate proxy by setting the following [environment variables](/en/settings#environment-variables):
128```
129 158
130### Using Foundry with corporate proxy159 ```bash theme={null}
160 # Enable Microsoft Foundry
161 export CLAUDE_CODE_USE_FOUNDRY=1
162 export ANTHROPIC_FOUNDRY_RESOURCE=your-resource
163 export ANTHROPIC_FOUNDRY_API_KEY=your-api-key # Or omit for Entra ID auth
131 164
132Route Azure traffic through a corporate HTTP/HTTPS proxy:165 # Configure corporate proxy
166 export HTTPS_PROXY='https://proxy.example.com:8080'
167 ```
168 </Tab>
133 169
134```bash theme={null}170 <Tab title="LLM Gateway">
135# Enable Microsoft Foundry171 Route Foundry traffic through your LLM gateway by setting the following [environment variables](/en/settings#environment-variables):
136export CLAUDE_CODE_USE_FOUNDRY=1
137export ANTHROPIC_FOUNDRY_RESOURCE=your-resource
138export ANTHROPIC_FOUNDRY_API_KEY=your-api-key # Or omit for Entra ID auth
139 172
140# Configure corporate proxy173 ```bash theme={null}
141export HTTPS_PROXY='https://proxy.example.com:8080'174 # Enable Microsoft Foundry
142```175 export CLAUDE_CODE_USE_FOUNDRY=1
143 176
144### Using Foundry with LLM Gateway177 # Configure LLM gateway
178 export ANTHROPIC_FOUNDRY_BASE_URL='https://your-llm-gateway.com'
179 export CLAUDE_CODE_SKIP_FOUNDRY_AUTH=1 # If gateway handles Azure auth
180 ```
181 </Tab>
182</Tabs>
145 183
146Use a gateway service that provides Azure-compatible endpoints:184### Google Vertex AI
147 185
148```bash theme={null}186<Tabs>
149# Enable Microsoft Foundry187 <Tab title="Corporate proxy">
150export CLAUDE_CODE_USE_FOUNDRY=1188 Route Vertex AI traffic through your corporate proxy by setting the following [environment variables](/en/settings#environment-variables):
151 189
152# Configure LLM gateway190 ```bash theme={null}
153export ANTHROPIC_FOUNDRY_BASE_URL='https://your-llm-gateway.com'191 # Enable Vertex
154export CLAUDE_CODE_SKIP_FOUNDRY_AUTH=1 # If gateway handles Azure auth192 export CLAUDE_CODE_USE_VERTEX=1
155```193 export CLOUD_ML_REGION=us-east5
194 export ANTHROPIC_VERTEX_PROJECT_ID=your-project-id
156 195
157### Using Vertex AI with corporate proxy196 # Configure corporate proxy
197 export HTTPS_PROXY='https://proxy.example.com:8080'
198 ```
199 </Tab>
158 200
159Route Vertex AI traffic through a corporate HTTP/HTTPS proxy:201 <Tab title="LLM Gateway">
202 Route Vertex AI traffic through your LLM gateway by setting the following [environment variables](/en/settings#environment-variables):
160 203
161```bash theme={null}204 ```bash theme={null}
162# Enable Vertex205 # Enable Vertex
163export CLAUDE_CODE_USE_VERTEX=1206 export CLAUDE_CODE_USE_VERTEX=1
164export CLOUD_ML_REGION=us-east5
165export ANTHROPIC_VERTEX_PROJECT_ID=your-project-id
166 207
167# Configure corporate proxy208 # Configure LLM gateway
168export HTTPS_PROXY='https://proxy.example.com:8080'209 export ANTHROPIC_VERTEX_BASE_URL='https://your-llm-gateway.com/vertex'
169```210 export CLAUDE_CODE_SKIP_VERTEX_AUTH=1 # If gateway handles GCP auth
211 ```
212 </Tab>
213</Tabs>
170 214
171### Using Vertex AI with LLM Gateway215<Tip>
172 216 Use `/status` in Claude Code to verify your proxy and gateway configuration is applied correctly.
173Combine Google Vertex AI models with an LLM gateway for centralized management:217</Tip>
174
175```bash theme={null}
176# Enable Vertex
177export CLAUDE_CODE_USE_VERTEX=1
178
179# Configure LLM gateway
180export ANTHROPIC_VERTEX_BASE_URL='https://your-llm-gateway.com/vertex'
181export CLAUDE_CODE_SKIP_VERTEX_AUTH=1 # If gateway handles GCP auth
182```
183
184### Authentication configuration
185
186Claude Code uses the `ANTHROPIC_AUTH_TOKEN` for the `Authorization` header when needed. The `SKIP_AUTH` flags (`CLAUDE_CODE_SKIP_BEDROCK_AUTH`, `CLAUDE_CODE_SKIP_VERTEX_AUTH`) are used in LLM gateway scenarios where the gateway handles provider authentication.
187
188## Choosing the right deployment configuration
189
190Consider these factors when selecting your deployment approach:
191
192### Direct provider access
193
194Best for organizations that:
195
196* Want the simplest setup
197* Have existing AWS or GCP infrastructure
198* Need provider-native monitoring and compliance
199
200### Corporate proxy
201
202Best for organizations that:
203
204* Have existing corporate proxy requirements
205* Need traffic monitoring and compliance
206* Must route all traffic through specific network paths
207
208### LLM Gateway
209
210Best for organizations that:
211
212* Need usage tracking across teams
213* Want to dynamically switch between models
214* Require custom rate limiting or budgets
215* Need centralized authentication management
216
217## Debugging
218
219When debugging your deployment:
220
221* Use the `claude /status` [slash command](/en/slash-commands). This command provides observability into any applied authentication, proxy, and URL settings.
222* Set environment variable `export ANTHROPIC_LOG=debug` to log requests.
223 218
224## Best practices for organizations219## Best practices for organizations
225 220
226### 1. Invest in documentation and memory221### Invest in documentation and memory
227 222
228We strongly recommend investing in documentation so that Claude Code understands your codebase. Organizations can deploy CLAUDE.md files at multiple levels:223We strongly recommend investing in documentation so that Claude Code understands your codebase. Organizations can deploy CLAUDE.md files at multiple levels:
229 224
230* **Organization-wide**: Deploy to system directories like `/Library/Application Support/ClaudeCode/CLAUDE.md` (macOS) for company-wide standards225* **Organization-wide**: Deploy to system directories like `/Library/Application Support/ClaudeCode/CLAUDE.md` (macOS) for company-wide standards
231* **Repository-level**: Create `CLAUDE.md` files in repository roots containing project architecture, build commands, and contribution guidelines. Check these into source control so all users benefit226* **Repository-level**: Create `CLAUDE.md` files in repository roots containing project architecture, build commands, and contribution guidelines. Check these into source control so all users benefit
232 227
233 [Learn more](/en/memory).228Learn more in [Memory and CLAUDE.md files](/en/memory).
234 229
235### 2. Simplify deployment230### Simplify deployment
236 231
237If you have a custom development environment, we find that creating a "one click" way to install Claude Code is key to growing adoption across an organization.232If you have a custom development environment, we find that creating a "one click" way to install Claude Code is key to growing adoption across an organization.
238 233
239### 3. Start with guided usage234### Start with guided usage
240 235
241Encourage new users to try Claude Code for codebase Q\&A, or on smaller bug fixes or feature requests. Ask Claude Code to make a plan. Check Claude's suggestions and give feedback if it's off-track. Over time, as users understand this new paradigm better, then they'll be more effective at letting Claude Code run more agentically.236Encourage new users to try Claude Code for codebase Q\&A, or on smaller bug fixes or feature requests. Ask Claude Code to make a plan. Check Claude's suggestions and give feedback if it's off-track. Over time, as users understand this new paradigm better, then they'll be more effective at letting Claude Code run more agentically.
242 237
243### 4. Configure security policies238### Configure security policies
244 239
245Security teams can configure managed permissions for what Claude Code is and is not allowed to do, which cannot be overwritten by local configuration. [Learn more](/en/security).240Security teams can configure managed permissions for what Claude Code is and is not allowed to do, which cannot be overwritten by local configuration. [Learn more](/en/security).
246 241
247### 5. Leverage MCP for integrations242### Leverage MCP for integrations
248 243
249MCP is a great way to give Claude Code more information, such as connecting to ticket management systems or error logs. We recommend that one central team configures MCP servers and checks a `.mcp.json` configuration into the codebase so that all users benefit. [Learn more](/en/mcp).244MCP is a great way to give Claude Code more information, such as connecting to ticket management systems or error logs. We recommend that one central team configures MCP servers and checks a `.mcp.json` configuration into the codebase so that all users benefit. [Learn more](/en/mcp).
250 245
252 247
253## Next steps248## Next steps
254 249
255* [Set up Amazon Bedrock](/en/amazon-bedrock) for AWS-native deployment250Once you've chosen a deployment option and configured access for your team:
256* [Configure Google Vertex AI](/en/google-vertex-ai) for GCP deployment251
257* [Set up Microsoft Foundry](/en/microsoft-foundry) for Azure deployment2521. **Roll out to your team**: Share installation instructions and have team members [install Claude Code](/en/setup) and authenticate with their credentials.
258* [Configure Enterprise Network](/en/network-config) for network requirements2532. **Set up shared configuration**: Create a [CLAUDE.md file](/en/memory) in your repositories to help Claude Code understand your codebase and coding standards.
259* [Deploy LLM Gateway](/en/llm-gateway) for enterprise management2543. **Configure permissions**: Review [security settings](/en/security) to define what Claude Code can and cannot do in your environment.
260* [Settings](/en/settings) for configuration options and environment variables
261 255
262 256
263---257---
