Why choose Charmed MLflow?

Are you considering using Charmed MLflow? Wondering what the advantages are of charmed MLflow vs. upstream MLflow?

Knowing the answer to this will help any prospective MLflow users decide whether they want the charmed version.

Simplified deployment

Charmed MLflow offers simplified deployment. Like any charmed product, Charmed MLflow is deployed as a charm bundle using Juju. Deploying an application with Juju is arguably simpler than deploying to a raw Kubernetes cluster.

Security, stability, and maintenance

Charmed MLflow benefits from the following:

  • Upgrade guides.

  • Automated security scanning: The bundle is scanned periodically.

  • Security patching: Charmed MLflow follows Canonical’s process and procedure for security patching. Vulnerabilities are prioritised based on severity, the presence of patches in the upstream project, and the risk of exploitation.

  • Maintained images: All Charmed MLflow images are actively maintained.

  • Comprehensive testing: Charmed MLflow is thoroughly tested on multiple platforms, including public cloud, local workstations, on-premises deployments, and various CNCF-compliant Kubernetes distributions.


Charmed MLflow provides integration capabilities, including:

  • Customised Prometheus exporter metrics

  • Customised MLflow dashboard for Grafana

  • Canonical Observability Stack

  • Charmed Kubeflow: including the ability use the MLflow registry directly from Kubeflow pipelines and notebooks

Enterprise Offering

Charmed MLflow offers an enterprise offering from Canonical, which includes:

  • 24/7 support for deployment, up-time monitoring, and security patching with Charmed MLflow.

  • Hardening features and compliance with standards like Federal Risk and Authorisation Management Program, Health Insurance Portability and Accountability Act, and Payment Card Industry Digital Signature Standard, making it suitable for enterprises running AI/ML workloads in highly regulated environments.

  • Timely patches for common vulnerabilities and exposures (CVEs).

  • A ten-year security maintenance commitment.

  • Hybrid cloud and multi-cloud support.

  • Bug fixing.

  • Optionally managed services, allowing your team to focus on development rather than operations.

  • Consultancy services to assess the best tools and architecture for your specific use cases.

  • A simple per-node subscription model.