Temporal's $550M round values durable execution at 2.5x its February price

A Temporal workflow is ordinary code written against a language-specific SDK. The server coordinates execution across services and records enough state to continue after a process, a dependency or a network connection fails, retrying failed operations and resuming long-running work after an outage ^[12].

Divide 1.9 trillion by August's 31 days and the platform averaged about 61 billion actions a day ^[3]. An increase of more than 350% puts the same month a year earlier at no more than about 422 billion ^[4]. Spread across more than 4,300 paying customers, August works out to a mean of roughly 442 million actions each ^[5]. The mean says little about the median when one named customer moves 414 million Stories a day ^[10].

February priced the company at $5 billion ^[4]. September priced it at $12.55 billion, 2.51 times as much, about seven months later ^[1][1][2]. Divided by paying customers, the new price is about $2.9 million each ^[6]; divided by the 570 people Temporal now employs, about $22 million a head ^[8][7]. Temporal says the proceeds go to global operations, work on the platform's core primitives, and the reliability and security work its enterprise customers have asked for ^[11].

For the 1.9 trillion figure to say anything about your bill, you need actions per run, and the announcement reports platform totals ^[6]. An agent run makes model calls, uses tools and leans on third-party services that can time out, return unexpected output or fail midway ^[14]. A payment that pauses for a confirmation, or an onboarding that waits days for a human approval, is the older shape of the same problem, and Temporal's design predates the agent push ^[13]. Those two shapes do not emit the same number of actions per run. Temporal Cloud's signup offer includes $1,000 in credits, and the announcement does not establish standard production rates ^[15].

The alternative to the meter is the MIT-licensed server, run in-house, with your own operators carrying it ^[15]. Or the engine already in the cloud account: AWS Step Functions, AWS Simple Workflow Service, Azure Durable Functions, with Uber Cadence, which preceded Temporal, still an option, and Restate and Trigger.dev among the newer entrants ^[16].

Writing state persistence that survives a lost process is hard, and Temporal has been shipping it since before agents were the reason to buy it ^[12][13]. The round prices the claim that agent runs need that machinery badly enough that no team should rebuild it ^[14]. For the agent half of the claim, this announcement offers one customer datapoint: OpenAI's usage up 60-fold in less than a year, reported by Temporal ^[10].