E2B, Which Gives AI Agents Their Own Cloud Computers, Passes $120 Million in Annual Recurring Revenue With 100% Inbound

E2B says annual recurring revenue has surpassed $100 million, up from $8 million a year ago, and projects more than $150 million of net new revenue this year. The company said almost 100% of its growth comes from agentic-led growth (ALG); this is its first public revenue disclosure.

Analysis

The investable signal is less the headline run rate than whether agent execution becomes a recurring infrastructure workload. If agents repeatedly need isolated environments to run code and use tools, E2B could sit in a durable control layer; underlying compute demand may flow to cloud providers even if E2B captures limited economics. The counterweight is bundling: major cloud platforms can package sandbox execution with existing developer and AI services, while open-source alternatives pressure pricing. Security incidents would be especially damaging because isolation is part of the product’s core value proposition.

Treat the growth and “agentic-led” acquisition claims as company-reported, not evidence yet of durable economics. ARR is not recognized revenue, and the projected net-new figure needs clarification on period, definition, and whether it represents contracted ARR or revenue. Rapid adoption can also mask usage volatility, customer concentration, support costs, or weak gross margins. Over 1–3 months, verification of retention, expansion, gross margin, and customer concentration matters more than the milestone; over 6–18 months, cloud bundling and agent workload persistence determine whether this is a standalone layer or a feature.

There is no direct public-equity exposure identified in the supplied data, so avoid forcing a proxy trade. The contrarian risk is that public markets capitalize agent infrastructure demand before proving that workloads are persistent and independently monetizable.

Key Decisions for Investors

• No standalone trade on the announcement: E2B is private and the supplied information does not establish a clean public-market read-through.
• Put cloud-platform bundling and developer-tool pricing on watch; consider a relative-value trade only if evidence shows agent execution is shifting workloads toward independent infrastructure rather than bundled services.
• Request confirmation of ARR versus recognized revenue, the time period and definition behind projected net-new revenue, gross margin, net retention, customer concentration, and usage-based churn before treating the growth trajectory as underwritable.
• Falsify the durable-infrastructure thesis if subsequent disclosures show slowing expansion or retention, deteriorating unit economics, material security failures, or cloud vendors offering comparable execution as a bundled feature.