dagster-mlflow
Package for mlflow Dagster framework components.
Decision gist · record as of 2026-08-14
Yes. The package is actively maintained, has no known vulnerabilities, and low install friction. It is worth installing if you are already using both Dagster and MLflow and want to unify experiment tracking with your data orchestration. If you use only one of these tools, it adds no value.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.10 or later (supports up to 3.14); dagster and mlflow must be installed as runtime dependencies.
- Low friction install with a pure Python wheel.
- Active maintenance with a release on 2026-08-14 and 15996 GitHub stars indicate a well-maintained project.
License · maintenance · safety
Apache-2.0 (permissive) — Apache-2.0 licensed under a permissive license, allowing use in commercial and proprietary projects with minimal restrictions beyond attribution.
last release 2026-08-14 (0 days) · last repo commit 2026-08-14 · 15,996 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 144,479 downloads/mo, #11,151 on PyPI
Alternatives
Verify before relying
pip install dagster-mlflow
import dagster as dg
from dagster_mlflow import mlflow_tracking
@dg.asset
@mlflow_tracking
def my_model():
return trained_model- Specific MLflow version compatibility constraints beyond the runtime dependency declaration.
- Whether the integration supports all MLflow tracking APIs or a subset of common operations.
- Performance overhead of the integration when logging large model artifacts or many experiments.
What it is and what it does
dagster-mlflow is a library that bridges MLflow's experiment tracking and model registry with Dagster's asset-oriented orchestration framework. It allows you to instrument Dagster assets with MLflow tracking decorators so that model training runs, metrics, parameters, and artifacts are automatically logged to MLflow while remaining part of your Dagster lineage graph. This is useful when you want to track ML experiments and models alongside your data pipelines, keeping both the orchestration and the ML metadata in one place.
The package depends on dagster, mlflow, pandas, and protobuf. It is maintained as part of the main Dagster project and receives regular updates. The integration is designed to work within Dagster's declarative asset model, so you define your ML workflows as Dagster assets and use the integration to connect them to MLflow's tracking backend.
Use it for
- Log model training metrics and parameters to MLflow while orchestrating the training job as a Dagster asset.
- Track model artifacts and versions in MLflow as outputs of Dagster asset runs.
- Build reproducible ML pipelines where experiment tracking is integrated into the asset lineage and observability.
- Manage model promotion and versioning through MLflow's registry while keeping orchestration logic in Dagster.
- Monitor ML experiment runs alongside data pipeline execution in a unified Dagster web UI.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes.
The package is actively maintained, has no known vulnerabilities, and low install friction. It is worth installing if you are already using both Dagster and MLflow and want to unify experiment tracking with your data orchestration. If you use only one of these tools, it adds no value.
Install
dagster-mlflow on PyPI
Before you install
Low friction install with a pure Python wheel. Active maintenance with a release on 2026-08-14 and 15996 GitHub stars indicate a well-maintained project. Depends on dagster, mlflow, pandas, and protobuf—all stable, widely-used packages.
Requires Python 3.10 or later (supports up to 3.14); dagster and mlflow must be installed as runtime dependencies.
License in practice
Apache-2.0 licensed under a permissive license, allowing use in commercial and proprietary projects with minimal restrictions beyond attribution.
Quickstart
pip install dagster-mlflow
import dagster as dg
from dagster_mlflow import mlflow_tracking
@dg.asset
@mlflow_tracking
def my_model():
return trained_model
Verify before relying
- Specific MLflow version compatibility constraints beyond the runtime dependency declaration.
- Whether the integration supports all MLflow tracking APIs or a subset of common operations.
- Performance overhead of the integration when logging large model artifacts or many experiments.
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release <3.15,>=3.10 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 4 packagesdagstermlflowpandasprotobuf |
| Maintenance | Actively maintained 0 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 144,479 / month, #11,151 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
Evidence: dagster_mlflow-0.29.18-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “mlflow dagster integration”
- dagster-mlflowIntegrates MLflow experiment tracking and model management with…
- azureml-mlflowIntegrates MLflow experiment tracking and model management with Azure…
- sagemaker-mlflowIntegrates MLflow with Amazon SageMaker by signing requests with AWS…
Give your agent the search over MCP, or paste the wish link into any chat.
More Distributed Computing packages
gRPC Python is an HTTP/2-based RPC framework that enables you to define and call remote procedures across network boundaries using protocol buffers for serialization.
Install it if you need RPC communication in a distributed system or are integrating with existing gRPC services.
execnet lets you spawn and communicate with Python interpreters across local processes, remote hosts, and different platforms, using a simple API for task distribution and inter-process messaging.
However, the aging maintenance status (275 days since last release) means you should verify it meets your concurrency and performance needs before committing to a…
Cloudpickle extends Python's standard pickle module to serialize lambda functions, interactively-defined functions and classes, and other constructs that the default pickle cannot handle, making it suitable for cluster computing and remote code execution.
Install it if you need to serialize lambda functions, interactively-defined code, or non-standard Python constructs for cluster computing or distributed execution.
Provides a unified, open()-compatible Python API for streaming large files from remote storage (S3, GCS, Azure, HDFS, SFTP, HTTP) and local filesystems, with transparent compression support.
Install it if you work with large files on cloud storage or remote systems and want to avoid writing boilerplate around multiple SDKs.
Portalocker provides cross-platform file locking with support for exclusive and shared locks, plus Redis-based distributed locks and process-aware PID file locking.
Install it if you need file or process coordination; the optional extras (pywin32, redis) are only required for specific lock types.
Ray is a distributed computing framework that scales Python applications from a single machine to multi-node clusters, providing abstractions for parallel tasks, stateful actors, and shared objects.
See also dagster · dagster-dbt · dagster-dg-core · dagster-cloud-cli · dagster-docker · dagster-webserver · dagster-pyspark · whylogs · mlflow · mlflow-skinny