Simplifying ML model management

“Everyone who has tried to do machine learning development knows that it is complex. The ability to manage, version and share models is critical to minimizing confusion as the number of models in experimentation, testing and production phases at any given time can span into the thousands,” said Matei Zaharia, co-founder and CTO at Databricks. “The new additions in MLflow, developed collaboratively with hundreds of contributors, are enabling organizations worldwide to improve ML development and deployment. With hundreds of thousands of monthly downloads, we are encouraged that the community's contributions are making a positive impact.”

Databricks’ MLflow offering already has the ability to log metrics, parameters, and artifacts as part of experiments, package models and reproducible ML projects, and provide flexible deployment options within the platform or any cloud inference services or containers. The MLflow Model Registry builds on these capabilities by allowing organizations to collaborate on models and optimize the development lifecycle of ML models as they move from being logged into actual deployment through: 

• One collaborative hub: The MLflow Model Registry facilitates the sharing of expertise and knowledge about building and deploying machine learning models across development teams by making models more discoverable, and providing collaborative features to jointly improve on common ML tasks.
• Flexible CI/CD pipelines: MLflow Model Registry allows teams to remain in control of machine learning models by either automatically transitioning a model into production based on predefined conditions, or manually controlling and validating lifecycle stage changes for your models from the experimentation phase, to testing and production.
• Visibility and governance: Large enterprises often have thousands of ML models in the experimentation, testing, and production phases at any point in time. The MLflow Model Registry provides full visibility and enables governance of each by keeping track of model history and managing who can approve changes.