MLflow

MLflow is an open-source platform for managing the machine learning lifecycle, enabling teams to track experiments, evaluate and monitor LLM and agent…

  • AI
  • Tools & Utilities
MLflow is an open-source platform for managing the machine learning lifecycle, enabling teams to track experiments, evaluate and monitor LLM and agent applications, and deploy models to production.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

78/100 Good

Maintained
100last commit 4 days ago
Popular
8928,858 GitHub stars
Easy to install
251 install platform, install notes
Light to run
701 GB minimum RAM

Availability: platform listings confirmed today

GitHub stars
28,858
Open issues
2256
Last commit
2026-11-17
Latest release
v3.18.0
License
Apache-2.0
Activity
steady

Checked 4 days ago - source: GitHub (mlflow/mlflow)

Resources & Compatibility

Minimum requirements: 1 GB RAM, 2 CPU core(s).

Checked 40 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install MLflow with Python 3.10+ Install the `mlflow` package with `pip install mlflow`, then start the app with `mlflow server`. You need Python 3.10 or newer; without a supported Python, the server will not start. source
  • Point tracing and server at the same store When you log traces, set a tracking URI (the address telling tools where metadata is stored) such as `-u sqlite:///mlflow.db`, and start the server with the same `--backend-store-uri`. If the two locations do not match, your runs and traces may be saved but not visible in the UI. source
  • Keep your mlflow.db file safe The local setup stores data in `sqlite:///mlflow.db`, a SQLite database file (a simple file-based database). If you delete or move it without updating the URI, your saved runs and traces can disappear from the server. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why does mlflow server not start after installing it?

It requires Python 3.10 or newer. Without a supported Python version, the server will not start.

Why are logged runs or traces not visible in the MLflow UI?

The client tracking URI and the server backend-store URI must point to the same store. If they differ, the data may be saved but not visible in the UI.

What port does the default local MLflow server use?

After starting the server with uvx mlflow server, the UI is available on localhost port 5000.

Answers sourced from github.com, github.com, github.com

Community

Collected 48 days ago - public community threads