Cognition raises $2B at $48B, nearly doubling its valuation since May

Cognition raises $2B at $48B, nearly doubling its valuation since May

Good morning ๐Ÿ‘‹ A valuation nearly doubled in four months, and this time the revenue actually kept pace. Cognition's new round is below, along with the question it doesn't answer: what happens once every engineering org is running three of these agents at once.

In today's issue:

Get tomorrow's issue in your inbox.

One concise AI brief, sent after the signal clears the noise.


๐Ÿ”ญ THE ONE THING

๐Ÿค– Cognition raises $2B at $48B, nearly doubling its valuation since May

Cognition just closed a Series E north of $2 billion, led by Andreessen Horowitz and Accel, with Founders Fund, General Catalyst, and Avenir all writing checks again. The valuation: $48B, up from $26B four months ago. The number that actually justifies it: run-rate revenue jumped from $492M to nearly $900M over that same stretch, which means Devin's usage is compounding faster than the check sizes are. That kind of revenue velocity is rare enough that I'll take the valuation at face value for once. The harder question is whether "engineers as architects, agents as swarms" holds up once every enterprise coding budget has three of these tools bolted on at once.


๐Ÿง  MODELS & RELEASES


๐Ÿ”ฌ RESEARCH HIGHLIGHTS


๐Ÿ› ๏ธ TRY THIS

Put a regression gate on your agent's behavior, not just its code

Cognition's $48B valuation is a bet that agents are production software now, which means the old "eyeball the demo, ship it" review process doesn't cut it. AWS just published the wiring for the fix: run your agent against a fixed prompt set on every PR, score the outputs, block the merge if it got worse.

1. Deploy your agent (and any MCP tools it calls) to a runtime your CI can hit, AgentCore or otherwise, alongside your existing pipeline.

2. Build a small, fixed set of test prompts, weighted toward your worst past failures rather than happy-path cases.

3. On each PR, invoke the agent against that set and score the responses against a baseline.

4. Fail the check and block the merge when a score drops below threshold. Treat it like a broken unit test.

Prompt: Given this agent's system prompt and its last 5 reported failure cases, write 10 adversarial test prompts that would catch a regression in tool-calling, refusal behavior, or output format.

Worth a look: Amazon Bedrock AgentCore Evaluations is the reference implementation above, complete with the GitHub Actions YAML if you'd rather copy than build.


๐Ÿ”— QUICK LINKS


See you tomorrow, same repo, presumably more agents in it.

Pradeep Perugu

Get inovAIte in your inbox.