Temporal
Durable execution: workflows written as ordinary code that survive crashes and restarts without losing their place.
Highlights
- Durable execution: workflow state is automatically persisted and replayed after any failure
- Write workflows as code in Go, Java, Python, TypeScript, .NET, and PHP
- Built-in retries, timeouts, and idempotency so failure handling isn't hand-rolled
- Long-running and stateful workflows that can span seconds to months
- Signals, queries, and timers for human-in-the-loop steps and event-driven coordination
- Open-source self-hosted server plus a managed Temporal Cloud option
- Polyglot orchestration across services and languages, used as an agentic backend
- Observability via the Temporal UI for inspecting, debugging, and replaying workflow histories
External link — opens temporal.io in a new tab. Temporal is a third-party product; we are not affiliated with it.
About Temporal
What it is
Temporal runs long-lived workflows reliably. You write the logic as ordinary code; Temporal records every step and replays state after a failure, so a process that takes hours or weeks survives crashes, deployments and outages without losing where it was. It is widely used for microservice orchestration and increasingly for AI agent workflows.
Why it's different
The problem it removes is the one every team rebuilds badly: a multi-step process that must not half-happen. The usual solution is a queue, a status column and retry logic that nobody trusts, growing more intricate with every edge case. Temporal makes durability a property of the runtime, so the code reads like a function rather than a state machine. It is particularly apt for agents, whose steps are slow, failure-prone and expensive to repeat. The honest costs: it is a substantial piece of infrastructure to operate, the programming model takes real time to internalise, and the determinism requirements catch people out. It is not a light dependency.
How people use it
It is used for order processing, provisioning, financial transactions, long-running data pipelines and agent workflows — anywhere partial completion is unacceptable. The self-hosted version is open source and the cloud offering removes the operational burden, which is how most teams start. The usual advice holds: adopt it when you have felt the pain of the alternative, because before that the programming model looks like overhead rather than relief.
Written by the n3os team. We are not affiliated with Temporal.
This listing was written from public information, without Temporal’s involvement. If you own it and something here is wrong — or you would rather not be listed at all — email us and we will correct or remove it.
Get the ones worth knowing about
We write one of these for every tool worth the trouble. Get the new ones, plus what we have found genuinely useful lately.
Your address goes to Buttondown, who send the emails on our behalf. One click unsubscribes, and the list is never sold or shared.