{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","category":{"description":"AI applications, model operations, inference and supporting vector databases.","id":"ai-tools","name":"AI tools \u0026 infrastructure"},"cloud":{"boundary":"Render workspace, project and services; platform-managed infrastructure","classificationReview":{"reviewed":"2026-11-20","source":"https://render.com/docs/deploys","summary":"Hosted application platform; a workspace is not a customer-owned underlying hyperscaler account."},"defaultBoundary":"platform-workspace","diligence":[{"reviewed":"2026-11-14","source":"https://render.com/docs/private-network","summary":"Services in the same region can use Render private networking. Free web services can send but cannot receive private-network requests. Review the actual paid service and endpoint requirements.","topic":"Private networking"}],"id":"render","identity":"Workspace membership and deployment credentials","install":"Deploy application services and databases using a Blueprint or Docker/source build; configure persistent disks, secrets and recovery.","name":"Render","network":"Private services with separately exposed public endpoints","providerType":"application-platform","reviewed":"2026-11-12","short":"Render","source":"https://render.com/docs/deploys"},"kind":"cloud-category","listings":[{"architecture":"Customer-operated trace/evaluation application with persistent trace and dataset storage","categories":["ai-observability","ai-tools"],"category":"AI observability \u0026 LLMOps","categoryFit":{"ai-observability":"AI trace collection, evaluation, datasets, experiments and prompt analysis for instrumented model applications.","ai-tools":"AI development and operations tooling for tracing and evaluation rather than a model-serving runtime."},"cloudEvidence":[{"clouds":["aws","azure","gcp","railway"],"notes":"The current Phoenix self-hosting index includes a Railway one-click template as well as AWS CloudFormation, Azure ARM and Google Cloud Run. These deploy the Phoenix application, not the separately licensed Arize AX product. A Railway project is customer-controlled while Railway manages its infrastructure.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Phoenix self-hosting deployment options","url":"https://arize.com/docs/phoenix/self-hosting","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"The vendor self-hosting index offers a Render one-click Blueprint for Phoenix alongside its Railway, AWS, Azure and Google Cloud options. This is the self-hosted Phoenix application, separate from Arize AX; customer workspace control does not imply ownership of the platform infrastructure.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Phoenix self-hosted Render Blueprint","url":"https://arize.com/docs/phoenix/self-hosting","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","railway","render"],"communityAcceptance":{"reviewed":"2026-11-10","sources":[{"title":"Maintainer account of user-contributed authentication and integrations","url":"https://arize.com/blog/phoenix-10k/"},{"title":"Current Phoenix maintenance releases","url":"https://github.com/Arize-ai/phoenix/releases"}],"summary":"Arize's June 2026 maintainer account describes actual participation outside the core team: it attributes OIDC authentication to users needing Keycloak/Cognito and credits contributors with expanding framework integrations and OpenInference. The upstream release history shows continuing maintenance. This concerns concrete community involvement rather than repository star counts; it does not certify any named customer's deployment model."},"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"AI observability and evaluation server for traces, datasets and application experiments.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Phoenix self-hosted application and data services; numeric workload sizing unresolved","source":"https://arize.com/docs/phoenix/self-hosting/deploying-phoenix.md","status":"inconclusive","summary":"The self-hosting guide documents deployment, storage/database configuration and trace retention, but does not establish a complete CPU/RAM minimum for a specified workload. Size span ingestion, retention, database, evaluation/model dependencies and redundant service instances. Hosted Arize AX sizing is a separate offering."},"iac":{"artifactRef":"repository default branch (moving; select matching application release)","artifactUrl":"https://github.com/arize-ai/phoenix","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://github.com/arize-ai/phoenix","status":"documented","summary":"The upstream Phoenix repository provides self-hosting/container documentation for the observability server. Match persistence and authentication settings to the chosen release; instrumented applications and model services remain separate."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE","status":"documented","summary":"Phoenix uses Elastic License 2.0, including limits on offering substantial hosted/managed functionality and bypassing licence controls. This is not an unrestricted Apache/MIT licence or a hosted-service price; review commercial service/support terms separately."},"release":{"releasePublishedAt":"2026-11-13T06:26:01Z","releaseTag":"arize-phoenix-v21.1.0","reviewed":"2026-11-14","scope":"Upstream Arize-ai/phoenix release record; commercial editions and deployment packages may differ","source":"https://github.com/Arize-ai/phoenix/releases/tag/arize-phoenix-v21.1.0","status":"documented","summary":"The publisher-designated GitHub release checked was arize-phoenix-v21.1.0, published 2026-11-13. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted Phoenix UI OAuth2/OIDC","source":"https://arize.com/docs/phoenix/deployment/authentication","status":"documented","summary":"Phoenix documents OAuth2 authorization-code login with OIDC provider discovery, configured alongside application authentication and secret settings. Configure the trusted provider, callback and account policy; client API keys remain a separate surface."}},"id":"phoenix","infrastructure":["servers"],"infrastructureNotes":"Customer-operated trace/evaluation application with persistent trace and dataset storage. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://arize.com/docs/phoenix/self-hosting"],"install":"Use the official self-hosted Docker/Compose or Kubernetes deployment instructions and configure persistent storage and instrumentation endpoints.","installMethods":["docker"],"kind":"product","license":"Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available.","licenseModel":"source-available","licenseModelNotes":"Elastic License 2.0; includes restrictions on providing the software as a hosted/managed service and on license-key circumvention. This is source-available. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.","licenseModelSources":["https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Arize Phoenix Self-Hosted","notes":"The self-hosted product is distinct from commercial Arize offerings. Traces may contain prompts and outputs; evaluation jobs can call separately configured external model services even when trace storage is local.","operations":"Customer manages trace capture, storage, authentication, retention, evaluation providers, backups and upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Official installation and runtime","url":"https://arize.com/docs/phoenix/self-hosting"},{"title":"Upstream project and capabilities","url":"https://github.com/Arize-ai/phoenix"},{"title":"Current upstream license","url":"https://raw.githubusercontent.com/Arize-ai/phoenix/main/LICENSE"}],"url":"https://launchinyourcloud.com/directory/phoenix/","website":"https://arize.com/phoenix/"},{"advisories":[{"action":"Upgrade to v4.82.0 or later and restrict outbound SSO connectivity.","conditions":"Requires the affected GitHub Enterprise SSO configuration and a reachable outbound target.","id":"langfuse-4-82-0-github-enterprise-sso-ssrf","listingIds":["langfuse"],"reviewed":"2026-11-18","scope":"Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.","source":"https://github.com/langfuse/langfuse/releases/tag/v4.82.0","summary":"Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO.","title":"Langfuse GitHub Enterprise SSO SSRF fix","type":"security-advisory"}],"architecture":"Application and worker containers with PostgreSQL, ClickHouse, Redis/Valkey and object storage","categories":["ai-observability","ai-tools","observability"],"category":"AI observability \u0026 LLMOps","categoryFit":{"ai-observability":"LLM/agent tracing, evaluation and prompt management deployed with customer-controlled storage. Evaluation and optional gateway providers must be scoped independently.","ai-tools":"Self-hosted LLM observability, evaluations and prompt-management platform.","observability":"Application/model traces and experiment visibility for AI workloads. Infrastructure metrics and broader application monitoring require separately selected tooling."},"cloudEvidence":[{"clouds":["aws"],"notes":"The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse customer cloud deployment on AWS","url":"https://langfuse.com/self-hosting/deployment/aws","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse customer cloud deployment on Azure","url":"https://langfuse.com/self-hosting/deployment/azure","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The vendor documents deployment of the self-hosted Langfuse application and its backing services in the customer account or project, including provider-specific infrastructure. This is distinct from Langfuse Cloud; database, object storage, model calls and enterprise licensing must be configured for the chosen topology.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse customer cloud deployment on Google Cloud","url":"https://langfuse.com/self-hosting/deployment/gcp","vendorSupport":"not-assessed"},{"clouds":["railway"],"notes":"The vendor documents a community-maintained Railway template for the complete Langfuse v3 stack. This establishes that version-specific application deployment; the same page explicitly distinguishes the v4 alternatives. The vendor does not systematically test the community template. Review the template services, image tags, database timezones and upgrade path.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse v3 community Railway deployment","url":"https://langfuse.com/self-hosting/deployment/railway","vendorSupport":"not-assessed"},{"clouds":["render"],"notes":"The vendor documents a community-maintained v4 Blueprint with separate web and worker services, PostgreSQL, Key Value, ClickHouse and MinIO. It creates the full application in the customer Render workspace. Review service plans, persistent disks, object-storage exposure and recovery procedures; community support is best-effort.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Langfuse v4 community Render Blueprint","url":"https://langfuse.com/self-hosting/deployment/render","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","cloudScope":"Documented provider-specific deployment","clouds":["aws","azure","gcp","railway","render"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[2],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[3],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[4],"operator":"customer"}],"description":"Self-hosted LLM observability, evaluations and prompt-management platform.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Langfuse Web/Worker resource recommendation; backing services additional","source":"https://langfuse.com/self-hosting/deployment/infrastructure/containers","status":"documented","summary":"The vendor recommends at least 2 CPUs and 4 GB RAM for application containers and at least two Web instances for HA. Worker, ClickHouse, PostgreSQL, Redis and blob storage capacity are additional. Confirm per-container resources and retention/ingestion volume rather than treating this as the whole-stack footprint."},"iac":{"artifactRef":"main (moving branch)","artifactUrl":"https://github.com/langfuse/langfuse/blob/main/docker-compose.yml","reviewed":"2026-11-14","scope":"Upstream Compose recipe; supporting-service operations remain customer responsibilities","source":"https://github.com/langfuse/langfuse/blob/main/docker-compose.yml","status":"documented","summary":"The upstream Compose recipe defines application services and backing data services. Pin a compatible Langfuse release and review credentials, persistent storage and exposed ports."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/langfuse/langfuse/main/LICENSE","status":"documented","summary":"Core code is MIT licensed, while ee directories, including application and worker enterprise paths, use a separate enterprise licence. Optional commercial features and support need separate terms; underlying databases, object storage and model services are additional."},"release":{"releasePublishedAt":"2026-11-17T14:28:42Z","releaseTag":"v4.82.0","reviewed":"2026-11-18","scope":"Upstream Langfuse self-hosted release","source":"https://github.com/langfuse/langfuse/releases/tag/v4.82.0","status":"documented","summary":"Langfuse v4.82.0 was published November 17, 2026. It fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse."},"securityControls":{"reviewed":"2026-11-18","scope":"Upstream v4.82.0 release; the vendor did not publish an affected-version range in the reviewed note.","source":"https://github.com/langfuse/langfuse/releases/tag/v4.82.0","status":"documented","summary":"Current advisory review: Langfuse v4.82.0 fixes a server-side request forgery path in GitHub Enterprise SSO. Upgrade to v4.82.0 or later and restrict outbound SSO connectivity."},"sso":{"availability":"available","reviewed":"2026-11-20","scope":"Self-hosted OAuth/OIDC sign-in","source":"https://langfuse.com/self-hosting/security/authentication-and-sso","status":"documented","summary":"The self-hosted guide documents OAuth/OIDC providers including Keycloak, Okta, Entra ID and a custom issuer. Configure account linking, email verification and access policy; SCIM and separately licensed enterprise features require their own review."}},"id":"langfuse","infrastructure":["servers"],"infrastructureNotes":"The documented deployment uses application/worker containers and persistent database, cache and object-storage services. Host/cluster capacity and database operations remain part of the self-hosted system.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://langfuse.com/self-hosting/deployment/docker-compose","https://langfuse.com/self-hosting/deployment/aws","https://langfuse.com/self-hosting/deployment/azure","https://langfuse.com/self-hosting/deployment/gcp"],"install":"Docker Compose for a single VM; Helm/Kubernetes and official AWS, Azure and Google Cloud Terraform modules.","installMethods":["terraform","helm","docker"],"kind":"product","license":"MIT core; designated enterprise directories and add-on capabilities use separate license terms or keys.","licenseModel":"open-source","licenseModelNotes":"The main codebase uses MIT terms outside designated enterprise directories. Enterprise code requires a separate valid license, so the directory treats the combined product as open-core.","licenseModelSources":["https://github.com/langfuse/langfuse/blob/main/LICENSE","https://github.com/langfuse/langfuse/blob/main/ee/LICENSE"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"Langfuse Self-Hosted","notes":"Traces can contain prompts, outputs and other sensitive application data, so configure capture and retention deliberately. Self-hosted trace storage does not move the underlying application model into the same account. Optional model-based evaluators or the gateway use configured providers, which may be external. The single-VM Compose example does not provide production high availability or backups. Langfuse v4.82.0 fixes an SSRF path in GitHub Enterprise SSO and moves audit logs to ClickHouse. Review outbound SSO connectivity and audit-log storage during upgrade.","operations":"Customer operates the deployment, persistence, access policies, retention, backups and scaling.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"Docker Compose on a VM","url":"https://langfuse.com/self-hosting/deployment/docker-compose"},{"title":"Self-hosting architecture and provider dependencies","url":"https://langfuse.com/self-hosting"},{"title":"AWS account Terraform deployment","url":"https://langfuse.com/self-hosting/deployment/aws"},{"title":"Azure account Terraform deployment","url":"https://langfuse.com/self-hosting/deployment/azure"},{"title":"Google Cloud account Terraform deployment","url":"https://langfuse.com/self-hosting/deployment/gcp"},{"title":"Core and enterprise licensing","url":"https://github.com/langfuse/langfuse/blob/main/LICENSE"},{"title":"Licensing and edition terms","url":"https://github.com/langfuse/langfuse/blob/main/ee/LICENSE"},{"title":"Langfuse v3 community Railway deployment","url":"https://langfuse.com/self-hosting/deployment/railway"},{"title":"Langfuse v4 community Render Blueprint","url":"https://langfuse.com/self-hosting/deployment/render"},{"title":"Langfuse v4.82.0 release","url":"https://github.com/langfuse/langfuse/releases/tag/v4.82.0"}],"url":"https://launchinyourcloud.com/directory/langfuse/","website":"https://langfuse.com/"},{"advisories":[{"action":"Upgrade the selected release line and recheck guardrail output and proxy-administrator permissions.","conditions":"Applicability depends on Bedrock guardrails and team-setting permissions.","id":"litellm-1-108-11-lts-security-fixes","listingIds":["litellm"],"reviewed":"2026-11-18","scope":"LiteLLM 1.108 LTS line; standard-line deployments should use their corresponding maintained release.","source":"https://github.com/BerriAI/litellm/releases/tag/v1.108.11","summary":"LiteLLM 1.108.11 LTS fixes Bedrock guarded_text handling and restricts os.environ team settings to proxy administrators.","title":"LiteLLM LTS proxy security fixes","type":"security-advisory"},{"action":"Upgrade the maintained LTS line to 1.108.12 or later and retest tool-policy enforcement.","conditions":"The request must use a blocked tool name longer than 64 characters.","disclosedOn":"2026-11-19","id":"litellm-1-108-12-tool-policy-bypass","listingIds":["litellm"],"reviewed":"2026-11-19","scope":"LiteLLM 1.108 LTS /v1/messages tool-policy enforcement.","source":"https://github.com/BerriAI/litellm/releases/tag/v1.108.12","summary":"LiteLLM 1.108.12 LTS prevents blocked tool names longer than 64 characters from bypassing tool_policy on /v1/messages.","title":"LiteLLM 1.108.12 LTS tool-policy fix","type":"security-advisory"}],"architecture":"Customer-operated gateway with optional PostgreSQL persistence and configured model endpoints","categories":["ai-inference-gateways","ai-tools"],"category":"AI inference \u0026 gateways","categoryFit":{"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."},"cloudEvidence":[{"clouds":["aws","azure","gcp"],"notes":"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.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"LiteLLM production deployment","url":"https://docs.litellm.ai/docs/proxy/deploy","vendorSupport":"not-assessed"},{"clouds":["railway","render"],"notes":"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.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"LiteLLM Railway and Render deployment options","url":"https://docs.litellm.ai/docs/proxy/deploy","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp","railway","render"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"not-assessed","evidence":[0],"operator":"customer"},{"boundary":"platform-workspace","cloud":"railway","controlPlane":"not-assessed","evidence":[1],"operator":"customer"},{"boundary":"platform-workspace","cloud":"render","controlPlane":"not-assessed","evidence":[1],"operator":"customer"}],"description":"Self-hosted AI API gateway providing model routing, access controls and usage tracking.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Gateway per-worker load-test starting point; backing services and inference excluded","source":"https://docs.litellm.ai/docs/proxy/prod","status":"documented","summary":"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."},"iac":{"reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://docs.litellm.ai/docs/proxy/deploy/helm","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/BerriAI/litellm/main/LICENSE","status":"documented","summary":"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."},"release":{"releasePublishedAt":"2026-11-19T05:05:03Z","releaseTag":"v1.110.1","reviewed":"2026-11-19","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","status":"documented","summary":"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.","supportingSources":[{"title":"Prior reviewed release context","url":"https://github.com/BerriAI/litellm/releases/tag/v1.110.0"},{"title":"LiteLLM v1.108.11 LTS","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.11"},{"title":"v1.108.12 LTS security fix","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.12"}]},"securityControls":{"reviewed":"2026-11-19","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","status":"documented","summary":"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.","supportingSources":[{"title":"Prior security-controls source","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.11"},{"title":"Canonical incident investigation","url":"https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain"},{"title":"Prior security-controls source","url":"https://docs.litellm.ai/blog/security-incident-oct-21-2026"}]},"sso":{"availability":"edition-dependent","reviewed":"2026-11-20","scope":"LiteLLM Admin UI OIDC; user-count/Enterprise entitlement applies","source":"https://docs.litellm.ai/docs/proxy/admin_ui_sso","status":"documented","summary":"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."}},"id":"litellm","infrastructure":["servers"],"infrastructureNotes":"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.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.litellm.ai/docs/proxy/deploy"],"install":"Official container image, Docker Compose or Kubernetes deployment; production infrastructure examples are documented.","installMethods":["docker"],"kind":"product","license":"MIT outside the enterprise directory; enterprise code and features have separate license terms.","licenseModel":"open-source","licenseModelNotes":"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.","licenseModelSources":["https://github.com/BerriAI/litellm/blob/main/LICENSE","https://docs.litellm.ai/docs/enterprise"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"LiteLLM Proxy Self-Hosted","notes":"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.","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.","publisher":false,"reviewed":"2026-11-19","sources":[{"title":"Production deployment","url":"https://docs.litellm.ai/docs/proxy/deploy"},{"title":"Gateway request flow and functionality","url":"https://docs.litellm.ai/docs/simple_proxy"},{"title":"MIT core and enterprise exception","url":"https://github.com/BerriAI/litellm/blob/main/LICENSE"},{"title":"Licensing and edition terms","url":"https://docs.litellm.ai/docs/enterprise"},{"title":"Supply-chain incident and Cosign verification guidance","url":"https://docs.litellm.ai/blog/security-incident-oct-21-2026"},{"title":"Canonical LiteLLM incident investigation","url":"https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain"},{"title":"LiteLLM v1.110.0 release","url":"https://github.com/BerriAI/litellm/releases/tag/v1.110.0"},{"title":"LiteLLM v1.108.11 LTS release","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.11"},{"title":"LiteLLM v1.110.1","url":"https://github.com/BerriAI/litellm/releases/tag/v1.110.1"},{"title":"LiteLLM v1.108.12 LTS","url":"https://github.com/BerriAI/litellm/releases/tag/v1.108.12"}],"url":"https://launchinyourcloud.com/directory/litellm/","website":"https://www.litellm.ai/"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/clouds/render/ai-tools/"}