ZenML screenshot thumbnail

ZenML

ML and AI engineers wrap existing code in a step, and ZenML turns it into a tracked pipeline that runs unchanged on a laptop, Kubernetes, Vertex AI, or SageMaker. Data scientists keep their scikit-learn or PyTorch training, and agent builders keep their LangGraph loops. ZenML containerizes the code and records metrics, logs, and metadata for every run. Platform engineers define stacks: an orchestrator and an artifact store, plus optional extras such as a container registry, deployer, or experiment tracker. Moving from laptop to production then means switching stacks, not rewriting code. Anyone can open the dashboard and see each run as a DAG or a Gantt-style timeline, with step logs, runtime metrics, and artifact lineage. DataFrames open as interactive tables, images render in the browser, and Evidently, Great Expectations, and WhyLogs output gets its own views. MLflow, Weights & Biases, and Langfuse plug in instead of being replaced. Example projects include a deep research agent, RAG with evaluation loops, LLM fine-tuning, and a document-analysis service with a web UI. The MCP server lets Claude Desktop, Cursor, or any MCP client answer which runs failed this week and trigger deployments, while a VS Code and Cursor extension manages pipelines from the editor. Self-host the server as one container image serving the API and dashboard on port 8080. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Deploy