
# MLflow Tracking Server Self-Hosted

Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.

Canonical page: https://launchinyourcloud.com/directory/mlflow/
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.


## MLflow Tracking Server Self-Hosted

Self-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.

- Listing: https://launchinyourcloud.com/directory/mlflow/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache 2.0 for upstream MLflow; connected model providers and managed distributions have separate terms.
- Licensing model: open-source
- Installation: Python MLflow server command, official Docker Compose bundle or Kubernetes Helm deployment.
- Architecture: Customer-operated tracking/API server with configurable metadata database and artifact storage
- Operations: Customer operates server access, metadata and artifact stores, retention, backups, scaling and version upgrades.
- Product website: https://mlflow.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

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.

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.


### Category fit

- 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.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/aws/ (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/azure/ (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/ (checked 2026-11-12). 


### Cloud deployment evidence

- Self-hosted MLflow deployment on AWS (aws): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/aws/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Self-hosted MLflow deployment on Azure (azure): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/azure/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Self-hosted MLflow deployment on Google Cloud (gcp): https://mlflow.org/docs/latest/self-hosting/deploy-to-cloud/gcp/
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Self-hosting server and deployment methods: https://mlflow.org/docs/latest/self-hosting/

- LLM/agent tracing and captured data: https://mlflow.org/docs/latest/genai/tracing/

- Apache 2.0 license: https://github.com/mlflow/mlflow/blob/master/LICENSE.txt

### Licensing sources

- https://github.com/mlflow/mlflow/blob/master/LICENSE.txt

### Infrastructure sources

- https://mlflow.org/docs/latest/self-hosting/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 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: Documented. 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. Scope: Officially documented community-plugin/proxy integration. Source: https://mlflow.org/docs/latest/self-hosting/security/sso/ (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://mlflow.org/docs/latest/self-hosting/ (reviewed 2026-11-14). Deployment artifact: https://github.com/mlflow/mlflow/tree/master/docker-compose. Artifact reference: master Compose bundle (moving).

- Minimum footprint / sizing: Sources checked — unresolved. 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. Scope: Self-hosted tracking-server topology; numeric production sizing unresolved. Source: https://mlflow.org/docs/latest/self-hosting/architecture/tracking-server/ (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/mlflow/mlflow/master/LICENSE.txt (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. 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. Scope: Upstream mlflow/mlflow release record; commercial editions and deployment packages may differ. Source: https://github.com/mlflow/mlflow/releases/tag/v3.18.0 (reviewed 2026-11-14).






