About

MLOps Talks is a written-up index of the MLOps Community YouTube channel, now AAIF Live: six years of conference talks, podcast episodes, meetups and reading groups. Every session gets a page with a three-bullet TL;DR, a summary, the key ideas with links into the video at the second each one starts, the quotes worth quoting, and tags. On top of those sit packs: sessions in a deliberate order, with a line under each saying why it sits where it does. There are 927 talks written up so far.

The summaries are generated from the videos' own captions by a language model working under a fixed set of rules, then read by a person before publishing. The rules are strict about one thing above all: only claims the speaker actually makes. If you find a summary that puts words in a speaker's mouth, that is a bug and we want to hear about it.

Reading this with an agent

Every talk page and pack page has a plain Markdown version at the same address with .md on the end, for example /talks/no-vibes-allowed-solving-hard-problems-in-complex-codebases.md. The same URLs also answer an Accept: text/markdown request with Markdown, which is what Claude Code and similar tools send. The Markdown version carries the same content without the layout. There is also /llms.txt and an RSS feed. If you would rather ask your own assistant, there is an MCP server it can search the site through.

Who makes it

The ZenML team. ZenML is an open-source framework for running ML and AI workflows as pipelines, which is the problem many of these sessions describe from the inside. On some of those sessions you will see a labelled Editor's note. It sits separate from the summary and is never in the speaker's voice.

MLOps Talks has a sister site, AIE Talks, which does the same for the AI Engineer conference channel. The two share one pipeline and one codebase; only the channel, the design and the sponsor differ.

What we log

Page views are counted with Plausible, which sets no cookies and stores no personal data, so there is no consent banner.

What you type into the "What are you building?" box is kept for three months, so we can see which questions have no good answer yet and write the pack that answers them. It is not tied to you.

Calls to the MCP server are kept the same way and for the same three months: which tool was called, what was asked, what came back. They are not tied to you.