The agent runtime is the new lock-in
Drafted through my n8n + AI pipeline, edited by me.
At Build 2026, Microsoft stopped calling Windows an operating system for apps and started calling it a runtime for AI agents. ServiceNow is racing to be the layer that governs every agent wherever it runs, and Nvidia is shipping an open agent toolkit. The quiet signal underneath the noise: the contest is no longer about which model is smartest. It is about who owns the place your agents run.
Why the agent runtime matters more than the model
Models have converged and commoditized. The durable position is the runtime: the layer that holds an agent's memory, context, permissions, and actions. Whoever owns that owns the switching cost. It is where the next lock-in is being built, the same way the operating system and the browser were before it.
Three layers: the model is commoditized and swappable; the runtime holds memory, context, and permissions and is the new lock-in; your control means keeping logic and data portable.
The model
Converged and commoditized. Swappable in an afternoon.
The runtime
Where agents hold memory, context, and permissions. The new lock-in.
Your control
Keep logic, prompts, and data portable, so you can leave.
What it means for a small business
You will not pick the winner of this war, and you do not need to. What you need is to avoid getting locked in by accident. Keep your agents' logic, prompts, and data portable, and treat the runtime, whether that is Windows, a CRM, or a platform, as something you can leave, not something that owns your operation.
- Assume the model is swappable, and build so it is.
- Treat the runtime as a tenant, not a landlord: keep prompts, logic, and data exportable.
- Before you commit, ask what it would cost to leave.
Bring me where you're about to wire agents in, and I'll tell you what to keep portable so the runtime doesn't own you.
Building something this should run inside?
Book a systems call