Skip to content

zenml-io/zenml

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

MLOps for Reliable AI - From Classical ML to Agents

Your unified toolkit for shipping everything from decision trees to complex AI agents, built on the MLOps principles you already trust.

Features β€’ Roadmap β€’ Report Bug β€’ Sign up for ZenML Pro β€’ Blog β€’ Podcast

πŸŽ‰ For the latest release, see the release notes.


🚨 The Problem: MLOps Works for Models, But What About AI?

No MLOps for modern AI

You're an ML engineer. You've perfected deploying scikit-learn models and wrangling PyTorch jobs. Your MLOps stack is dialed in. But now, you're being asked to build and ship AI agents, and suddenly your trusted toolkit is starting to crack.

  • The Adaptation Struggle: Your MLOps habits (rigorous testing, versioning, CI/CD) don’t map cleanly onto agent development. How do you version a prompt? How do you regression test a non-deterministic system? The tools that gave you confidence for models now create friction for agents.

  • The Divided Stack: To cope, teams are building a second, parallel stack just for LLM-based systems. Now you’re maintaining two sets of tools, two deployment pipelines, and two mental models. Your classical models live in one world, your agents in another. It's expensive, complex, and slows everyone down.

  • The Broken Feedback Loop: Getting an agent from your local environment to production is a slow, painful journey. By the time you get feedback on performance, cost, or quality, the requirements have already changed. Iteration is a guessing game, not a data-driven process.

πŸ’‘ The Solution: One Framework for your Entire AI Stack

Stop maintaining two separate worlds. ZenML is a unified MLOps framework that extends the battle-tested principles you rely on for classical ML to the new world of AI agents. It’s one platform to develop, evaluate, and deploy your entire AI portfolio.

# Morning: Your sklearn pipeline is still versioned and reproducible.
train_and_deploy_classifier()

# Afternoon: Your new agent evaluation pipeline uses the same logic.
evaluate_and_deploy_agent()

# Same platform. Same principles. New possibilities.

With ZenML, you're not replacing your knowledge; you're extending it. Use the pipelines and practices you already know to version, test, deploy, and monitor everything from classic models to the most advanced agents.

πŸ’» See It In Action: Multi-Agent Architecture Comparison

The Challenge: Your team built three different customer service agents. Which one should go to production? With ZenML, you can build a reproducible pipeline to test them on real data and make a data-driven decision.

from zenml import pipeline, step
import pandas as pd

@step
def load_real_conversations() -> pd.DataFrame:
    """Load actual customer queries from a feature store."""
    return load_from_feature_store("customer_queries_sample_1k")

@step
def run_architecture_comparison(queries: pd.DataFrame) -> dict:
    """Test three different agent architectures on the same data."""
    architectures = {
        "single_agent": SingleAgentRAG(),
        "multi_specialist": MultiSpecialistAgents(),
        "hierarchical": HierarchicalAgentTeam()
    }
    
    results = {}
    for name, agent in architectures.items():
        # ZenML automatically versions the agent's code, prompts, and tools
        results[name] = agent.batch_process(queries)
    return results

@step
def evaluate_and_decide(results: dict) -> str:
    """Evaluate results and generate a recommendation report."""
    # Compare architectures on quality, cost, latency, etc.
    evaluation_df = evaluate_results(results)
    
    # Generate a rich report comparing the architectures
    report = create_comparison_report(evaluation_df)
    
    # Automatically tag the winning architecture for a staging deployment
    winner = evaluation_df.sort_values("overall_score").iloc[0]
    tag_for_staging(winner["architecture_name"])
    
    return report

@pipeline
def compare_agent_architectures():
    """Your new Friday afternoon ritual: data-driven agent decisions."""
    queries = load_real_conversations()
    results = run_architecture_comparison(queries)
    report = evaluate_and_decide(results)

if __name__ == "__main__":
    # Run locally, compare results in the ZenML dashboard
    compare_agent_architectures()

The Result: A clear winner is selected based on data, not opinions. You have full lineage from the test data and agent versions to the final report and deployment decision.

πŸ”„ The AI Development Lifecycle with ZenML

From Chaos to Process

Development lifecycle

Click to see your new, structured workflow

Your New Workflow

Monday: Quick Prototype

# Start with a local script, just like always
agent = LangGraphAgent(prompt="You are a helpful assistant...")
response = agent.chat("Help me with my order")

Tuesday: Make it a Pipeline

# Wrap your code in a ZenML step to make it reproducible
@step
def customer_service_agent(query: str) -> str:
    return agent.chat(query)

Wednesday: Add Evaluation

# Test on real data, not toy examples
@pipeline
def eval_pipeline():
    test_data = load_production_samples()
    responses = customer_service_agent.map(test_data)
    scores = evaluate_responses(responses)
    track_experiment(scores)

