Tool Open source
Temporal is a durable execution platform developed by Temporal Technologies for building scalable applications and workflows. Its server executes application logic as Workflows, automatically handling intermittent failures and retrying failed operations so applications do not need to implement all timeout, retry, and recovery logic themselves. Developers implement Workflows, Activities, and Workers with SDKs for multiple programming languages, then use the Temporal server, CLI, and Web UI to run and inspect them. The open-source Temporal server originated as a fork of Uber's Cadence and is distributed under the MIT License.
6 uses taken from transcripts — each links to the moment in the video.
A durable execution platform for building scalable and reliable applications and workflows. Its server automatically handles intermittent failures and retries, reducing the need to write custom timeout, retry, and recovery logic.
Temporal is a platform for durable execution. It takes user-written code and makes it resilient while providing SDKs in multiple programming languages.
Temporal provides durable execution and state management for distributed systems and agents. Its workers, workflows, activities, wait conditions, and signals let systems pause for human input, survive failures, and recover with their state intact.
The open-source Temporal repository contains the software and primitives used to build durable, stateful workflows. The speaker points viewers to it as a resource for the demo and Temporal code.
A durable execution platform that lets workflows and agents survive crashes: state and progress persist in an event history, workers can die and be replaced, retries and human-approval signals are recorded, and LLM tool calls aren't re-spent after a failure. The video demos a $2,500 payout workflow that survives intentional worker kills without losing state.
A durable execution framework for applications and agents. It maintains application state so that if a worker fails or is killed mid-run, it reconstructs the state to the point of failure and continues without re-running LLM calls or re-executing activities, with built-in retries and a payload encoder for encrypting sensitive data out of the event history.
5 in the library.