One episode after Zapier's CEO sat in the same chair, I asked @JanOberhauser the obvious question. He didn't take the bait, which was more interesting than a swipe would have been. Right tool for the right use case, and Wade's a great guy building a great product. Then he drew the line where he actually sees it, which is power and flexibility. Specifically, never feeling locked in. Look at what that means in practice. Code nodes for when the visual layer runs out. Agents where you define your own memory. Output parsers that force a guaranteed format. A different model per step. Fallback models. Human approval gates. Every one of those is a door for the moment the abstraction stops fitting your problem. That's the difference that never shows up in a comparison table. Simple workflows look the same everywhere. You find out which tool you picked the day you need something slightly unusual and there's either a door or there isn't. He's clear that you should start small and build up. The question is whether the thing lets you keep building once small stops being enough. Plus self-hosting, which decides it for a lot of companies before anyone compares a single feature.