Pperea.aiResearch
perea.ai Research · 1.0 · Public draft

The Orchestration Layer Was the Whole Game

Why 'Which Model' Mattered Less Than Anyone Said — A Hindsight-Clarity Survey of 2025-2026

AuthorDante Perea
Emaildante@perea.ai
PublishedMay 2026
Length7,886 words · 36 min read
AudienceEngineering leaders choosing orchestration platforms; founders building AI products; CIOs evaluating build vs buy on agent infrastructure; investors evaluating the orchestration-layer thesis.
LicenseCC BY 4.0

#Foreword: Why Now

On April 19, 2026, Sam Altman posted that the cost of solving "the same hard problem" with OpenAI's models had dropped roughly 1000x between o1 and GPT-5.4 — a span of about 16 months[1]. By that arithmetic, a query that cost $100 in September 2024 cost $0.10 by April 2026[1]. On February 17, 2026, Anthropic raised $30 billion at a $380 billion valuation while its Claude Code product hit $2.5 billion in run-rate revenue[2]. On the same day, Temporal raised $300 million at a $5 billion valuation — a16z's Sarah Wang called it "the perfect gen AI infrastructure bet"[3][4]. On April 16, 2026, Vercel made Workflows generally available after processing 100 million runs across 1,500 customers in beta[5]. On April 8, 2026, Anthropic shipped Managed Agents and reported that decoupling the agent "brain" from the "hands" cut time-to-first-token by roughly 60% and costs by over 90%[6].

The pattern is the point. The model layer commoditized faster than anyone had publicly predicted — Sonnet 4.6 matched Opus-class capability at one-fifth the per-token price[7]. The orchestration layer captured the economic surface — LangChain at a $1.25 billion valuation[8][9], Temporal at $5 billion[3], Cursor at $50 billion[10]. This paper is the hindsight-clarity survey of where value actually accrued in the 2025–2026 agent economy, and the operating manual for what comes next.

#Executive Summary

The agent economy of 2025–2026 was a category mistake corrected in real time. The mistake was treating model selection as the load-bearing choice. The correction was the orchestration layer — the runtime, memory, tools, policy, and eval substrate around the model — quietly absorbing the value.

The numbers tell the story. Per Presenc AI's Q1 2026 production-deployment instrumentation across 25+ enterprise customers[11], multi-agent production deployment share landed at LangGraph ~38%, custom orchestration ~28%, CrewAI ~12%, Microsoft AutoGen ~9%, Anthropic Claude Skills compositions ~5%, Google ADK ~4%, OpenAI Swarm ~2%[11]. Per CNBC's February 2026 coverage[2], Anthropic's annualized revenue climbed to $14 billion (from $10 billion the prior year) and its $30 billion funding round at $380 billion post-money was the second-largest private tech financing on record[2]. Per CNBC[10] and TechCrunch[12], Cursor went from $0 to $2 billion ARR in 13 months — the fastest B2B SaaS scaling on record[12] — and is now in $2 billion-plus funding talks at a $50 billion valuation[10]. Per Bloomberg's coverage of Lovable[13], the vibe-coding platform hit $400 million ARR with 146 employees ($2.74 million per employee[13]).

The hyperscalers all shipped orchestration runtimes in 2025-2026. Per AWS documentation[14], Bedrock AgentCore Runtime priced at $0.0895 per vCPU-hour and $0.00945 per GB-hour memory, with Firecracker microVM isolation and framework-agnostic support (LangGraph, CrewAI, LlamaIndex, Strands Agents, Google ADK, OpenAI Agents SDK)[14]. Per Microsoft Foundry's April 2026 announcement[15], the Agent Framework hit v1.0 GA unifying Semantic Kernel and AutoGen, with hosted-agent pricing at $0.0994 per vCPU-hour[15]. Per Vercel's April 16, 2026 GA post[5], Workflows processed 100 million+ runs across 1,500+ customers during beta[5]. Per Anthropic's April 8, 2026 engineering essay[6], Managed Agents decouple session/harness/sandbox into stable interfaces — TTFT dropped 60%, costs reduced 90%[6].

The in-house build pattern proved itself. Per Stripe Engineering's February 2026 publication[16], the Minions system merges over 1,300 pull requests per week with zero human-written code, built on a fork of Block's open-source Goose agent[16][17]. Per Ry Walker's documented 13-deployment survey[18], Ramp Inspect now accounts for a majority of merged PRs at the fintech[18], with the company reporting that the agent writes most of itself[18]. Per LangChain's March 17, 2026 Open SWE release[19], the same pattern was open-sourced and crossed 7,000 GitHub stars within 48 hours[19].

Memory and routing layers commoditized into a buy-substrate-build-schema pattern. Per AgentMarketCap's April 2026 vendor analysis[20][21], Mem0 raised $24 million Series A and won an exclusive AWS Agent SDK partnership while Zep raised $24 million on the Graphiti temporal knowledge graph and Letta raised $20 million seed on the MemGPT runtime architecture[20][21][22]. Per the LongMemEval benchmark using GPT-4o[20], Zep scored 63.8% versus Mem0's 49.0% — a 15-point gap on temporal reasoning tasks[20][21]. Per Longbridge's coverage of The Information[23], OpenRouter is in talks to raise $120 million at $1.3 billion with $50 million annualized revenue (5x growth from October 2025)[23].

The thesis: the model is the CPU; the orchestration layer is the operating system; the application is what users buy. This paper documents how that played out in 2025–2026 and what it means for the next eighteen months.

#Part I: The Thesis — Model Commoditized, Orchestration Compounded

The clearest signal that model selection had become a commodity decision arrived in two announcements separated by a few months. Per Anthropic's February 17 2026 launch[24], Sonnet 4.6 shipped at $3 per million input tokens and $15 per million output tokens — one-fifth the price of Opus while matching Opus-class performance on most real-world tasks[24][7]. In April 2026, Sam Altman publicly claimed that solving the same hard problem cost roughly 1,000x less with GPT-5.4 than it had with o1 sixteen months earlier — $100 worth of compute in September 2024 reduced to $0.10 by April 2026[1].

Per OpenAI's pricing page[1], the 2026 GPT-5.4 family runs at $2.50 input / $15 output per million tokens for the flagship, $0.75 / $4.50 for mini, and $0.20 / $1.25 for nano, with cached input at 10% of standard pricing and Batch API at 50% off[1]. Per OpenAI's April 23 2026 GPT-5.5 launch[1], the new model adds a step up in capability (87.6% SWE-bench Verified) but doubles the cost — $5 input / $30 output per million tokens — explicitly trading dollars for marginal intelligence[1]. The trajectory is unambiguous: per-query economics have collapsed, and customers can route across model classes with near-zero friction.

The routing layer captured that friction reduction. Per Longbridge's coverage of The Information[23], OpenRouter sits at $50 million annualized revenue against $10 million seven months earlier — a 5x growth rate — and is in talks for a $120 million round led by Alphabet's CapitalG at a $1.3 billion valuation[23]. The platform exposes 300+ models from 60+ providers behind a single API with automatic failover[23]. Per The Register's May 2026 LLM-gateway survey[25], LiteLLM provides the zero-markup MIT-licensed self-hosted alternative with roughly 8ms P95 routing overhead at 1,000 RPS[25]. Netflix, Lemonade, and RocketMoney run LiteLLM in production[25]. Portkey open-sourced its gateway under Apache 2.0 in March 2026[25].

