Durable Workflow state
Temporal automatically persists the state and event history of running Workflows, allowing execution to continue from completed progress after failures, crashes, restarts, or deployments.
Temporal
Freemium
Temporal is a durable execution platform for building applications whose workflows can recover from failures without losing completed progress. Developers define workflows and failure-prone activities in supported programming languages, then run them locally, self-hosted, or through Temporal Cloud.
O que é Temporal?
Temporal is a durable execution platform for applications that need reliable, stateful processes. Developers define business logic as Workflows and represent failure-prone interactions—such as API calls, service operations, or external actions—as Activities. Temporal persists workflow state and event history so a Workflow can resume after a service crash, deployment, network failure, or other interruption instead of requiring custom checkpointing and recovery code.
The platform provides execution primitives for retries, timeouts, timers, schedules, signals, queries, updates, task queues, and child Workflows. These primitives support processes that finish quickly as well as workflows that remain active for days, weeks, or months. Execution visibility tools allow teams to inspect, replay, reset, and rewind Workflow executions.
Temporal supports local development and production deployment through two hosting paths: the open-source Temporal project can be run in a team’s own environment, or Temporal Cloud can host the Temporal Service. The site lists SDKs for Go, Java, Python, TypeScript, .NET, PHP, Ruby, and Rust, with support for polyglot workflows. Temporal Cloud uses usage-based pricing for Actions and storage, with a free offer that includes $150 in credits for 90 days.
O que Temporal pode fazer?
Activity retries and failure handling
Activities can use retry policies with backoff, timeout classes, heartbeating, and saga compensation for operations that depend on unreliable APIs, networks, or services.
Long-running timers and schedules
Durable Timers support waits lasting days, weeks, or months, while Schedules provide cron-like workflow starts that can be paused, restarted, stopped, and backfilled.
Workflow interaction and composition
Signals, Queries, and Updates support interaction with running Workflows; Child Workflows provide composition and fault isolation, and Temporal Nexus supports durable calls across teams.
Execution visibility and controls
Teams can inspect Workflow executions, event histories, and stack traces, and can replay, rewind, or reset executions, including batch resets.
SDKs and deployment options
Developers can use SDKs for Go, Java, Python, TypeScript, .NET, PHP, Ruby, and Rust, develop locally, and deploy either a self-hosted open-source service or Temporal Cloud.
Casos de uso
“AI agents and tool workflows”
Run agent and tool calls as durable Activities so long-running AI processes can recover from interruptions. The site specifically references support for the OpenAI Agents SDK and Google ADK.
“Order fulfillment”
Coordinate multi-step order processing across services so a failed dependency does not discard completed work or leave the order process without a recovery path.
“Financial transfers and durable ledgers”
Model money movement and compensating actions as code, including a fallback such as returning funds when a later transfer step fails.
“Human-in-the-loop processes”
Pause a Workflow while waiting for a person to submit or approve information, then continue the same process when the external interaction arrives.
“Infrastructure and delivery workflows”
Orchestrate cloud infrastructure deployments, CI/CD processes, GPU fleet operations, or other scheduled and event-driven jobs that benefit from retries, rollbacks, and execution visibility.
Perguntas frequentes
How does Temporal recover a Workflow after failure?
Temporal captures Workflow state and persists event history as execution proceeds. When an interruption occurs, the Workflow can resume from its recorded progress, while Activities can be retried according to their configured policies.
Can Temporal run locally or only in the cloud?
Both options are available. Developers can install and run a local development server, self-host the open-source Temporal Service in their own environment, or use Temporal Cloud as the hosted option.
Which programming languages have Temporal SDKs?
The product pages list SDKs for Go, Java, Python, TypeScript, .NET, PHP, Ruby, and Rust. The platform also describes support for polyglot Workflows.
How is Temporal Cloud priced?
Temporal Cloud uses usage-based pricing. Billable Actions represent operations between an application and Temporal Cloud, while workflow history is charged as active or retained storage. The pricing page lists a free offer with $150 in credits for 90 days, with paid usage and support options available afterward.
What kinds of processes fit Temporal?
Temporal is intended for stateful, multi-step processes that need retries, durable waiting, human input, scheduling, or recovery from service failures. Examples on the site include AI pipelines, order fulfillment, financial transfers, long-running Workflows, CI/CD, customer acquisition, and infrastructure operations.
Informações rápidas
- Product category
- Durable execution and workflow orchestration platform
- Deployment
- Self-hosted open-source service or Temporal Cloud
- Primary users
- Software developers and engineering teams building distributed applications
- SDK languages
- Go, Java, Python, TypeScript, .NET, PHP, Ruby, and Rust
- Core execution model
- Workflows coordinate durable business logic; Activities handle failure-prone operations
- Cloud pricing model
- Usage-based Actions and storage, with a free offer of $150 in credits for 90 days