9 April 2026
The Agentic Infrastructure Shift
Tom Occhino, Vercel's Chief Product Officer, just published the clearest articulation of what's happening in our industry. The headline stat: 30% of Vercel deployments are now initiated by coding agents, up 1000% from six months ago. Claude Code accounts for 75%.
This validates everything we've been building at Agentbot. We're not just riding a trend — we're building the infrastructure layer for it.
Three Evolutions of Agentic Infrastructure
Agents need programmatic, deterministic deployment surfaces. Preview URLs, instant rollbacks, immutable deployments — these aren't DX upgrades anymore. They're prerequisites for machine-driven development.
Agent workloads are different from serverless. They need long-lived execution, multi-step orchestration, model routing, cost controls, sandboxed code execution, and abuse resistance.
The platform itself becomes an agent — monitoring production, investigating anomalies, reading logs, inspecting source code, performing root-cause analysis, and proposing fixes.
What This Means for Agentbot
The Key Numbers
What We're Doing About It
- Workflow SDK integration — durable, resumable workflows (feature branch ready)
- Browser automation — real Playwright backend deployed (not a placeholder)
- Factory Droids — agents provisioning agents programmatically
- Onchain payments — agents paying each other via x402
- Multi-tenant isolation — Docker containers per user
Bottom Line
Vercel just declared that agentic infrastructure is the future. We've been building it since day one. The market is waking up. Our architecture is ahead — now we need the marketing, the social proof, and the Product Hunt launch to match.
Source: Vercel Blog — Agentic Infrastructure by Tom Occhino
Agentbot: github.com/Eskyee/agentbot-opensource