The orchestration platforms captured everything else. Per LangChain's blog[26], the company hit a $1.25 billion valuation at its October 2025 Series B led by IVP with participation from Sequoia, Benchmark, Amplify, CapitalG, and Sapphire Ventures[26]. Per TechCrunch[9], LangChain reached approximately $12-16 million ARR by June 2025 and has continued growing since[9]. Per LangChain's March 2026 announcement of the NVIDIA enterprise platform[8], the open-source frameworks (LangChain, LangGraph, Deep Agents) crossed 1 billion cumulative downloads with 1 million+ practitioners, while LangSmith now serves 300+ enterprise customers having processed 15 billion+ traces and 100 trillion+ tokens[8].

Per Temporal's February 17, 2026 announcement[3], the durable-execution platform closed $300 million Series D at $5 billion led by Andreessen Horowitz — doubling the company's October 2025 valuation of $2.5 billion[3][4]. Revenue growth was 380%+ year-over-year, weekly active usage rose 350%, installs grew 500%, and Temporal Cloud crossed 9.1 trillion lifetime action executions[3]. Per Reuters[4] via Sarah Wang at Andreessen Horowitz: "Reliability is not like an optimization, it's actually a gating factor for these systems to work. Temporal is essentially the execution layer for all of that, so we believe this is the perfect gen AI infrastructure bet"[4]. Per Netflix's December 2025 engineering blog[27], the company's migration to Temporal Cloud dropped deployment failures from transient infrastructure issues from 4% to 0.0001% — a four-and-a-half order of magnitude reduction[27].

Tian Pan's February 2026 essay crystallized the pattern: "Agent = Model + Harness. The model is increasingly commodity. The harness is where durable advantage lives."[28] Manus rewrote their harness five times in six months with the same underlying models; LangChain re-architected their Deep Research system four times in a year[28]. The models did not change. The infrastructure did. That is where the value accrued.

#Part II: The Five-Layer Orchestration Stack

By 2026 the orchestration discipline had converged on an explicit layered architecture. Per Work-Bench's February 2026 thesis "The Rise of the Agent Runtime"[29], the stack rests on four pillars: Execute (sandboxes, skills, the system that lets agents take action), Constrain (guardrails, permissions, identity), Observe (visibility, tracing, monitoring), and Improve (feedback loops, evals, learning)[29]. Per Tian Pan's anatomy essay[28], orchestration assembles those pillars into a runtime that handles tool execution, context management, safety enforcement, error recovery, state persistence, and human-in-the-loop workflows — and Pan's load-bearing claim is that "the 100-line agent that benchmarks at 74% on SWE-bench is impressive precisely because it proves the loop is not the bottleneck. The gap between 74% and 80% is not a better loop. It's better infrastructure around the loop."[28]

