MLOps lifecycle template

The machine learning loop from problem framing to monitored production model, with retraining when data drifts.

Use this templateFree, opens in your browser. No sign-up.

MLOps lifecycle template
Tooling
Frame the problem + success metric
Collect + version data (DVC)
Validate + label data
Feature engineering (feature store)
Train, tracking runs in MLflow
Evaluate vs baseline + fairness checks
Beats prod?
Register model version
Deploy: shadow → canary → full
Monitor drift, accuracy, latency
Pipelines: Kubeflow, SageMaker or Vertex AI
Tracking + model registry: MLflow
Monitoring: Evidently or WhyLabs
Retrain when drift passes a threshold or monthly
MLOps lifecycle
no: iterate
drift → retrain
The MLOps lifecycle template as it opens in Kelvo: 10 boxes, 1 decision among them, 4 sticky notes and 11 links.

What's on the board

Tooling
Pipelines: Kubeflow, SageMaker or Vertex AI · Tracking + model registry: MLflow · Monitoring: Evidently or WhyLabs · Retrain when drift passes a threshold or monthly

Also on the board

  • Frame the problem + success metric
  • Feature engineering (feature store)
  • Collect + version data (DVC)
  • Train, tracking runs in MLflow
  • Validate + label data
  • Monitor drift, accuracy, latency
  • Evaluate vs baseline + fairness checks
  • Beats prod?
  • Deploy: shadow → canary → full
  • Register model version

How to use this template

  1. Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
  2. Double-click any box to change its text. Replace the examples with your own content.
  3. Sketch, then convert. Draw boxes and arrows with the pen, select the strokes and click Convert sketch: they become real boxes and links.
  4. Ask Kelvo right on the board (Pro). With Pro, type @kelvo and what you want in any box or text, for example “@kelvo add error handling”, and press Enter. The change is made there and the request disappears; ⌘Z undoes it.
  5. Keep the prompt next to the diagram. Add a code block from the Insert (+) menu for prompts, schemas or config, right beside the boxes they belong to.

Good for

  • ai
  • machine learning
  • mlops
  • data science
  • model deployment
  • Explaining an LLM feature's architecture to engineers and stakeholders
  • Deciding between prompting, retrieval and fine-tuning
  • Planning evaluations and risks before launch

Related templates

  • ML feature store template previewML feature store

    How a feature store serves the same features to training and real-time inference: batch and streaming pipelines, offline and online stores.

  • ML experiment tracker template previewML experiment tracker

    Log every model experiment with its hypothesis, change, metrics and decision, so the team knows what worked and what to try next.

  • Data labeling pipeline template previewData labeling pipeline

    Who does what when labeling training data: guidelines, model pre-labels, double annotation, QA on agreement and retraining.

  • RAG pipeline template previewRAG pipeline

    Retrieval-augmented generation end to end: ingest and embed documents offline, then retrieve, rerank and answer with citations.

  • LLM agent loop template previewLLM agent loop

    How a tool-using agent plans, calls tools, observes results and updates memory until the goal is met, with guardrails.

  • Prompt design canvas template previewPrompt design canvas

    Design a production prompt piece by piece — role, context, task, constraints, examples, output format — plus test cases.

All ai and machine learning diagram templates · All templates

Use the MLOps lifecycle template