β¨ Enterprise
- New to Enterprise? Start with the β¨ Enterprise Quickstart
- Free trial: 30-day enterprise license
- Talk to us: Book a demo
- SSO is free for up to 5 users. Beyond that, an enterprise license is required.
Who is Enterprise for?β
For teams running LiteLLM at scale β 100+ users or 10+ production AI use-cases β that need SSO, audit logs, fine-grained access control, and professional support on top of OSS. Not sure if you qualify? Get in touch.
Why Enterprise?β
LiteLLM OSS already covers the fundamentals β an OpenAI-compatible gateway, virtual keys, spend tracking, budgets, fallbacks, and request/response logging. Enterprise adds the controls larger organizations need to safely give hundreds of users and dozens of applications access to LLMs.
| OSS | Enterprise | |
|---|---|---|
| Auth | API keys | SSO + SCIM, OIDC/JWT |
| Key Management | Virtual keys, users, teams across LLM APIs, MCPs, and Agents | Organizations, org/team admins, delegated admin roles |
| Security | β | Key rotations, read/write to secret manager |
| Guardrails | Always-on / request-based1 | Key and team scoped guardrails |
| Logging | Request/response logging, Prometheus metrics | Per-key / per-team routing to Langfuse, Langsmith, Arize and more. Management-op logs |
| Deployment | Single-region proxy | Multi-region deployment under one license, admin/worker split |
1 The OSS guardrail framework supports custom guardrails plus Presidio (PII masking). Several built-in callback integrations β including llmguard_moderations, llamaguard_moderations, hide_secrets, openai_moderations, google_text_moderation, lakera_prompt_injection, and aporia_prompt_injection β require a LiteLLM Enterprise license.
Core Enterprise Featuresβ
Security & Access Controlβ
- SSO for the Admin UI β Okta, Azure AD, Google Workspace, and any OIDC/SAML provider
- JWT-based Authentication β Authenticate requests with your identity provider's tokens
- Audit Logs with retention policies β Track every admin action and key-level change
- Role-Based Access Control β Organizations, teams, and user roles
- Public & private route controls β Restrict admin routes, lock down surface area
- IP address-based access control lists β Restrict proxy access to specific CIDR ranges
- Key Rotations β Automate rotation for virtual keys
- Secret Managers β AWS KMS, AWS Secrets Manager, Azure Key Vault, Google KMS, Google Secret Manager, HashiCorp Vault, CyberArk, or a custom secret manager
- AI Hub β Share a public, branded page of available models and agents with your users
Governance & Cost Controlβ
- Multi-tenant Architecture β Organizations β Teams β Projects β Keys
- Project Management β Group keys by application or use-case with budgets, owners, and isolated spend tracking
- Tag-based Budgets β Budgets and spend tracking by custom tag
- Model-specific Budgets per Virtual Key β Different limits per model, per key
- Temporary Budget Increases β Time-boxed spend bumps without permanent changes
- Soft Budget Email Alerts β Warn teams before they hit hard limits
- Generate Spend Reports β Programmatic access to spend by key/team/tag/model
Observability & Complianceβ
- Team-Based Logging β Route each team's logs to their own Langfuse project or callback
- Disable logging per team β GDPR-friendly opt-out at the team level
- Log export to GCS / Azure Blob β Durable storage for compliance
- Guardrails per key/team β Secret redaction, content moderation, banned keywords
- Enforced required params β Reject requests missing required metadata
Operations & Brandingβ
- Custom Swagger branding β Your title, description, and filtered routes
- Custom email branding β Your logo and colors on system emails
- Max request/response size limits β Protect the proxy from runaway payloads
- Team-managed models β Let teams bring their own keys and fine-tunes
Projectsβ
Projects let you group virtual keys by application or use-case. Each project has its own budget, owners, rate limits, and isolated spend view β useful when a single team runs multiple apps and needs separate reporting per app.
- Group keys by application, environment, or customer
- Per-project budgets, rate limits, and model allowlists
- Dedicated owners and spend dashboards
- Works with organizations, teams, and tags
See Project Management and the UI walkthrough for setup.
Deployment Optionsβ
Self-Hostedβ
Deploy our Docker image (or build from the pip package) on your own infrastructure. We provide a license key that unlocks the enterprise features above, plus a dedicated support channel.
LITELLM_LICENSE="eyJ..."
No data leaves your environment. Procurement available via AWS and Azure Marketplace.
Pricing depends on your deployment size β get in touch to scope it.
Professional Supportβ
Standard Support (included)β
Included with every enterprise license: a dedicated Slack/Teams channel with our engineering team for integration, deployment, and provider troubleshooting. Support hours are 9am to 9pm PST, Monday through Friday. No guaranteed response time is included.
24/7 Support SLAs (additional fee)β
For teams that need guaranteed response times around the clock, we offer 24/7 Support SLAs for an additional fee on top of standard support.
| Severity | Response SLA |
|---|---|
| Sev 0 β 100% production traffic failing | 1 hour |
| Sev 1 β partial production impact | 6 hours |
| Sev 2β3 β setup issues, non-urgent bugs | 24 hours (7amβ7pm PT, MonβSat) |
| Security patches | 72 hours |
Custom SLAs available on request.
Version supportβ
LiteLLM supports the four most recent stable minor lines. Each of those lines keeps getting patch releases; anything older reaches end of life and stops receiving updates. This policy takes effect Monday, June 29, 2026. As of mid-June 2026 the supported lines are 1.86, 1.87, 1.88, and 1.89, and the set rolls forward as new stable releases ship.
Why we are doing this. LiteLLM ships fast, with a new minor line going out roughly every week. Patching lines well down the list meant carrying every fix forward onto every line we kept alive, a cost that grows with the number of lines we maintain rather than the number of fixes we make. Focusing on four lines lets us give each one more care.
How it works. The window always holds the four most recent stable minor lines. When we promote a new line, the oldest one drops out and stops receiving releases. End of life is a clean cutoff; there is no separate long-term maintenance track. For any supported line, the recommended build is its latest patch. For rare, high-severity issues we will use our judgment and may act beyond the window when the situation calls for it.
What it means for you. To check where you stand, take the latest stable line and count back four; if your version is older than that, plan an upgrade. The simplest path is to pin to a minor line, take its patches, and move onto a newer line before yours drops out.
Public AI Hubβ
Share a public page of available models, MCP, Agents and skills for users
Secret Managersβ
LiteLLM Enterprise integrates with the following secret managers:
- AWS KMS
- AWS Secrets Manager
- Azure Key Vault
- Google KMS
- Google Secret Manager
- HashiCorp Vault
- CyberArk
- Custom Secret Manager
See the Secret Managers overview for setup.
FAQβ
How do I set up and verify an Enterprise License?β
-
Add the license key to your environment:
LITELLM_LICENSE="eyJ..." -
Restart LiteLLM Proxy.
-
Open
http://<your-proxy-host>:<port>/β the Swagger page should show "Enterprise Edition" in the description. If it doesn't, confirm the key is correct, unexpired, and that the proxy was fully restarted.
Where can I read more about data security and compliance?β
See Data Security / Legal / Compliance FAQs.
How is pricing structured?β
Pricing is based on usage. Contact us for a quote tailored to your team.
How do I get day-0 support for new models without restarting?β
Use Auto Sync New Models to pull the latest pricing and context-window data from GitHub on demand or on a schedule β no restart required. Trigger a manual sync with POST /reload/model_cost_map, or schedule periodic syncs with POST /schedule/model_cost_map_reload?hours=6.