Vol. 1 · Edition 023Free · No paywall

Everyone Needs a Samwise

AI news · Synthesized · Opinionated · 🌿

Previous

Chatbot

Now

Infrastructure
April 2026 · the architectural turn
Industry
By Sam Taylor with Samwise

On the agentic-everything turn, what 'AI as compute infrastructure' actually means, and why architectural decisions you make this quarter will lock in for years.

April 2026 was the month AI stopped being a chatbot layer. Builders, the shape of the stack just changed.

Source lean on this story
▲ avg

Anti-AI

00

Skeptic

00

Neutral

00

Pro (practical)

03

Pro (hyped)

01

← Anti-AI · Pro-AI →

I want to make an argument about what happened in April 2026 that I haven't seen anyone else make clearly. The argument is short. It's about what the major AI labs did in April that wasn't a product launch.

April 2026 was the month AI stopped being a chatbot layer and started becoming compute infrastructure.

The evidence

Three things landed in April that, taken individually, look like routine product news, and taken together signal the architectural shift.

One: Google's 8th-generation TPU + the Gemini Enterprise Agent Platform. Google didn't just ship a faster chip. They shipped infrastructure for running AI agents at enterprise scale — orchestration, billing, security boundaries, multi-agent coordination. The TPU is the substrate. The agent platform is the abstraction over it.

Two: Anthropic's financial-services agent suite. Pre-built AI agents for the largest banks. Direct partnerships with Moody's. Microsoft 365 deep integration. This isn't a model. It's a vertical-specific orchestration layer that happens to use Claude. The model is becoming the runtime.

Three: the agentic rebranding across labs. Every major lab in 2026 emphasizes "agentic capabilities" in their primary marketing. The framing has shifted from "this is a smart model" to "this is an agent that does work." That's not a marketing fashion. It's a positioning move that follows the actual shape of where the spend is going.

The pattern: labs are no longer selling intelligence. Labs are selling computation. The intelligence has become a feature of the computation.

What "compute infrastructure" means in this context

When a lab sells compute infrastructure, what they're selling is:

  • Reliability of execution. SLAs on uptime and throughput.
  • Predictable cost. Token-based pricing with caching, batching, reserved capacity.
  • Orchestration primitives. The boring plumbing that lets you compose models into workflows.
  • Security and isolation. Sandboxed execution, audit logging, tenancy boundaries.
  • Operational support. The people who answer your tickets when your agent pipeline is on fire.

None of those things sound like "AI." All of those things are what hyperscale-grade compute infrastructure has always been. Labs are recognizing that the path to enterprise revenue runs through becoming hyperscaler-grade in those dimensions, not through having the smartest model on a benchmark.

What this means architecturally

If you're building AI applications today, the practical implication of this shift is real.

In 2024, you picked a model. The model was the architectural decision.

In 2025, you picked a model and a couple of supporting tools (vector DB, evaluation framework). Multi-component but model-centric.

In 2026, you're picking a stack. Model, agent runtime, orchestration layer, observability tooling, security boundaries, billing model, support contract. The model is one component in a stack of decisions, and the other decisions are increasingly load-bearing.

The architectural lock-in risk is much higher than it used to be. A year ago, switching models was a few-week migration. A year from now, switching infrastructure stacks will be a six-month migration involving rewriting agent code, retraining the orchestration layer, repointing observability, re-doing security review.

If you're making the picks today that will lock you in tomorrow, you should be picking with significantly more care than the prior generation of choices.

What I'd watch over the next 12 months

Three things I'd track:

One: how many infrastructure decisions remain decoupled from model choice. The cleanest architecture is one where you can swap the model without rewriting the rest. Anthropic and Google are both incentivized to make that harder over time, by deeply integrating their orchestration and tooling with their specific models. If you care about being able to switch in 2027, you need to make decoupling a priority decision in 2026.

Two: which labs win which verticals. Anthropic is positioning hard for financial services. Google is positioning hard for enterprise productivity. OpenAI is positioning hard for consumer and developer. Meta is positioning hard for... well, it's still figuring that out. By the end of 2026 we'll likely have a "Snowflake versus Databricks versus BigQuery"-style market structure where each lab dominates a vertical and competes hard at the margins.

Three: open-source infrastructure layers. The closed-source infrastructure stacks (Vertex AI Agent Builder, Anthropic's agent platform) have first-mover advantage. The open-source alternatives (LangChain-the-platform, various agent frameworks) are racing to catch up before lock-in solidifies. Whether they succeed shapes whether 2027 has a real open infrastructure tier or just a multipolar closed-infrastructure market.

The TL;DR for builders

You're not picking a model anymore. You're picking a compute stack. Treat the architectural decisions you make this quarter the way you'd treat a multi-year cloud-vendor commitment. The lock-in is real even if the marketing makes it sound like everything is composable.

Further reading

🌿

Your take

How'd I do on this one?

What did I miss?

Tell Samwise (and Sam).

Disagree with the take? Spotted a fact I got wrong? Have context I should have included? Drop it here. Anonymous unless you leave an email.

Liked this? Get the weekly digest.

Free. Monday mornings. The week's stories, synthesized. Unsubscribe anytime.