{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","category":{"description":"Model and LLM traces, experiments, evaluation and operational visibility.","id":"ai-observability","name":"AI observability \u0026 LLMOps"},"cloud":{"boundary":"Google Cloud project","classificationReview":{"reviewed":"2026-11-20","source":"https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects","summary":"Navigation group for the documented infrastructure offering; read each application path for its actual account boundary."},"defaultBoundary":"cloud-account","diligence":[{"reviewed":"2026-11-14","source":"https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers","summary":"Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement.","topic":"Private offers"},{"reviewed":"2026-11-14","source":"https://docs.cloud.google.com/vpc/docs/private-service-connect","summary":"Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture.","topic":"Private connectivity"},{"reviewed":"2026-11-14","source":"https://docs.cloud.google.com/iam/docs/workload-identity-federation","summary":"Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles.","topic":"External workload access"},{"reviewed":"2026-11-14","source":"https://docs.cloud.google.com/assured-workloads/docs/overview","summary":"Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification.","topic":"Regulated environments"}],"id":"gcp","identity":"IAM policies and service accounts","install":"Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.","name":"Google Cloud","network":"VPC network","providerType":"cloud-infrastructure","reviewed":"2026-11-10","short":"Google Cloud","source":"https://docs.cloud.google.com/infrastructure-manager/docs/overview"},"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/"},{"architecture":"Customer-operated tracking/API server with configurable metadata database and artifact storage","categories":["ai-observability","ai-tools","observability"],"category":"AI observability \u0026 LLMOps","categoryFit":{"ai-observability":"Experiment tracking and LLM/agent tracing server. This entry describes customer-hosted tracking/observability services, not every model runtime, managed MLflow product or inference backend.","ai-tools":"Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.","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 project documents deployment of the MLflow server, metadata database and artifact storage on AWS. This does not refer to a managed MLflow edition or to model serving alone.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Self-hosted MLflow deployment on AWS","url":"https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/aws/","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"The project documents deployment of the MLflow server, metadata database and artifact storage on Azure. This does not refer to a managed MLflow edition or to model serving alone.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Self-hosted MLflow deployment on Azure","url":"https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/azure/","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"The project documents deployment of the MLflow server, metadata database and artifact storage on Google Cloud. This does not refer to a managed MLflow edition or to model serving alone.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Self-hosted MLflow deployment on Google Cloud","url":"https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"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"}],"description":"Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Self-hosted tracking-server topology; numeric production sizing unresolved","source":"https://mlflow.org/docs/latest/self-hosting/architecture/tracking-server/","status":"inconclusive","summary":"The self-hosted guide documents the UI/API tracking server, metadata backend and artifact-store configuration, but not a universal production CPU/RAM minimum. Size runs/traces, request concurrency, database, artifact storage and redundancy; starting the default local SQLite server does not establish production or HA capacity."},"iac":{"artifactRef":"master Compose bundle (moving)","artifactUrl":"https://github.com/mlflow/mlflow/tree/master/docker-compose","reviewed":"2026-11-14","scope":"Upstream self-hosted deployment; not a provider support or production-readiness certification","source":"https://mlflow.org/docs/latest/self-hosting/","status":"documented","summary":"The self-hosting guide links an upstream Compose bundle with MLflow, PostgreSQL and object storage, plus an official Helm option. Configure production credentials and persistence rather than retaining development defaults."},"licensePricing":{"reviewed":"2026-11-20","scope":"Upstream core licence; commercial features, support and hosting priced separately","source":"https://raw.githubusercontent.com/mlflow/mlflow/master/LICENSE.txt","status":"documented","summary":"The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate."},"release":{"releasePublishedAt":"2026-11-04T06:51:02Z","releaseTag":"v3.18.0","reviewed":"2026-11-14","scope":"Upstream mlflow/mlflow release record; commercial editions and deployment packages may differ","source":"https://github.com/mlflow/mlflow/releases/tag/v3.18.0","status":"documented","summary":"The publisher-designated GitHub release checked was v3.18.0, published 2026-11-04. 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":"Officially documented community-plugin/proxy integration","source":"https://mlflow.org/docs/latest/self-hosting/security/sso/","status":"documented","summary":"The official guide documents the community-maintained mlflow-oidc-auth plugin and an SSO reverse-proxy pattern. This provides UI/API OIDC integration, but plugin maintenance, MLflow-version compatibility and client token behavior require separate review; it is not a claim of vendor-operated identity support."}},"id":"mlflow","infrastructure":["servers"],"infrastructureNotes":"The tracking server runs as a Python service or container with metadata/artifact stores. A local SQLite example is not a production architecture; separately plan persistent database, storage and application-runtime infrastructure.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://mlflow.org/docs/latest/self-hosting/"],"install":"Python MLflow server command, official Docker Compose bundle or Kubernetes Helm deployment.","installMethods":["helm","docker","source"],"kind":"product","license":"Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms.","licenseModel":"open-source","licenseModelNotes":"The upstream self-hosted tracking server is Apache-2.0 licensed. This classification does not extend to separate managed MLflow distributions, connected model providers or their commercial services.","licenseModelSources":["https://github.com/mlflow/mlflow/blob/master/LICENSE.txt"],"licenseReviewed":"2026-11-10","model":"Fully in your account","modelLabel":"Customer-operated","name":"MLflow Tracking Server Self-Hosted","notes":"Traces can capture model inputs, outputs and intermediate metadata. Point clients at the customer-hosted server and review recording/redaction settings. Applications, evaluators and optional model integrations may still call external providers; hosting the tracking server does not host all training or inference runtimes. Production database, storage and security configuration differ from a local quickstart.","operations":"Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.","publisher":false,"reviewed":"2026-11-12","sources":[{"title":"Self-hosting server and deployment methods","url":"https://mlflow.org/docs/latest/self-hosting/"},{"title":"LLM/agent tracing and captured data","url":"https://mlflow.org/docs/latest/genai/tracing/"},{"title":"Apache 2.0 license","url":"https://github.com/mlflow/mlflow/blob/master/LICENSE.txt"}],"url":"https://launchinyourcloud.com/directory/mlflow/","website":"https://mlflow.org/"}],"schemaVersion":1,"url":"https://launchinyourcloud.com/clouds/gcp/ai-observability/"}