A year ago, we were a different company. The mission is the same, but the scale and urgency around it have changed completely.
The problems we’ve been solving for years — how to build systems that work correctly over time, handle failures gracefully, don’t lose state when things go wrong — became everyone’s problems this year. AI made them impossible to ignore. And developers didn't just adopt Temporal. You pushed it into production systems we never anticipated, building architectures that surprised even us.
I’m proud of what this year looked like, and deeply grateful — to our team, and to you, our developer community, for trusting us with your most critical systems.
What we built together#
Temporal’s revenue grew 380% year-over-year. Weekly active usage jumped 350%. Installs hit 20 million installs per month, up 500%. Behind those numbers are real teams shipping production systems that can’t go down.
That’s always been what drives Max and me.Temporal is bottoms-up: we’re in the field, solving problems for people writing code. But something I’ve come to appreciate as CEO is how far that developer trust carries. The developers who choose Temporal become advocates inside their organizations, making the case to leadership that system design has to account for failure, and that Durable Execution isn’t optional.
This year, we handled 150,000+ actions-per-second spikes without notice, and we helped our customers’ systems stay online during major cloud outages while others went dark. That kind of track record is what turns adoption into company-wide commitment.
The trust we’ve earned#
In October, I sat in a CIOSE study group, a roundtable where CIOs and enterprise leaders evaluate emerging technology directly with the founders building it. The people in that room were thinking about platform shifts, organizational risk, and what happens when critical systems fail.
The conversation made something click for me. Temporal’s developer roots translate directly into enterprise trust. Developers choose us because we solve hard problems, their engineering leaders see the productivity gains, and CIOs see systems that run reliably at predictable cost. It builds on itself.
And when you trust your infrastructure, you stop over-provisioning just to be safe. Temporal is cloud-agnostic from day one — Cloud or open-source, your choice. You control your architecture and your spend. As AI systems get more stateful and long-running, that only matters more.
Why we raised this round#
The opportunity got bigger than we expected, faster than we expected. Long-running workflows and stateful architectures used to be edge cases, but they aren’t anymore. We want to stay ahead of that.That’s why we raised this Series D. We’re investing in better primitives for AI workflows, observability, performance at scale, and enterprise capabilities that don’t come at the cost of developer experience. We’re building for systems that have to work in production over time, not just in demos.
We’re also hiring, more than ever before. We want people to take reliability seriously, those who’ve operated at scale and understand what it takes to keep systems running when things go sideways. If that sounds like you, come talk to us.
What’s next#
Our community keeps growing, and so does the complexity of what you’re building on Temporal.
The open-source trajectory over the last six months speaks for itself. The feedback we get from teams running us in production is what keeps us getting better, and this funding lets us act on it — better features, more support, continued investment in both open source and Temporal Cloud.
Thank you for trusting us with your production systems. We take it seriously.
This is just the beginning.
— Samar
Join our Slack community. Come to Replay May 5–7 in San Francisco.