Durable Workflow
Open-source workflow orchestration engine for PHP, Python, and Rust that keeps long-running business processes alive for days, with automatic retries and full execution history.
🔗 Visit Durable Workflow
Description
Some tasks in software don't finish in a second — they take days, involve waiting for a human to approve something, or need to survive a server restart partway through. Regular code and simple job queues aren't built for that; if the process crashes at step 7 of 10, you usually have to start over. Durable Workflow is built specifically to keep track of exactly where a long-running process left off, so it can pick back up instead of restarting, and it does this across three different programming languages.
Durable Workflow provides durable execution — automatic retries, full execution history persistence, and saga-pattern support for coordinating multi-step processes that can span minutes to days — with native support for PHP (including an embedded mode built for Laravel), Python, and Rust. It handles parallel execution, child workflows, signal-based coordination and querying (so external systems can send events to or ask questions of a running workflow), and timer-based scheduling. Deployment is flexible: embedded directly in a Laravel app, self-hosted as a standalone server, or via a managed cloud option, with a dedicated operator UI called Waterline for monitoring running workflows.
💬 Our review
The short version: Durable Workflow brings the "durable execution" pattern popularized by Temporal to a genuinely useful new combination — PHP/Laravel developers in particular have had far fewer good options in this space than Python or Go teams.
Temporal and AWS Step Functions are the established names in durable execution/workflow orchestration — Temporal in particular has a large, mature ecosystem and is the de facto standard for teams already on Go, Java, or Python. Durable Workflow's real differentiator is PHP support, and specifically an embedded Laravel mode that doesn't require running a separate orchestration server — a gap Temporal doesn't fill, since it has no first-class PHP SDK. The tradeoff is ecosystem maturity: Temporal has years more production hardening, a larger community, and more integrations, while Durable Workflow (1,200+ stars) is younger and has a smaller support base if something goes wrong in production. Worth adopting specifically if you're a Laravel/PHP shop that needs durable execution and doesn't want to bolt on a Go/Java-centric tool like Temporal; if you're already on Python, Java, or Go, Temporal's maturity is hard to argue against.
💰 Pricing
📊 Global score
🤖 AI-enriched data
100% gratuit et open source (auto-hébergé) ; option cloud managée mentionnée sans tarif public détaillé
Pros
Support natif PHP avec mode embarqué Laravel, rare sur ce marché
Multi-langages (PHP, Python, Rust)
Historique d'exécution complet et reprise automatique après échec
Interface d'opérateur dédiée (Waterline)
Cons
Écosystème plus jeune et plus restreint que Temporal
Moins de retours de production à grande échelle
Option cloud managée sans tarification publique claire