# Self-host MLflow

> Track experiments, compare runs, and manage models with a self-hosted MLflow tracking server.

- Page: https://levelrail.com/templates/mlflow/
- JSON: https://levelrail.com/templates/mlflow.json
- Category: AI
- Licence: Apache-2.0 (Permissive license)
- Source: https://github.com/mlflow/mlflow
- Upstream docs: https://mlflow.org/docs/latest

## Requirements
- Memory: about 1 GiB
- amd64: published, arm64: published
- Needs configuration before start: no
- Pinned image tag: v3.16.1

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| mlflow | ghcr.io/mlflow/mlflow | v3.16.1 | 5000 | mlflow_data -> /mlflow |

## Deploy

### CLI

```bash
levelrail-cli templates deploy mlflow --name my-mlflow
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/mlflow/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## Questions

### Can I deploy MLflow on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for MLflow, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image ghcr.io/mlflow/mlflow:v3.16.1 is what you deploy there.

Self-host MLflow, MLflow docker compose file, deploy MLflow on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
