Skip to content
Rush Commerce
Software & Dev3 min read

Temporal's $12.55B round: your retry layer is now a bill

Temporal raised $550M at a $12.55B valuation on 200%+ net dollar retention. Durable execution works — but it meters the step, not the seat. Budget the retry.

Temporal announced a $550M Series E at a $12.55B valuation on September 14. The valuation is not the number operators should read. The number is net dollar retention above 200% since February — existing customers more than doubled what they spend. Durable execution has stopped being a library you install and started being a meter that runs.

What actually happened

Per Temporal's announcement, Lightspeed led the round, co-led by Wellington Management, Growth Equity at Goldman Sachs Alternatives, and Tiger Global, with T. Rowe Price and SV Angel participating and a16z, Sequoia, Index, GIC, Sapphire and Amplify returning. Valuation roughly doubled.

The operating numbers, as reported by GeekWire and the release:

  • Annualized revenue run rate past $250M, up more than 200% year over year
  • Net dollar retention above 200% since February
  • Temporal Cloud processed 1.9 trillion+ actions in August, up more than 350% year over year
  • Open-source installs past 43 million in August, up 134% since January
  • 4,300+ paying customers, including OpenAI, NVIDIA, Netflix, JPMorgan Chase, Shopify, DoorDash, Block and Anysphere

Read those two growth rates together. Revenue grew 200%. Actions grew 350%. The billable unit is the step, and agents generate steps faster than companies generate seats.

Why durable execution matters for your business

The reliability problem became a metered problem. We have argued before that the thing breaking your agent is not the model — it is a process that died on step four of seven and nobody knows whether step three already charged the card. Durable execution fixes that. It also means every retry, every heartbeat, every timer is now a line item. An agent that loops because a flaky vendor API returns 502s does not just fail slowly. It bills.

Instrument before you adopt. Before you put a workflow engine under anything, count the steps in your highest-volume process and multiply by your real failure rate. If that number surprises you, it will surprise you again on an invoice. Set a per-workflow action budget and alert on it the same way you alert on token spend.

43 million open-source installs is a real fork in the road. Temporal's core is open source and self-hostable. For a small shop running a few thousand workflows a month, a single self-hosted cluster is a Tuesday, not a platform team. Cloud is worth it when your ops burden exceeds the bill — not before. Decide that on your own numbers.

And the pattern outranks the vendor. Idempotent steps, state persisted outside the agent process, a durable log of what was attempted versus what happened. That is the thing you actually need. Temporal sells the best-known implementation of it; a $12.55B valuation is evidence the problem is real, not evidence you must buy this particular answer.

Key takeaways

  • Temporal raised $550M at $12.55B on September 14, led by Lightspeed; valuation roughly doubled
  • ARR past $250M, up 200%+ YoY; net dollar retention above 200% since February
  • Temporal Cloud processed 1.9T+ actions in August, up 350%+ YoY — actions grew faster than revenue
  • The billable unit is the workflow step, so every agent retry has a price
  • Count steps × failure rate before you adopt, and set a per-workflow action budget
  • 43M+ open-source installs: self-hosting is a real option until ops burden exceeds the bill
  • Idempotency, external state and a durable run log are the pattern — the vendor is a choice

Adding a workflow engine, or just adding a bill? We size the retry math first, then build the durable layer — self-hosted or managed, whichever your volume actually justifies. See how we scope it or send us your worst workflow.

Sources: BusinessWire, GeekWire.

  • #durable-execution
  • #ai-agents
  • #reliability
  • #infrastructure
  • #cost-control
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.