A founder I know sent me a screenshot last week. It was their "agent operations dashboard." It was a Notion page. The page contained five screenshots of five other dashboards, taken at different times that week, with handwritten arrows pointing at numbers nobody had figured out how to reconcile.
This was at a Series A company with thirty engineers.
I am not picking on them. I have seen the same Notion page at six different companies in the last month. The handwriting is different. The arrows point at different things. The screenshots come from different vendors. The pattern is identical.
We are at the part of the cycle where every company that shipped agents in 2025 is discovering that "shipping agents" and "running agents" are different problems. The first one is a demo. The second one is infrastructure. Nobody told them the second one was a thing.
So they buy it piecemeal. An observability tool because the engineers want traces. A cost tool because finance wants to know why the bill is what it is. A governance tool because legal walked into the standup and asked an uncomfortable question. A vector store for memory. A browser tool for web tasks because the agent kept getting stuck on cookie banners. Each tool costs money, each one needs an integration, and each one has its own dashboard.
You are now paying five vendors to half-answer one question. What is the agent doing.
The screenshots exist because the answer never lives in one place. The audit log is in vendor A, the cost line is in vendor B, the policy violation is in vendor C, the model choice is in vendor D, and the web action that caused all the trouble is in vendor E. When something breaks, somebody opens five tabs, takes five screenshots, and pastes them into Slack with an "umm." Then Slack becomes the actual postmortem system.
Slack is not a postmortem system.
Last quarter I started counting how many companies I talked to were in this exact state. I stopped at thirty. They all had the same conversation in roughly the same week. They all said "I think we need to consolidate," which is the polite phrase for "we built a thing we did not intend to build and now it is on fire."
What they did not intend to build was a runtime.
A runtime is the layer between the agent and everything else. It is the layer that knows what the agent did, what it saw, what it spent, what it was allowed to do, and what to do next time the same thing happens. A real runtime treats those as one question because they are one question. The arrival of agents did not change what infrastructure is. It just rearranged which seams break.
Every company assembling this from parts will converge on the same realization eventually. The five vendors do not federate. The traces do not cross-reference. The cost line cannot tell you which policy violation caused it. The policy violation cannot tell you which web action triggered it.You can paint over the seams with Notion pages forever. You will still be painting.
I find it useful to remember that the standard answer to "we built six things that should be one thing" is, historically, that one of them eats the other five. Sometimes the eating takes a year. Sometimes it takes a decade. The shape of the eater is roughly predictable in advance, which is why I keep writing about it.
You do not have an agent platform. You have a stack of receipts. The fact that nobody has built the runtime layer yet at your company does not mean the runtime layer does not exist. It means you are currently the runtime, and your title is "person who screenshots dashboards on Tuesday."
That is not a job. It is a tax.
The runtime is coming.