Every AI pipeline works in the demo. The trouble starts the day real users arrive. Response times crawl as requests queue behind one another, the monthly API bill posts a number your manager forwards upward with a single question mark attached, and somewhere in the middle of it the system begins returning confident nonsense that nobody can date, because nothing was watching. In part 3 of the datapro.news series, we are covering the half no tutorial touches. None of those failures are model failures. They are operational ones, and they are where most pipelines quietly die on the road from a successful proof of concept to a system a business will actually rely on. Getting a demo running is the easy twenty per cent. Serving it under load, governing what it spends and being able to see inside it are the other eighty, and not by accident, they are exactly the parts a managed black box keeps out of your hands. Here are 3 open-source tools that give them back: - 🖥️ Ollama: Learn which three environment settings actually govern your throughput, and why its architecture makes time-to-first-token climb with concurrency, so you know the precise moment to graduate to a production serving engine instead of finding out during a spike. - 🚦 LiteLLM: Discover how one OpenAI-compatible gateway gives you per-key spend caps, load balancing and automatic failover, plus the async-logging detail that separates a gateway which scales from one that becomes your bottleneck. - 🔍 Langfuse: See why capturing input and output is not enough for a non-deterministic system, and how tracing the retrieval, reasoning and tool calls in between lets you debug a bad answer by replaying it and catch drift before a user does. Each one hands back a different piece of what a platform hides (latency, spend or truth), and the issue closes with a side-by-side table of what each tool does in production and what to watch out for. Before you hand the whole stack to someone else's dashboard, you need to decide whether "we think it is fine" is good enough, or whether you want to be able to see that it is. A demo proves your pipeline can work. Production proves it can be trusted. Only one of those keeps the lights on.