Maturity Matrix
Matrix/Infrastructure

Infrastructure

The technical layer that enables (or blocks) agents. From shared Jenkins to ephemeral agent sandboxes.

4capabilities20levels61practices61guides
The matrix · full map
Capability ↓
Maturity →
L1 · Stage 01
Ad-hoc
L2 · Stage 02
Guided
L3 · Stage 03
Systematic
L4 · Stage 04
Optimized
Sweet spot
L5 · Stage 05
Autonomous
01·15 guides
Agent Runtime & Sandboxing
Where and how AI agents execute code - isolation, security, and resource management
Agents run on developer laptops
3 practices·3 guides
Docker walls and scoped credentials
3 practices·3 guides
Isolated devboxes, blind to production
3 practices·3 guides
Hardware-isolated microVMs in ten seconds
3 practices·3 guides
A fleet on its own compute
3 practices·3 guides
02·15 guides
MCP & Tool Integration
How agents connect to external tools, APIs, and internal systems via MCP (now universal standard) and plugins
Built-in tools and copy-paste
3 practices·3 guides
A few MCP servers, wired by hand
3 practices·3 guides
MCP is a managed platform
3 practices·3 guides
Four hundred tools behind one door
3 practices·3 guides
MCP is the nervous system
3 practices·3 guides
03·15 guides
Build System
Build tooling optimized for agent-scale throughput - caching, incrementality, and speed
Full rebuilds in a shared queue
3 practices·3 guides
Cached and parallel - that's it
3 practices·3 guides
Bazel, remote, incremental
3 practices·3 guides
Any change, under two minutes, per agent
3 practices·3 guides
Builds too fast to notice
3 practices·3 guides
04·16 guides
Observability & Feedback Loop
Monitoring agent behavior, costs, and outcomes to close the improvement loop
Logs and error alerts
3 practices·3 guides
Structured logs, basic OpenTelemetry
3 practices·3 guides
Agent cost and outcomes on dashboards
3 practices·3 guides
Anomalies open tickets; agents investigate
4 practices·4 guides
Production fixes itself through the loop
3 practices·3 guides
Climb the matrix

You don't have to figure this out alone.

Every level in this matrix has a path. Read the playbooks the teams that have climbed it wrote. Run the assessment with our consultants. Start where you are.

Live with Visdom

Book an AI Maturity Assessment session with your team.

We walk you through all four perspectives, score where you actually are, and leave you with a 90-day plan to climb in the dimensions that matter most.

Book an assessment See what's included90-day plan - scored assessment - coaching
Author Commentary

July 2026 update: infrastructure became the answer to a question May made urgent - how do you depend on AI without being owned by it.

The runtime moved off the shared cloud and onto hardware-isolated, often self-hosted ground. AWS launched Lambda MicroVMs (June 22, Firecracker, built explicitly for AI-generated code, up to 8h runtime), AWS/Google/Azure all moved agent execution to hardware-enforced isolation, and self-hosted E2B/Daytona now keep the agent's code inside the customer VPC for data residency. "Enterprise AI agents are leaving the server" stopped being a slogan. The sovereign endpoint of that path is a full local stack: open-weight models (GLM-5.2, Kimi K2.7-Code, DeepSeek V4) running on your own hardware via llama.cpp/vLLM - the same capability, none of the vendor lock-in that disabled Fable 5 worldwide in 72 hours.

The supply chain hardened to match. PolicyLayer's State of MCP scanned 2,031 servers and found 42% expose a destructive tool while 96.1% never warn the agent; "Agentjacking" showed a malicious tool or error response treated as trusted remediation. Mitigations went mainstream - MCP Tool Search and lazy tool-loading cut both token overhead (~90% through gateways) and the live attack surface, and Dapr 1.18 Verifiable Execution (June 11) added cryptographic, tamper-evident provenance to every agent run. On the cost side the market turned from tokenmaxxing to efficiency: local token-compression proxies (prompts never leave the machine) report 60-95% savings, and Anthropic and OpenAI shipped enterprise usage analytics and spend controls. Infrastructure, not the model, still decides whether your fleet scales gracefully or burns the budget on a Tuesday night - and now it also decides whether you still have a fleet when your vendor goes dark.

Other perspectives