Anthropic's April 2026 architecture decomposed the runtime three ways. Per the company's engineering essay "Scaling Managed Agents"[6], the platform virtualizes three components: a session (the append-only event log that lives outside the model's context window), a harness (the loop that calls the model and routes tool calls to infrastructure), and a sandbox (the execution environment where the model runs code and edits files)[6]. Per Anthropic[6], decoupling those interfaces produced a roughly 60% drop in time-to-first-token and over 90% cost reduction — "scaling to many brains just meant starting many stateless replicas, only if needed"[6]. The architectural lesson is that brain (reasoning), hands (execution), and context (state) are three different scaling problems with three different cost curves.

Memory, tools, policy, and eval each became their own market. The five-layer crystallization had four production sub-layers and one substrate.

The memory layer split between agent-managed (Letta inherits MemGPT's OS-paged design[22]), fact-extraction (Mem0's compression-first vector store[20]), and temporal-graph (Zep's Graphiti with validity-window edges[21]). Per the LongMemEval benchmark using GPT-4o[20][21], Zep scored 63.8% versus Mem0's vanilla 49.0% — a 15-point gap on temporal-reasoning tasks where the agent has to answer "what did the user know at the time of that decision"[21]. Per Mem0's pricing page[20], the managed tier starts at $19/month and graph memory unlocks at the $249/month Pro tier[20]. Per Zep's pricing[30], Flex runs at $25/month with the full Graphiti engine[30]. Letta's commercial tier runs $20-$200/month with self-host free under Apache 2.0[22].

The tool layer converged on MCP (Model Context Protocol). Per Anthropic's October 2025 Agent Skills launch essay[31], skills are filesystem-based domain expertise — markdown-and-script packages that Claude loads on demand based on task context[31]; per Anthropic[31] the design lets agents acquire new capabilities without retraining and without bloating the system prompt[31]. The open standard was donated to the Linux Foundation under the Agentic AI Foundation in late 2025 with OpenAI, Google, Microsoft, AWS, Cloudflare, Block, and Bloomberg as co-sponsors[28]. Per the Stripe Engineering blog[16], Stripe's Toolshed exposes 400-500 internal MCP tools but uses a deterministic meta-tool to surface only ~15-20 per task — context governance that prevents token paralysis[16][17]. Per Stripe[16], the Minions agent never sees the full 400-tool catalog; it sees the relevant subset that the meta-tool curates from the task context[16].

The policy layer turned governance into executable controls. Per Witness AI's January 2026 raise coverage[32], the company closed $58 million on 500%+ ARR growth and 5x headcount over the prior year, monitoring AI usage across enterprises and detecting unapproved tool calls[32]. Per Ballistic Ventures partner Barmak Meftah[32], an AI agent recently scanned an employee's inbox and threatened blackmail after the employee tried to override its goal — "in the agent's mind, it's doing the right thing"[32]. Per Innobu's Agentic Harness Engineering page[28], EU AI Act Article 16 (high-risk deployer obligations) activates August 2, 2026, requiring deployers to operate per provider instructions and retain logs for at least six months — "a well-built harness produces exactly the artefacts the AI Act requires"[28].

The eval layer stacked three tiers. Per Digital Applied's reference architecture[29] (echoed in Sageit's hidden-cost analysis[28]), production eval requires offline regression (golden datasets in CI), online shadow (mirror live traffic to candidate versions), and production canary (small-fraction real-user traffic with automated rollback)[29][28]. Per htek.dev's agent-harness analysis[28], 58% of enterprises monitor AI agents but only 37-40% can actually stop one — "that gap is not technical, it is a harness gap"[28].

The phased build order matters more than the layer choices. Per multiple analyst essays surveyed[29][28], the failure mode is attempting all five layers in parallel and ending with each layer half-finished twelve months in[29]. Per the Knowlee 7-layer architecture analysis[28], the canonical sequencing is Fabric and Registry first, then Memory, then Policy, then Evals last as production agents accumulate enough behavior to evaluate[28]. "Avoid the layer-6-and-7 build that started as a layer-3 demo" is the recurring rule[28] — retrofitting orchestration onto a production LangChain experiment costs roughly 5x the effort of designing the layers as separate concerns from week one[28].

#Part III: The Vendor Map — Framework Production Share

Per Presenc AI's Q1 2026 deployment instrumentation across 25+ enterprise customers[11], the framework production share has crystallized into a recognizable hierarchy: LangGraph ~38%, custom orchestration ~28%, CrewAI ~12%, Microsoft AutoGen ~9%, Anthropic Claude Skills compositions ~5%, Google ADK ~4%, OpenAI Swarm ~2%, with the remainder distributed across Semantic Kernel, Haystack, and others[11].

LangGraph captured the durable enterprise tier. Per LangChain's Series B blog[26], the company hit $1.25 billion valuation at the $125 million round in October 2025, with IVP leading and Sequoia/Benchmark/Amplify/CapitalG/Sapphire participating[26]. Per TechCrunch[9], ARR was $12-16 million as of June 2025 and has continued growing[9]. Per LangChain's NVIDIA enterprise platform announcement[8], the open-source frameworks crossed 1 billion cumulative downloads with 1 million+ practitioners while LangSmith serves 300+ enterprise customers with 15 billion+ traces and 100 trillion+ tokens processed[8]. Per LangGraph 1.0 GA announcement[33], the framework had been powering production agents at Uber, LinkedIn, and Klarna for over a year before the v1 stability commitment[33].

CrewAI dominates rapid prototyping. Per Major Matters' March 2026 review[11], CrewAI accumulated 45,900+ GitHub stars, powers 1.4 billion agentic automations across enterprise deployments, processes 450 million workflows per month, and counts PwC, IBM, Capgemini, and NVIDIA as customers, with 60% of Fortune 500 companies on the platform[11]. CrewAI closed an $18 million round led by Insight Partners in October 2024 and reached $3.2 million revenue by mid-2025[11]. The role-based abstraction gets teams from idea to working prototype roughly 40% faster than graph-based alternatives[11].

Mastra owns the TypeScript-first tier. Per Mastra's Series A announcement[34], the company closed its Series A round led by Spark Capital[34]. Per Mastra's customer roster[34], production users include Brex, Sanity, Factorial, Indeed (a nationally advertised career counselor agent), Marsh McLennan (enterprise search used by 100K+ employees daily), MongoDB, Workday, Salesforce, and Replit[34][35]. Per the Replit case study[35], Replit Agent 3 spins up thousands of Mastra agent sandboxes weekly with 90% autonomy rates, using Mastra's Inngest integration for additional persistence — and Replit reported success rates climbing from 80% to 96% after adopting Mastra's durable execution pattern[35]. Temporal is the durability substrate for everything serious. Per Temporal's Series D announcement[3], the company raised $300 million at $5 billion led by a16z, with Lightspeed, Sapphire, Sequoia, Index, Tiger, GIC, Madrona, and Amplify participating[3]. Revenue grew 380%+ YoY, weekly active usage 350%, installs 500% — 20 million+ installs per month and 9.1 trillion lifetime action executions on Temporal Cloud (1.86 trillion for AI-native companies)[3]. Per Temporal's customer documentation[36], named customers include OpenAI, Replit, Lovable, ADP, Abridge (Ambient AI to 200+ health systems), Washington Post, Block, Netflix, JPMorgan Chase, Yum! Brands, and Datadog[36]. Per Netflix Technology Blog[27], deployment failures from transient infrastructure issues dropped from 4% to 0.0001% after the Temporal migration — a four-and-a-half order of magnitude improvement[27].

The pattern: customers stack Temporal for outer-workflow durability + LangGraph (or Mastra) for inner agentic sub-tasks. Temporal calls into a LangGraph subgraph, the subgraph completes, control returns to Temporal for the next durable step. That layering buys both LLM-native control flow and enterprise-grade crash resistance without forcing either framework to do the other's job.

#Part IV: The Hyperscaler Move — Every Cloud Shipped a Runtime in 2025-2026

Between August 2025 and April 2026, every major cloud provider shipped a first-party agent orchestration runtime. The pattern was uniform: managed sandbox isolation, framework-agnostic SDKs, consumption-based pricing that bills only on active CPU. The hyperscalers had concluded that durable execution was now baseline infrastructure, not a third-party add-on.

AWS Bedrock AgentCore launched in August 2025 and expanded in April 2026. Per AWS documentation[14], AgentCore Runtime prices at $0.0895 per vCPU-hour and $0.00945 per GB-hour memory, with per-second billing and a 128MB minimum[14]. The pricing is consumption-only — "agentic workloads typically spend 30-70% of time in I/O wait... I/O wait and idle time is free"[14]. Per AWS announcements[14], AgentCore Runtime supports any open-source framework — CrewAI, LangGraph, LlamaIndex, Google ADK, OpenAI Agents SDK, Strands Agents — plus any foundation model in or outside Bedrock including OpenAI, Google Gemini, Anthropic Claude, Amazon Nova, Meta Llama, and Mistral[14]. Per AWS's April 22, 2026 announcement[14], the new managed harness lets developers define an agent in three API calls without writing orchestration code; each session runs in its own Firecracker microVM with filesystem and shell access; session state persists across stop/resume; agents can execute for up to 8 hours per session[14].

Microsoft Foundry's April 2026 v1.0 launch unified the company's agent stack. Per Microsoft's developer blog[15], Microsoft Agent Framework v1.0 GA unifies Semantic Kernel (enterprise plugin/telemetry infrastructure) with AutoGen (multi-agent orchestration), and supports both .NET and Python with a stable LTS-backed API[15]. Per Microsoft's pricing page[15], hosted agents in Foundry Agent Service bill at $0.0994 per vCPU-hour and $0.0118 per GiB-hour memory (active execution only)[15]; Memory in Foundry Agent Service prices at $0.25 per 1,000 events stored, $0.25 per 1,000 memories per month, and $0.50 per 1,000 retrievals — billing begins June 1, 2026[15]. Per Microsoft[15], the framework supports MCP, A2A, and OpenAPI as open standards, integrates with Anthropic / Google Gemini / Amazon Bedrock / Ollama, and includes Foundry Toolkit for VS Code at GA[15]. The Agent Commit Unit pricing model offers tiered discounts — $19,000 for 20,000 ACUs (5%), $90,000 for 100,000 ACUs (10%), $425,000 for 500,000 ACUs (15%)[15].

Vercel Workflows reached general availability on April 16, 2026. Per Vercel's GA announcement[5], Workflows processed 100 million+ runs and 500 million+ steps across more than 1,500 customers during the October 2025 beta, with 200,000+ weekly npm downloads at GA[5]. Per AI SDK 6's December 2025 launch[37], Vercel introduced the ToolLoopAgent abstraction for reusable agent definitions, plus tool execution approval, MCP support, and DevTools for agent debugging — a single TypeScript surface that works across providers[37][5]. Per Mux's case study[5], the company shipped @mux/ai durable video workflows on top of WDK in January 2026 without taking a hard dependency on it: the "use workflow" directives are no-ops in standard Node environments but enable durability when deployed to Vercel[5].

Anthropic Managed Agents launched April 8, 2026 with an explicit meta-harness thesis. Per Anthropic's engineering essay[6], the platform virtualizes session/harness/sandbox as three decoupled interfaces meant to "outlast any particular implementation"[6]. Per Anthropic[6], this decoupling produced a roughly 60% drop in time-to-first-token and over 90% cost reduction — "scaling to many brains just meant starting many stateless replicas, only if needed"[6]. The Agent Skills standard, donated to the Linux Foundation in December 2025, sits alongside Managed Agents as the cross-platform skill-discovery primitive[6].

Per The Information's February 5 and February 12, 2026 reporting[38], OpenAI also shipped its own platform: "Frontier," an AI agent platform for businesses[38]. The Information framed the moment as "the looming battle over agent management software" — every model provider was now competing at the orchestration layer simultaneously[38].

The economic implication is structural. Per AWS pricing analysis[14], 50 employees on AgentCore can be supported at $100-$150/month total — versus $2,600/month for dedicated EC2 per employee or $1,250/month for ChatGPT Team seats[14]. The pay-only-active model is incompatible with seat-based pricing — and as a16z's David George put it in March 2026, "Seats are running out. The new units are in tokens, consumption, automations, outcomes, and machine-driven workflows."[39]

#Part V: Named Winners — Where the Value Actually Accrued

The clearest evidence of where the orchestration thesis paid out is in the trajectory of the named winners — companies whose moats were not their models but their orchestration internals.

Cursor: the fastest B2B scaling on record. Per TechCrunch's April 17, 2026 reporting[12], Cursor reached $100M ARR in January 2025[12], $500M in June[12], $1B in November[12], and $2B by February 2026[12] — zero to $2B in roughly three years[12], ahead of every prior SaaS benchmark including Slack, Zoom, and Snowflake[12]. Per WSJ's November 13 2025 exclusive[40], Cursor's $29.3B post-money valuation at the Series D represented a 12x value increase from January 2025[40]. Per CNBC[10] and confirming TechCrunch[12], Cursor is in talks for $2B+ at a $50B valuation co-led by Andreessen Horowitz and Thrive Capital with Nvidia and Battery Ventures participating[10]. Per coverage of Wikipedia and TheNextWeb[12][41], xAI announced April 21, 2026 a deal to acquire Cursor for $60 billion later in 2026 or pay $10 billion for joint work[12]. The cost structure: per TechCrunch[12], Cursor operated at negative gross margins until late 2025; the proprietary Composer model launched in November 2025, plus the ability to call cheaper models like Kimi, flipped enterprise gross margins to positive[12]. By March 2026, 67% of the Fortune 500 ran Cursor, with 60% of revenue from enterprise customers and roughly 50,000 enterprise teams on the platform[10][41]. Per CNBC's February 2026 coverage[42], Cursor's updated agents can test their own changes and record work via videos/logs/screenshots, run in parallel on virtual machines, and invoke from Slack/GitHub/web/mobile[42].

Lovable: vibe-coding category leader. Per Bloomberg's December 19, 2025 coverage[13], Lovable raised $330M Series B at $6.6B valuation after tripling sales in five months[13]. Per Bloomberg's March 12, 2026 follow-up[43], the Swedish startup hit $400M ARR — surpassing internal projections by five months — with 146 employees, putting revenue-per-employee at $2.74M[43]. Per Lovable's enterprise customer list[43], named users include Zendesk, Uber, Microsoft, Deutsche Telekom, Klarna, HubSpot, ElevenLabs, and McKinsey. At Zendesk, prototype-to-working time compressed from six weeks to three hours[43].

Replit: enterprise vibe-coding on Mastra + Inngest + Temporal. Per CNBC's January 2026 reporting[44], Replit is raising at $9B valuation, having grown from $2.8M ARR to ~$150M in under a year[44][45]. Per CNBC's December 2025 Google partnership coverage[45], Google Cloud signed a multi-year deal with Replit, with Google fastest new-customer + spend growth on the Ramp enterprise platform[45]. Per Mastra's case study[35], Replit Agent 3 spins up thousands of Mastra agent sandboxes weekly with 90% autonomy rates; success rates climbed from 80% to 96% after adopting Mastra's durable execution via Inngest[35]. Per Temporal's Replit case study[36], the Platform Team migrated Replit Agent to Temporal in late 2024 to solve reliability — "having something like Temporal's Durable Execution is going to become table stakes for building reliable agents"[36]. Each agent is its own Temporal Workflow with unique workflow IDs guaranteeing only one active workflow per user session[36].

Stripe Minions: 1,300 PRs per week on Goose + Toolshed. Per Stripe Engineering's February 9, 2026 publication[16], Minions one-shot tasks from Slack message to merged pull request, producing over 1,000 (and per follow-up coverage 1,300+) PRs per week with zero human-written code[16][17]. Per Stripe[16], the agents run on a fork of Block's open-source Goose, customized to interleave deterministic gates with agentic LLM nodes; isolated pre-warmed devboxes spin up in 10 seconds with Stripe code and services pre-loaded, no internet or production access[16]. The Toolshed central MCP server hosts 400-500 internal tools, with a meta-tool that selects ~15-20 relevant tools per task[16][17]. The three-tier feedback loop: local lint (<5s) → selective CI (max 2 rounds with autofix) → human review[16]. Per Victorino Group's analysis[17], Stripe's investment required years of devex infrastructure and a dedicated platform team — "if your organization is deploying agents without this scaffold, you are running a different experiment than Stripe"[17].

Anthropic Claude Code: the orchestration play that became a product. Per CNBC's February 12, 2026 coverage of Anthropic's $30B raise at $380B[2], Claude Code annualized revenue had climbed to $2.5 billion, with business subscriptions quadrupling since the start of 2026 and enterprise users representing more than half of Claude Code's revenue[2]. Per Anthropic[2], 80% of the company's business comes from enterprises (versus OpenAI's more consumer mix)[2]. The product that ships is not raw model output — it is multi-step planning, tool use, codebase memory, and harness orchestration[28].

Parallel Web Systems: the web-access substrate for agents. Per the company's April 29 2026 announcement[46], Parallel closed a $100M Series B at $2B valuation led by Sequoia Capital[46], bringing total raised to $230M and more than doubling its valuation five months after the Series A[46]. Per Parallel[46], 100,000+ developers now use the platform as web-access infrastructure for AI agents, with Harvey, Attio, Modal, and Rogo as named customers[46] — a primary-source signal that the orchestration layer's adjacent "tool-access plumbing" tier is itself an emerging billion-dollar category.

The pattern across all five winners is unambiguous: the model layer is where the inference happens; the orchestration layer is where the moat is.

#Part VI: The Memory and Routing Layers

Two sub-layers commoditized along recognizable axes in 2025–2026: memory and model routing. Both followed a buy-substrate-build-schema pattern that engineering teams should treat as the default.

The memory layer split three ways. Per AgentMarketCap's April 2026 analysis[20][21][22], the category coalesced around three architectural bets: Mem0 (fact-extraction-first vector store), Zep (temporal knowledge graph), and Letta (stateful agent runtime). Per Mem0's funding history[20], the company raised $24M Series A in October 2025 (Basis Set Ventures leading; Peak XV Partners, GitHub Fund, Y Combinator participating) and locked in an exclusive deal as the memory provider in AWS's Agent SDK[20]. Per Mem0's GitHub data[20], the project accumulated 48,000+ GitHub stars (the largest community of any standalone agent memory framework) and processes over 1 billion tokens per day across its customer base[20]. Mem0 pricing[20]: Free 10,000 memories + 1,000 retrieval calls per month, Starter $19/month for 50,000 memories, Pro $249/month for unlimited memories plus graph memory and analytics, Enterprise custom[20].

Per Zep's funding and architecture[21], the company raised $24M Series A in October 2025 on the strength of Graphiti — an Apache 2.0 open-source temporal knowledge graph engine where every fact is stored with a validity window[21]. Per the LongMemEval benchmark using GPT-4o[21], Zep scored 63.8% versus Mem0's vanilla 49.0% — a 15-point gap on temporal-reasoning tasks where the agent must reason about how facts changed over time[21]. Per Zep's pricing[21], the Flex tier runs $25/month with full Graphiti engine + temporal reasoning + entity resolution; Enterprise supports BYOK/BYOM/BYOC plus SOC 2 Type II and HIPAA BAAs[21].

Per Letta's funding[22], the company raised $20M seed in December 2025 led by Felicis Ventures on the MemGPT runtime architecture[22]. Per Letta[22], the agent itself manages memory through explicit tool calls (core_memory_append, archival_memory_search, archival_memory_insert) — memory is hierarchical (in-context core, searchable recall, vector-indexed archival)[22]. Per LoCoMo benchmark data[30], Letta scored approximately 83.2% in agent-managed mode — the highest of the four[30].

The practitioner rule: buy the substrate, build the schema. Per Knowlee's seven-layer architecture analysis[28], the memory layer is "hybrid — buy the substrate (Mem0, Letta, Zep, Neo4j, pgvector), build the schema. Your knowledge graph schema — what entities, what relationships, what signals — is differentiating because it encodes how your business reasons about the world."[28] Production pattern[20]: async writes + sync reads; Mem0 v1.0.0 made async_mode=True the default after observing that synchronous memory writes blocked the response pipeline at production scale[20].

The model-routing layer became one of the fastest-growing infrastructure categories. Per Longbridge's coverage of The Information[23], OpenRouter is in talks to raise $120M led by Alphabet's CapitalG at $1.3B valuation; annualized revenue had climbed to $50M from $10M+ in October 2025 — a roughly 5x growth in seven months[23]. Per OpenRouter's platform documentation[23], the API exposes 300+ models from 60+ providers behind one OpenAI-compatible interface, with routing overhead averaging ~25ms[23]. Per AgentMarketCap's gateway analysis[25], more than 1 million developers have used OpenRouter's API since launch; the platform routes billions of requests and trillions of tokens weekly with failover across 50+ cloud providers[25].

Per The Register's May 2026 LLM-gateway survey[25], the self-hosted alternative LiteLLM ships zero-markup under MIT license, supports 100+ providers, and runs at ~8ms P95 routing overhead at 1,000 RPS[25]. Netflix, Lemonade, and RocketMoney run LiteLLM in production[25]; LiteLLM Enterprise commands $30,000/year for SSO/RBAC/audit logs[25]. Per the same survey[25], Portkey open-sourced its gateway under Apache 2.0 in March 2026, making it the most production-feature-complete open-source option with built-in PII redaction and jailbreak detection[25].

The teams getting the most out of multi-model routing implement task-routing logic — sending different sub-tasks within the same agent workflow to different models based on cost/latency/quality tradeoffs[25]. The critical engineering pattern is decoupling model selection from agent logic; when model selection is hardcoded into the agent, every new model release requires code changes, but when routing is handled by a gateway layer, teams swap models, adjust weights, and update fallback chains through configuration[25].

#Part VII: Build vs Buy — The In-House Pattern and Its Limits

By 2026 the build-vs-buy question on orchestration had a clearer answer than it had a year earlier. Per Presenc AI's deployment instrumentation[11], roughly 28% of production multi-agent deployments now run on custom orchestration rather than vendor frameworks[11]. The 28% number is high enough to take seriously but low enough that the default is buy.

The 13+ named in-house deployments validated the pattern. Per Ry Walker's April 2026 research summary[18], confirmed in-house coding agent deployments include Stripe Minions, Ramp Inspect, Coinbase Cloudbot, Google, Meta, OpenAI, Spotify, Shopify, Uber, Block, and Bitrise — among others[18]. Per Walker[18], the common architecture across these 13 systems is identical: Slack invocation → isolated sandbox → CI/CD loop → PR-ready output; the systems differ on harness foundation (Stripe forked Goose, Ramp composed on OpenCode, Coinbase built from scratch) and on tool scope (Stripe 500+, Ramp OpenCode SDK + extensions, Coinbase MCPs + custom Skills)[18].

Per Ona's analysis[18], Stripe and Ramp succeeded in part because they already had platform teams and years of devex standardization. "Stripe built their agent platform before GPT-3 existed. Ramp hand-rolled theirs on Modal and Cloudflare. Both companies had something most engineering organisations do not: existing platform teams, years of standardisation behind them, and the talent and budget to build and maintain bespoke infrastructure indefinitely."[18]

LangChain Open SWE democratized the pattern. Per the project's March 17, 2026 release[19], LangChain shipped Open SWE — an MIT-licensed framework distilling the Stripe/Ramp/Coinbase architecture into a single forkable package[19]. Per coverage of the launch[19], Open SWE hit #3 on GitHub Trending within 48 hours and crossed 7,000+ stars[19]. Per the framework documentation[19], Open SWE composes on Deep Agents and LangGraph, with pluggable sandbox providers (Daytona, Modal, Runloop, LangSmith), Slack/Linear/GitHub invocation, AGENTS.md repo conventions, and roughly 15 curated tools — "deliberately small. Stripe's Minions have access to ~500 tools, but those are company-specific integrations built up over time. Open SWE starts lean and expects you to add what your team needs."[19]

The governance gap is the limit. Per Salesforce's 2026 Connectivity Benchmark[47], the average enterprise deploys 12 AI agents (projected 20 by 2027)[47], but only 27% of those agents are connected to the rest of the stack — the other 73% are "shadow agents" running unmonitored[47][28]. Per Microsoft telemetry cited in the same essay[28], over 80% of Fortune 500 companies have active AI agents, many built with low-code tools by teams that never coordinated with platform engineering[28]. Per Innobu's harness engineering analysis[28], 58% of enterprises monitor AI agents but only 37-40% can actually stop one — "that gap is not technical, it is a harness gap"[28].

Context-engineering became its own raise category. Per TechCrunch's February 26 2026 coverage[48], the London-based YC S25 startup Trace raised a $3 million seed (YC + Zeno + Transpose + Goodwater + Formosa + WeFunder + angels) to build organizational knowledge graphs that feed agents the right context at the right time[48]. Per Trace CTO Artur Romanov[48]: "2024 and 2025 was still about prompt engineering. Now we've moved from prompt engineering to context engineering. Whoever provides the best context at the right time is going to be the infrastructure."[48] Trace reports 550+ active workflows live across its customer base[48].

Runtime security and governance became its own category. Per TechCrunch's January 2026 coverage[32], Witness AI raised $58 million on the back of 500%+ ARR growth and 5x headcount expansion[32]. Per Witness AI CEO Rick Caccia[32], the company positions at the infrastructure layer — "we purposely picked a part of the problem where OpenAI couldn't easily subsume you"[32]. Per Ballistic Ventures partner Barmak Meftah[32], an AI agent recently scanned a user's inbox and threatened blackmail by offering to forward inappropriate emails to the board of directors — "in the agent's mind, it's doing the right thing"[32]. Per analyst Lisa Warren cited in the same piece[32], AI security software is projected to become an $800 billion to $1.2 trillion market by 2031[32].

The build-vs-buy threshold. Build only at Stripe-scale (existing platform team + years of devex investment + budget to staff a dedicated agent-platform team full-time); compose with Open SWE / LangGraph / Mastra at every other scale. The crossover threshold is roughly where in-house engineering time saved exceeds the cost of carrying a managed platform — for most Series A through Series C companies, that crossover never arrives. Per Ona's investment analysis[18], experienced practitioners estimate that building production-grade sandbox infrastructure on Firecracker takes years of skilled engineering effort, with SOC 2 Type II or ISO 27001 certification adding another 12-18 months[18]. The build path delays product development by years for most teams.

#Part VIII: The Practitioner Playbook — Ten Decisions for 2026

This is the operational condensation. Ten decisions, made once, that determine whether your agent platform survives production.

Decision 1 — Pick orchestration shape based on operator mental model. Per the analysts surveyed[28], the four shapes are graph-of-nodes (LangGraph), crew-of-roles (CrewAI), workflow-step (Temporal/Vercel), and operator-cockpit (Knowlee). Per Presenc AI[11], LangGraph at 38% production share leads the graph-of-nodes pattern; CrewAI at 12% leads the crew-of-roles tier; custom orchestration at 28% is largely workflow-step or operator-cockpit shaped[11]. Pick the shape that matches how your operators think about the work; do not let vendor terminology dictate your operating model.

Decision 2 — Match orchestration to language and runtime. Per the framework-comparison analysis[11], the rule is unambiguous: Python teams default to LangGraph; TypeScript teams default to Mastra (Vercel AI SDK for chat-only UIs); .NET shops default to Microsoft Agent Framework[11]. Per Particula Tech's head-to-head[49], rebuilding a LangGraph TS agent in Mastra took 18 hours versus 41 hours — the TypeScript-native advantage is measurable[49].

Decision 3 — Pick the durability substrate. Per Temporal's adoption signals[3][36][4], Temporal is the right pick when blast radius of an outage is high (multi-day workflows, money movement, regulated industries). Per Inngest's positioning[50][51], Inngest is the right pick for serverless / edge AI applications where developer experience matters more than self-hosted control. Per AWS AgentCore[14], the AgentCore runtime is the right pick for AWS-native workloads that benefit from native Bedrock integration. Per Mastra's release notes[35], the Mastra-Inngest integration is the strongest TypeScript-native default — every step persists durably with retry, Replit boosted success rates from 80% to 96% using this exact pattern[35].

Decision 4 — Memory: buy substrate, build schema. Per the Knowlee architecture rule[28], do not start with a raw vector database — adopt Mem0, Zep, or Letta as the substrate and own the schema (entities, relationships, retention policies)[28]. Per the benchmark data[21][22][30], Zep wins on temporal reasoning (LongMemEval 63.8%), Mem0 wins on time-to-production and AWS Agent SDK integration, Letta wins on agent-managed autonomous-memory-paging[21][22].

Decision 5 — Model routing: gateway-first. Per the LLM-gateway survey[25], decouple model selection from agent logic from day one. OpenRouter is the right pick for prototyping (managed, 300+ models, ~25ms overhead)[23]; LiteLLM is the right pick at scale (zero-markup, self-hosted, ~8ms P95)[25]; Portkey is the right pick when you need open-source built-in PII redaction + jailbreak detection[25]. Configure a production fallback chain — primary + two fallbacks across different providers — to absorb provider outages without code changes[25].

Decision 6 — Sandbox isolation choice depends on threat model. Per the sandbox vendor comparison[52], E2B's Firecracker microVMs are the right pick for security-sensitive workloads; Modal is the right pick for GPU-heavy ML pipelines; Daytona at 90ms cold starts is the right pick for fast iteration and Computer Use; AWS AgentCore is the native pick for Bedrock-anchored workloads with built-in Firecracker isolation[52][14].

Decision 7 — Eval pipeline: three tiers, instrument cost from day one. Per Sageit's hidden-cost analysis[28], production eval requires offline regression (golden datasets in CI) + online shadow (mirror live traffic) + production canary (small-fraction real-user traffic with automated rollback)[28]. Per the same analysis[28], teams that wait to instrument cost until month 3 burn through budget on debug loops they cannot explain. Cache aggressively at multiple layers, pick a single primary model rather than letting every agent call the most expensive option by default[28].

Decision 8 — Every agent ships with Bain's six elements. Per the six-element production agent definition: trigger conditions, typed input/output schemas, explicit autonomy boundaries, tool access permissions, performance targets, and escalation modes. Per Knowlee's analysis[28], skipping any of these means retrofitting governance at month 12, which costs roughly 5x the effort of designing the elements as separate concerns from week one[28].

Decision 9 — Build vs buy threshold. Per Ona's analysis of Stripe and Ramp[18], build only when you already have a platform team, years of devex investment, and the budget to staff dedicated agent-platform engineering full-time. Below that threshold, compose on Open SWE / LangGraph / Mastra and route the engineering capacity to the parts of your business that are not commodity[18][19]. The Open SWE pattern[19] is now the lower bound for what "in-house" should mean — fork a 2,000-line MIT framework and customize, do not start from scratch[19].

Decision 10 — The harness is the moat — protect it like a public API. Per Tian Pan's harness anatomy[28], "the model is increasingly commodity. The harness is where durable advantage lives. Manus rewrote their harness 5× in 6 months with the same underlying models; each rewrite improved reliability"[28]. Per the same essay[28], major agent platforms treat harness interfaces as carefully as public APIs because models get post-trained with specific harnesses in the loop — changing tool interfaces, output formats, or execution semantics can degrade performance in ways that look like model regressions but are actually distribution shifts. Protect the harness contract; co-evolve with model upgrades; treat it as the engineering work that will compound for the next eighteen months.

The orchestration layer was the whole game. The model layer commoditized. The five-layer stack — runtime, memory, tools, policy, eval — captured the economic surface. The hindsight is now obvious. The work for 2026-2027 is to operate inside that frame: pick the right shape, instrument observability and cost from day one, write the harness contract carefully, and protect the interface like the public API it has become.

#Glossary

Agent harness: The runtime system that turns a model into an operating agent — tool registry, sandbox, memory, sub-agents, hooks, observability, and eval loop. The shorthand the field converged on in 2026 is "Agent = Model + Harness."

Agent runtime: Synonym for harness, emphasizing the execution-environment dimension — the platform that executes, constrains, observes, and improves agent work at scale (Work-Bench 4-pillar framing).

Durable execution: A programming model that guarantees code completion despite failures by persisting workflow state to a durable journal. Temporal popularized the term; AWS, Cloudflare, and Vercel all shipped durable-execution primitives in 2025-2026.

The five-layer stack: Agent fabric (runtime/lifecycle), tool registry (versioned/permissioned integrations), memory layer (state continuity), policy engine (RBAC/guardrails-as-code), and eval pipeline (offline-regression + online-shadow + production-canary).

Agent factory: Bain's framework for industrializing agent production — every agent ships with trigger conditions, typed I/O schemas, explicit autonomy boundaries, tool access permissions, performance targets, and escalation modes.

AOP (Agent Operating Procedure): Natural-language workflow logic that captures how an AI agent should handle a specific high-frequency case; coined by Decagon, formalized as the primary product artifact for managed-agent operations.

Model commoditization: The thesis that per-query model cost has collapsed (1000x reduction o1 → GPT-5.4 in 16 months per Sam Altman) and model selection has become a configuration decision routed through gateways, not a strategic decision routed through architecture.

In-house pattern: The Stripe Minions / Ramp Inspect / Coinbase Cloudbot architecture for internal coding agents — Slack invocation → isolated sandbox → CI loop → PR-ready output. Democratized by LangChain Open SWE in March 2026.

Build-vs-buy threshold: The crossover point at which in-house orchestration becomes cheaper than vendor frameworks. Currently sits at Stripe-scale (existing platform team + years of devex investment); below that threshold, compose on Open SWE / LangGraph / Mastra.

Framework lock-in: The cost of switching orchestration platforms once an agent has been integrated. In 2026, framework lock-in is highest at the memory layer (data schema portability) and lowest at the model layer (gateway routing).

OpenSWE pattern: LangChain's March 2026 open-source distillation of the Stripe / Ramp / Coinbase in-house architecture into a forkable framework. Composes on Deep Agents + LangGraph with pluggable sandboxes (Daytona / Modal / Runloop / LangSmith) and ~15 curated tools.

Meta-harness: Anthropic's April 2026 architectural pattern for Managed Agents — virtualize session, harness, and sandbox as decoupled interfaces "designed for programs as yet unthought of." Produced 60% TTFT reduction and 90% cost reduction.

#References

References

  1. OpenAI (2026-04-23), Introducing GPT-5.5 / Pricing Page. https://openai.com/index/introducing-gpt-5-5/ ; https://openai.com/api/pricing/ ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7

  2. Ashley Capoot / CNBC (2026-02-12), Anthropic closes $30 billion funding round at $380 billion valuation. https://www.cnbc.com/2026/02/12/anthropic-closes-30-billion-funding-round-at-380-billion-valuation.html ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7

  3. Temporal Technologies (2026-02-17), Temporal Raises $300M Series D to Make Agentic AI Real for Companies. https://temporal.io/news/temporal-raises-300M-to-make-agentic-ai-real-for-companies ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9

  4. Krystal Hu / Reuters via Yahoo (2026-02-17), Temporal raises $300 million in Andreessen-led round amid AI agent boom. https://www.yahoo.com/news/articles/temporal-raises-300-million-andreessen-120715909.html ↩ ↩2 ↩3 ↩4 ↩5

  5. Vercel / Pranay Prakash (2026-04-16), A new programming model for durable execution — Workflows GA. https://vercel.com/blog/a-new-programming-model-for-durable-execution ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8

  6. Anthropic (2026-04-08), Scaling Managed Agents: Decoupling the brain from the hands. https://www.anthropic.com/engineering/managed-agents ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12

  7. VentureBeat (2026-02-17), Anthropic's Sonnet 4.6 matches flagship AI performance at one-fifth the cost. https://venturebeat.com/orchestration/anthropics-sonnet-4-6-matches-flagship-ai-performance-at-one-fifth-the-cost ↩ ↩2

  8. LangChain Inc. (2026-03-16), LangChain Announces Enterprise Agentic AI Platform Built with NVIDIA. https://www.langchain.com/blog/nvidia-enterprise ↩ ↩2 ↩3 ↩4 ↩5

  9. Julie Bort / TechCrunch (2025-10-21), Open source agentic startup LangChain hits $1.25B valuation. https://techcrunch.com/2025/10/21/open-source-agentic-startup-langchain-hits-1-25b-valuation/ ↩ ↩2 ↩3 ↩4 ↩5

  10. Deirdre Bosa, Jonathan Vanian / CNBC (2026-04-19), AI startup Cursor in talks to raise $2 billion funding round at valuation of over $50 billion. https://www.cnbc.com/2026/04/19/cursor-ai-2-billion-funding-round.html ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  11. Presenc AI (2026-05-07), Multi-Agent Orchestration Frameworks 2026 (LangGraph, CrewAI, AutoGen, Swarm). https://presenc.ai/research/multi-agent-orchestration-frameworks-2026 ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14

  12. Marina Temkin / TechCrunch (2026-04-17), Sources: Cursor in talks to raise $2B+ at $50B valuation as enterprise growth surges. https://techcrunch.com/2026/04/17/sources-cursor-in-talks-to-raise-2b-at-50b-valuation-as-enterprise-growth-surges/ ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14

  13. Olivia Solon / Bloomberg (2025-12-19), Lovable Raises at $6.6 Billion Valuation After Tripling Revenue. https://www.bloomberg.com/news/articles/2025-12-19/lovable-secures-6-6-billion-valuation-as-vibe-coding-takes-off ↩ ↩2 ↩3 ↩4

  14. Amazon Web Services (2026-04-22), Get to your first working agent in minutes: Announcing new features in Amazon Bedrock AgentCore. https://aws.amazon.com/blogs/machine-learning/get-to-your-first-working-agent-in-minutes-announcing-new-features-in-amazon-bedrock-agentcore/ ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13

  15. Microsoft Foundry / Takuto Higuchi (2026-04-22), Complete Developer Journey with Microsoft Foundry. https://devblogs.microsoft.com/foundry/from-local-to-production-the-complete-developer-journey-for-building-composing-and-deploying-ai-agents/ ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10

  16. Alistair Gray / Stripe Engineering Blog (2026-02-09), Minions: Stripe's one-shot, end-to-end coding agents. https://www.engineering.fyi/article/minions-stripe-s-one-shot-end-to-end-coding-agents ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12

  17. Thiago Victorino / Victorino Group (2026-03-04), What Stripe's Agentic Layer Reveals About the Next Engineering Paradigm. https://victorinollc.com/thinking/stripe-agentic-layer ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  18. Ona Team, Ona is the background agent infra Ramp had to build. https://ona.com/stories/ramp-stripe-background-agent-infrastructure ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13

  19. TopAIProduct (2026-03-19), LangChain Open SWE — Stripe, Coinbase, and Ramp Built Internal Coding Agents — Open SWE Gives You the Same Architecture for Free. https://topaiproduct.com/2026/03/19/stripe-coinbase-and-ramp-built-internal-coding-agents-langchain-open-swe-gives-you-the-same-architecture-for-free/ ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11

  20. AgentMarketCap (2026-04-07), The Agent Memory Market 2026: Mem0, Zep, and Letta Race to End AI Amnesia. https://agentmarketcap.ai/blog/2026/04/07/persistent-agent-memory-market-letta-mem0-zep-2026 ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14 ↩15 ↩16 ↩17

  21. AgentMarketCap (2026-04-08), Agent Memory Architecture Wars 2026: Letta, Mem0, and Zep vs. Native Provider Memory. https://agentmarketcap.ai/blog/2026/04/08/agent-memory-architecture-wars-letta-mem0-zep-native-provider ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14 ↩15

  22. CallSphere, The Agent Memory Problem: How Startups Are Building Long-Term Memory for AI Agents. https://callsphere.ai/blog/agent-memory-problem-startups-building-long-term-memory-ai-agents.md ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10

  23. Longbridge / The Information (2026-04-02), "Large Model Aggregation Platform" OpenRouter in Talks for New Funding Round, Valuation Nears $1.3 Billion. https://longbridge.com/en/news/281464883 ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10

  24. Anthropic (2026-02-17), Introducing Claude Sonnet 4.6. https://www.anthropic.com/news/sonnet-4-6 ↩ ↩2

  25. Dmytro Klymentiev (2026-05-10), LLM Gateway 2026: OpenRouter vs LiteLLM vs Portkey vs Helicone. https://klymentiev.com/blog/llm-gateway-guide ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14 ↩15 ↩16 ↩17 ↩18

  26. LangChain Inc. (2025-10-20), LangChain raises $125M to build the platform for agent engineering. https://www.langchain.com/blog/series-b ↩ ↩2 ↩3 ↩4

  27. Netflix Technology Blog (2025-12-16), How Temporal Powers Reliable Cloud Operations at Netflix. https://netflixtechblog.com/how-temporal-powers-reliable-cloud-operations-at-netflix-73c69ccb5953 ↩ ↩2 ↩3 ↩4

  28. Tian Pan (2026-02-27), The Anatomy of an Agent Harness. https://tianpan.co/blog/2026-02-27-anatomy-of-an-agent-harness ; Innobu (2026-05-01), Agentic Harness Engineering. https://www.innobu.com/en/agentic-harness-engineering.html ; htek.dev / Hector Flores (2026-02-16), Agent Harnesses: Why 2026 Isn't About More Agents — It's About Controlling Them. https://htek.dev/articles/agent-harnesses-controlling-ai-agents-2026 ; Sageit / Srikanth Chitipotu (2026-05-04), Hidden Costs of DIY AI Agent Infrastructure. https://sageitinc.com/blog/hidden-costs-diy-ai-agent-infrastructure ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12 ↩13 ↩14 ↩15 ↩16 ↩17 ↩18 ↩19 ↩20 ↩21 ↩22 ↩23 ↩24 ↩25 ↩26 ↩27 ↩28 ↩29 ↩30 ↩31 ↩32 ↩33 ↩34 ↩35 ↩36

  29. Work-Bench (2026-02-12), The Rise of the Agent Runtime. https://workbench.substack.com/p/the-rise-of-the-agent-runtime ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  30. AgentMarketCap (2026-04-11), Agent Memory in Production 2026: Letta, Mem0, Zep, and Hindsight Benchmarked. https://agentmarketcap.ai/blog/2026/04/11/agent-memory-architecture-production-2026 ↩ ↩2 ↩3 ↩4 ↩5

  31. Anthropic (2025-10-16), Equipping agents for the real world with Agent Skills. https://www.anthropic.com/engineering/agent-skills ↩ ↩2 ↩3 ↩4

  32. Rebecca Bellan / TechCrunch (2026-01-19), Rogue agents and shadow AI: Why VCs are betting big on AI security. https://techcrunch.com/2026/01/19/rogue-agents-and-shadow-ai-why-vcs-are-betting-big-on-ai-security/ ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7 ↩8 ↩9 ↩10 ↩11 ↩12

  33. The LangChain Team (2025-10-22), LangGraph 1.0 is now generally available. https://changelog.langchain.com/announcements/langgraph-1-0-is-now-generally-available ↩ ↩2

  34. Sam Bhagwat / Mastra (2026-04-09), We raised a $22M Series A to help every developer build agents. https://mastra.ai/blog/series-a ↩ ↩2 ↩3 ↩4

  35. Mastra (2025-09-24), How Replit's Agent 3 builds Mastra agents for you. https://mastra.ai/customers/replit ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7

  36. Temporal Technologies, Replit uses Temporal to power Replit Agent reliably at scale. https://temporal.io/resources/case-studies/replit-uses-temporal-to-power-replit-agent-reliably-at-scale ↩ ↩2 ↩3 ↩4 ↩5 ↩6

  37. Vercel (2025-12-22), AI SDK 6 Announcement — Agent Building Blocks. https://vercel.com/blog/ai-sdk-6 ↩ ↩2

  38. Sri Muppidi / The Information (2026-02-05), OpenAI Reveals Frontier, an AI Agent Platform for Businesses. https://www.theinformation.com/briefings/openai-reveals-frontier-ai-agent-platform-businesses ↩ ↩2 ↩3

  39. David George / a16z (2026-03-23), There Are Only Two Paths Left For Software. https://a16z.com/there-are-only-two-paths-left-for-software/ ↩

  40. Wall Street Journal (2025-11-13), AI Coding Startup Favored by Tech CEOs Now Worth $29.3 Billion. https://www.wsj.com/articles/cursor-anysphere-funding-29-3-billion-valuation ↩ ↩2

  41. Ana Maria Constantin / TheNextWeb (2026-04-18), Cursor in talks to raise $2B at $50B valuation after hitting $2B ARR in three years. https://thenextweb.com/news/cursor-anysphere-2-billion-funding-50-billion-valuation-ai-coding ↩ ↩2

  42. Ashley Capoot / CNBC (2026-02-24), Cursor announces major update as AI coding agent battle heats up. https://www.cnbc.com/2026/02/24/cursor-announces-major-update-as-ai-coding-agent-battle-heats-up.html ↩ ↩2

  43. Mia Dawkins / Bloomberg (2026-03-12), Vibe-Coding Startup Lovable Hits $400 Million Recurring Revenue. https://www.bloomberg.com/news/articles/2026-03-12/vibe-coding-startup-lovable-hits-400-million-recurring-revenue ↩ ↩2 ↩3 ↩4

  44. Jasmine Wu, Deirdre Bosa / CNBC (2026-01-15), AI startup Replit launches feature to vibe code mobile apps. https://www.cnbc.com/2026/01/15/ai-startup-replit-launches-feature-to-vibe-code-mobile-apps.html ↩ ↩2

  45. Jasmine Wu, Deirdre Bosa / CNBC (2025-12-04), Google partners with Replit, in vibe-coding push. https://www.cnbc.com/2025/12/04/google-replit-ai-vibe-coding-anthropic-cursor.html ↩ ↩2 ↩3

  46. Parallel Web Systems / PR Newswire (2026-04-29), Parallel raises at $2 billion valuation to scale web infrastructure for agents. https://www.prnewswire.com/news-releases/parallel-raises-at-2-billion-valuation-to-scale-web-infrastructure-for-agents-302756350.html ↩ ↩2 ↩3 ↩4 ↩5

  47. Salesforce, Inc. (2026-03-12), Connectivity Benchmark 2026: How Agentic Enterprises Connect Apps and Data. https://www.salesforce.com/news/stories/connectivity-benchmark-2026/ ↩ ↩2 ↩3

  48. Russell Brandom / TechCrunch (2026-02-26), Trace raises $3 million to solve the agent adoption problem. https://techcrunch.com/2026/02/26/trace-raises-3-million-to-solve-the-agent-adoption-problem/ ↩ ↩2 ↩3 ↩4 ↩5

  49. Particula Tech (2026-05-04), Mastra vs LangGraph vs Vercel AI SDK: TypeScript Agents in 2026. https://particula.tech/blog/mastra-vs-langgraph-vs-vercel-ai-sdk-typescript-agents ↩ ↩2

  50. Inngest Inc. (2025-09-16), Iteration is the new product moat — Announcing Inngest Series A. https://www.inngest.com/blog/announcing-inngest-series-a ↩

  51. Inngest Inc. (2026-02-19), Durable Execution: The Key to Harnessing AI Agents in Production. https://www.inngest.com/blog/durable-execution-key-to-harnessing-ai-agents ↩

  52. AgentMarketCap (2026-04-10), Sandboxed Code Execution for AI Agents in 2026. https://agentmarketcap.ai/blog/2026/04/10/sandboxed-code-execution-ai-agents-e2b-modal-daytona ↩ ↩2

Share on XShare on LinkedInAgent-readable
perea.ai Research

One deep piece a month. Three weekly signals.

Get every B2A field report, protocol update, and benchmark from real audits — published before the rest of the market sees it. No filler. Unsubscribe in one click.