Directory / Temporal
Temporal
Verified
Durable workflow engine for sequencing long-running jobs.
Temporal persists workflow state across process death, retries, and long-running agent requests. Teams use it as the orchestration spine when an agent run must retain state. Model inference belongs to the application.
- Model support
- Multi-model
- Deployment
- Cloud, Self-hosted
- Open source
- Yes
- License
- MIT (server); Temporal Cloud is a service
- Pricing model
- Mixed
- Added / updated
- 19 Aug 2026 / 19 Aug 2026
temporal.io · Docs · Source
Assessment
Temporal persists workflow state across process failures, retries, timeouts, and signals. It fits long-running agent jobs; code generation, model selection, and sandboxing remain application concerns. The MIT server and Temporal Cloud are separate operating choices.
Strengths
- Durable execution with an MIT server you can run.
- Retries, timeouts, and signals that match long agent jobs.
- Cloud and self-hosted options with the same programming model.
Limitations
- Durable execution; agent harness and sandbox remain separate.
- Self-hosting adds operational cost.
- A cron job may not warrant a workflow cluster.
Compare
- vs inngest : Durable workflow runtimes for sequencing work.