Thursday: Compare Architectures

# Make data-driven architecture decisions
results = compare_architectures(
    baseline="current_prod",
    challenger="new_multiagent_v2"
)

Friday: Ship with Confidence

# Deploy the new agent with the same command you use for ML models
python agent_deployment.py --env=prod --model="customer_service:challenger"

πŸš€ Get Started (5 minutes)

For ML Engineers Ready to Tame AI

# You know this drill
pip install zenml  # Includes LangChain, LlamaIndex integrations
zenml integration install langchain llamaindex

# Initialize (your ML pipelines still work!)
zenml init

# Pull our agent evaluation template
zenml init --template agent-evaluation-starter

Your First AI Pipeline

# look_familiar.py
from zenml import pipeline, step

@step
def run_my_agent(test_queries: list[str]) -> list[str]:
    """Your existing agent code, now with MLOps superpowers."""
    # Use ANY framework - LangGraph, CrewAI, raw OpenAI
    agent = YourExistingAgent()
    
    # Automatic versioning of prompts, tools, code, and configs
    return [agent.run(q) for q in test_queries]

@step
def evaluate_responses(queries: list[str], responses: list[str]) -> dict:
    """LLM judges + your custom business metrics."""
    quality = llm_judge(queries, responses)
    latency = measure_response_times()
    costs = calculate_token_usage()
    
    return {
        "quality": quality.mean(),
        "p95_latency": latency.quantile(0.95),
        "cost_per_query": costs.mean()
    }

@pipeline
def my_first_agent_pipeline():
    # Look ma, no YAML!
    queries = ["How do I return an item?", "What's your refund policy?"]
    responses = run_my_agent(queries)
    metrics = evaluate_responses(queries, responses)
    
    # Metrics are auto-logged, versioned, and comparable in the dashboard
    return metrics

if __name__ == "__main__":
    my_first_agent_pipeline()
    print("Check your dashboard: http://localhost:8080")

πŸ“š Learn More

πŸ–ΌοΈ Getting Started Resources

The best way to learn about ZenML is through our comprehensive documentation and tutorials:

For visual learners, start with this 11-minute introduction:

Introductory Youtube Video

πŸ“– Production Examples

  1. E2E Batch Inference - Complete MLOps pipeline with feature engineering
  2. LLM RAG Pipeline - Production RAG with evaluation loops
  3. Agentic Workflow (Deep Research) - Orchestrate your agents with ZenML
  4. Fine-tuning Pipeline - Fine-tune and deploy LLMs

🏒 Deployment Options

For Teams:

  • Self-hosted - Deploy on your infrastructure with Helm/Docker
  • ZenML Pro - Managed service with enterprise support (free trial)

Infrastructure Requirements:

  • Kubernetes cluster (or local Docker)
  • Object storage (S3/GCS/Azure)
  • PostgreSQL database
  • Complete requirements

πŸŽ“ Books & Resources

ZenML is featured in these comprehensive guides to production AI systems.

🀝 Join ML Engineers Building the Future of AI

Contribute:

Stay Updated:

  • πŸ—Ί Public Roadmap - See what's coming next
  • πŸ“° Blog - Best practices and case studies
  • πŸŽ™ Podcast - Interviews with ML practitioners

❓ FAQs from ML Engineers Like You

Q: "Do I need to rewrite my agents or models to use ZenML?" A: No. Wrap your existing code in a @step. Keep using scikit-learn, PyTorch, LangGraph, LlamaIndex, or raw API calls. ZenML orchestrates your tools, it doesn't replace them.

Q: "How is this different from LangSmith/Langfuse?" A: They provide excellent observability for LLM applications. We orchestrate the full MLOps lifecycle for your entire AI stack. With ZenML, you manage both your classical ML models and your AI agents in one unified framework, from development and evaluation all the way to production deployment.

Q: "Can I use my existing MLflow/W&B setup?" A: Yes! We integrate with both. Your experiments, our pipelines.

Q: "Is this just MLflow with extra steps?" A: No. MLflow tracks experiments. We orchestrate the entire development process – from training and evaluation to deployment and monitoring – for both models and agents.

Q: "What about cost? I can't afford another platform." A: ZenML's open-source version is free forever. You likely already have the required infrastructure (like a Kubernetes cluster and object storage). We just help you make better use of it for MLOps.

πŸ›  VS Code Extension

Manage pipelines directly from your editor:

πŸ–₯️ VS Code Extension in Action!
ZenML Extension

Install from VS Code Marketplace.

πŸ“œ License

ZenML is distributed under the terms of the Apache License Version 2.0. See LICENSE for details.