
# LiteLLM Proxy Self-Hosted

Self-hosted AI API gateway providing model routing, access controls and usage tracking.

Canonical page: https://launchinyourcloud.com/directory/litellm/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## LiteLLM Proxy Self-Hosted

Self-hosted AI API gateway providing model routing, access controls and usage tracking.

- Listing: https://launchinyourcloud.com/directory/litellm/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, railway, render
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT outside the enterprise directory; enterprise code and features have separate license terms.
- Licensing model: open-source
- Installation: Official container image, Docker Compose or Kubernetes deployment; production infrastructure examples are documented.
- Architecture: Customer-operated gateway with optional PostgreSQL persistence and configured model endpoints
- Operations: Customer manages gateway availability, credentials, database, access policies, logs and upgrades, including pinning versions and verifying release artifacts with the documented version-appropriate Cosign method; model providers remain separate services.
- Product website: https://www.litellm.ai/
- Source review: 2026-11-19; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The gateway forwards each request to its configured model provider. Self-hosting the proxy does not ensure prompts stay inside the account: external model APIs, guardrail services and logging integrations can receive data. Use appropriate self-hosted inference endpoints and explicitly review outbound integrations when required. For release integrity, release images and the Helm chart starting with v1.111.0-dev.3 use keyless Cosign signatures bound to LiteLLM's release workflow; earlier releases require the documented historical public keys. The October 21 incident affected PyPI v1.107.0 and Docker Hub/GHCR v1.107.0 plus mutable latest, main-latest and main-stable tags during the documented exposure windows. Check the incident's artifact digests and remediation instructions; the compromised images carried valid historical signatures, so signature verification alone does not establish safety. LiteLLM v1.110.0 changes authentication, guardrail, accounting, and S3 behavior. The 1.108.11 LTS patch also fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators; review both the selected release line and existing incident-response or image-signing guidance. LiteLLM v1.108.12 LTS fixes tool_policy allowing blocked /v1/messages tool names longer than 64 characters. The standard v1.110.1 UI image changes to slim nginx and removes curl while retaining wget and nc, so retest health probes and scripts that assume curl.

The gateway has an MIT-licensed base and separately licensed enterprise features. The enterprise documentation describes a license key enabling restricted capabilities in the gateway, beyond paid hosting or support alone.

The gateway runs as provisioned application containers or Kubernetes workloads; persistent key/spend storage can use PostgreSQL. Inference compute is a separate dependency rather than included in the gateway.


### Category fit

- ai-inference-gateways: Self-hosted model API gateway for routing, virtual keys, spend tracking and policy enforcement. It routes inference requests; it is not an inference engine for all supported models.

- ai-tools: Self-hosted AI API gateway providing model routing, access controls and usage tracking.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 

- render: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://docs.litellm.ai/docs/proxy/deploy (checked 2026-11-12). 


### Cloud deployment evidence

- LiteLLM production deployment (aws, azure, gcp): https://docs.litellm.ai/docs/proxy/deploy
  Official production guidance covers EKS, AKS and GKE with Helm, plus Terraform on AWS and Google Cloud. The proxy, database and Redis deployment is separate from the model services it calls.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- LiteLLM Railway and Render deployment options (railway, render): https://docs.litellm.ai/docs/proxy/deploy
  The current upstream deployment guide supplies Railway and Render deployment buttons in addition to its EKS/AKS/GKE instructions, followed by readiness and Admin UI verification. These are customer application deployments on managed platforms; configure persistent data, secrets and external model-provider endpoints separately.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Production deployment: https://docs.litellm.ai/docs/proxy/deploy

- Gateway request flow and functionality: https://docs.litellm.ai/docs/simple_proxy

- MIT core and enterprise exception: https://github.com/BerriAI/litellm/blob/main/LICENSE

- Licensing and edition terms: https://docs.litellm.ai/docs/enterprise

- Supply-chain incident and Cosign verification guidance: https://docs.litellm.ai/blog/security-incident-oct-21-2026

- Canonical LiteLLM incident investigation: https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain

- LiteLLM v1.110.0 release: https://github.com/BerriAI/litellm/releases/tag/v1.110.0

- LiteLLM v1.108.11 LTS release: https://github.com/BerriAI/litellm/releases/tag/v1.108.11

