# MLOps (MLOps)

URL: https://www.onsomble.ai/tools/ai-glossary/mlops

Published: 2026-03-14 14:09:00.000Z

The set of practices and tools for deploying, monitoring, and maintaining machine learning models in production — essentially DevOps principles applied to the ML lifecycle.

Category: Developer Experience

## Core Components

MLOps covers the full lifecycle from trained model to production system and back. **Model versioning and registry** tracks which model version is deployed where, with full lineage back to the training data and hyperparameters that produced it — you need to reproduce any model on demand. **Deployment and serving** handles the infrastructure for getting predictions out of models at scale, whether that's batch inference, real-time API endpoints, or edge deployment. **Monitoring and drift detection** watches for the moment production data diverges from training data — models degrade silently when the world changes underneath them. **Retraining pipelines** automate the response: detect drift, trigger retraining on fresh data, validate the new model, and roll it out with minimal human intervention.

## Key Tools

The MLOps tooling ecosystem has matured significantly. **MLflow** is the open-source Swiss Army knife — experiment tracking, model registry, and deployment in one package. **Kubeflow** handles orchestration for teams already invested in Kubernetes. **Weights & Biases** has become the default for experiment tracking and visualisation, particularly popular in research-to-production workflows. Cloud providers offer integrated platforms: **AWS SageMaker**, **Google Vertex AI**, and **Azure ML** bundle training, serving, and monitoring into managed services. The trade-off is always flexibility versus convenience — managed platforms are faster to start but harder to customise as requirements become complex.

## Evolution to LLMOps

The rise of large language models has shifted the MLOps conversation. Traditional MLOps assumes you're training models from scratch — LLMOps assumes you're mostly calling APIs or fine-tuning foundation models. The new operational concerns are different: **prompt management** replaces feature engineering, **evaluation frameworks** replace traditional ML metrics (how do you measure "good" for open-ended text?), **guardrails** handle safety at inference time, and **cost monitoring** becomes critical when every API call has a per-token price. Tools like Langfuse, LangSmith, and Braintrust have emerged specifically for this LLM-era operational stack, focusing on tracing, evaluation, and prompt iteration rather than traditional model training pipelines.

## Related terms

- [Large Language Model](https://www.onsomble.ai/tools/ai-glossary/large-language-model)
- [Observability](https://www.onsomble.ai/tools/ai-glossary/observability)
- [Fine-tuning](https://www.onsomble.ai/tools/ai-glossary/fine-tuning)

## Related Radar topics

## Related articles
