Product1 publisher3 min readPublished
Temporal's $550m round prices its crash-resume log at about 50 times revenue
Temporal closed a $550 million round at a $12.55 billion valuation, roughly 50 times the revenue it reports. The product it sells exists to remember which step of a crashed job already ran.
The Product Desk · Product desk
What happened
- Temporal Technologies confirmed it has closed a $550 million investment at a $12.55 billion valuation, about a month after reports of its fundraising plans first appeared.
- Lightspeed and Wellington Management co-led the Series E, joined by Goldman Sachs, Tiger Global, T. Rowe Price, SV Angel and several existing investors.
- The company said its annualized revenue recently topped $250 million after more than tripling over the past year.
- Temporal Cloud has more than 4,300 paying users, among them Nvidia and OpenAI, while the Workers that execute customer tasks run on the customers' own infrastructure.
- Temporal sells against hand-written failure handling, which SiliconANGLE's account says takes a significant amount of custom code and slows software projects.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- decision Teams currently running recovery out of a cron job and a status column now have a priced comparison for that code, and because the core is open source, adopting it does not have to begin with a Cloud invoice.
- cost At roughly $58,000 a year for the average paying Cloud customer, the in-house alternative has to beat that on maintenance, not on the cost of writing it once.
- constraint Paying for the hosted version puts the coordination layer at a vendor while the compute stays on your hardware, so the next 3am incident review has two owners and one of them does not carry your pager.
- precedent Revenue grew faster than the customer count, so the vendor's model assumes each team moves a second and third workflow across after the first one lands. A buyer should expect that expansion to be the renewal conversation.
The failure this is sold against is the half-finished job: the process dies at step seven of twelve, and nobody can say for certain which of the first six already fired. SiliconANGLE's account of the product describes a log written as each sub-step completes, so the restarted program reads the last step it finished and carries on from there [3]. Retry counts are a parameter a developer sets. When the retries run out, the platform can start a standby copy of the program and hand it the workflow [4].
Anyone weighing build against adopt has four pieces to price, not one: the log that survives your own process dying, the retry policy, the standby takeover, and the queue routing that can pin work belonging to the same user request onto Workers on a single server so they exchange data faster [5]. In-house schedulers usually have some version of the retry policy. The log is tedious to write and unpleasant to debug, and in my view that is where a homegrown version gives out first.
Temporal disclosed the money figures itself [12]. Against the $12.55 billion valuation, $250 million annualized works out to about 50 times revenue [1]. Divide the same revenue by the more than 4,300 paying Temporal Cloud users and the average one is paying on the order of $58,000 a year [2]; SiliconANGLE reports that the company's revenue comes from the Cloud product, so the division is fair [8]. Customer count is up 139%, or 2.39 times, while revenue more than tripled, which puts the average revenue per paying customer up by at least a quarter [13][3].
Samar Abbas, Temporal's co-founder and chief executive, made the agent case directly: "As agents take on more critical work across more systems, every additional step creates another place to fail," he said [10]. The company also says its platform lends itself to improving the reliability of AI workloads [9]. Temporal did not break out how much of the $250 million comes from agent or AI workloads [4], so that reading rests on the framing plus two names in the customer list, Nvidia and OpenAI [14].
The count worth running before Monday is this: how many workflows in production must survive a process restart mid-run, and how many steps the longest of them takes through systems you do not control. One workflow with three internal steps is a weekend of code. Nine workflows, one of them thirty steps deep into third-party APIs where a duplicated call charges a customer twice, and you are already maintaining a worse version of this, at which point the remaining question is whether you run the open-source tool yourself [6] or pay Temporal to coordinate the queues [8].
What to watch
- Whether Temporal's next disclosure separates agent-workload revenue from the rest of the $250 million, which is currently a single self-reported figure.
- Whether the product spend from this round extends to hosting Workers, which today sit on the customer's own infrastructure.
- Whether customer count keeps growing near 139% in the next update, or slows while revenue holds, which would make the growth almost entirely expansion inside existing accounts.