- LiteLLM v1.110.1: https://github.com/BerriAI/litellm/releases/tag/v1.110.1

- LiteLLM v1.108.12 LTS: https://github.com/BerriAI/litellm/releases/tag/v1.108.12

### Licensing sources

- https://github.com/BerriAI/litellm/blob/main/LICENSE

- https://docs.litellm.ai/docs/enterprise

### Infrastructure sources

- https://docs.litellm.ai/docs/proxy/deploy


### Buyer diligence


Research coverage: 6/12 fields (50%); 6 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. The Admin UI documents OIDC SSO. From 1.76.0, it is free for up to five users; larger deployments require an Enterprise licence. Configure issuer, callbacks, roles and database/master-key prerequisites. This is Admin UI identity, distinct from model API virtual keys. Scope: LiteLLM Admin UI OIDC; user-count/Enterprise entitlement applies. Source: https://docs.litellm.ai/docs/proxy/admin_ui_sso (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Release images and Helm charts use keyless Cosign from v1.111.0-dev.3; verify the documented workflow identity and issuer. Earlier releases use historical keys. The October 21 v1.107.0 compromise also affected mutable image tags; compare digests and exposure windows because affected images had valid historical signatures. Follow the incident remediation guidance for executed artifacts. Current advisory review: LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Current review: v1.108.12 LTS fixes tool_policy allowing a /v1/messages request through when a blocked tool name exceeded 64 characters. Upgrade the maintained LTS line and retest tool-policy enforcement. Scope: LiteLLM 1.108 LTS /v1/messages tool_policy; standard and other maintained lines require their own release review. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12 (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: Canonical incident investigation — https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain. Supporting source: Prior security-controls source — https://docs.litellm.ai/blog/security-incident-oct-21-2026.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official Helm guide documents Kubernetes installation and configurable database/secret settings. Select matching chart/image versions and review the separate scaling and production-readiness guidance. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.litellm.ai/docs/proxy/deploy/helm (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The current production guide starts load testing at 1 vCPU and 4 GiB per worker, preferably one worker per Kubernetes pod. Memory depends on queued requests, payloads, stream duration and logging. PostgreSQL, Redis for multiple workers/instances, HA and model inference are additional. Scope: Gateway per-worker load-test starting point; backing services and inference excluded. Source: https://docs.litellm.ai/docs/proxy/prod (reviewed 2026-11-20).

- License pricing: Documented. Core code outside litellm/enterprise is MIT licensed; the enterprise directory has separate terms. Enterprise features and support need separate entitlement and pricing. Upstream model APIs, infrastructure and operating labour are additional. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/BerriAI/litellm/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. LiteLLM v1.110.1 was published November 19, 2026. It refreshes the Wolfi base and changes the UI image to slim nginx, removing curl. The maintained v1.108.12 LTS line fixes a tool_policy bypass for blocked tool names longer than 64 characters. Scope: Upstream LiteLLM standard release; select and maintain either the standard or LTS line. Source: https://github.com/BerriAI/litellm/releases/tag/v1.110.1 (reviewed 2026-11-19). Supporting source: Prior reviewed release context — https://github.com/BerriAI/litellm/releases/tag/v1.110.0. Supporting source: LiteLLM v1.108.11 LTS — https://github.com/BerriAI/litellm/releases/tag/v1.108.11. Supporting source: v1.108.12 LTS security fix — https://github.com/BerriAI/litellm/releases/tag/v1.108.12.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- LiteLLM LTS proxy security fixes (security-advisory): LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators. Scope: LiteLLM 1.108 LTS line; standard-line deployments should use their corresponding maintained release. Conditions: Applicability depends on Bedrock guardrails and team-setting permissions. Action: Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.11; reviewed 2026-11-18.

- LiteLLM 1.108.12 LTS tool-policy fix (security-advisory): LiteLLM 1.108.12 LTS prevents blocked tool names longer than 64 characters from bypassing tool_policy on /v1/messages. Scope: LiteLLM 1.108 LTS /v1/messages tool-policy enforcement. Conditions: The request must use a blocked tool name longer than 64 characters. Action: Upgrade the maintained LTS line to 1.108.12 or later and retest tool-policy enforcement. Source: https://github.com/BerriAI/litellm/releases/tag/v1.108.12; reviewed 2026-11-19.



