duragraphvstemporal
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| duragraph | temporal | |
|---|---|---|
| Score | 43/100 | 82/100 |
| Rank in category | #6 of 7 in AI Workflows | #1 of 1 in Workflow |
| GitHub stars | 146 | 24 539 |
| Stars, last 30 days | +-15 | +729 |
| Stable releases, 12 months | 9 | 14 |
| Latest release | v0.8.1 · 10 Sept 2026 | v1.32.2 · 2 Nov 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Go |
Which one should you pick?
temporal scores 82/100 against 43/100 for duragraph, so it is the safer default.
temporal ships more often: 14 stable releases in the past year, against 9 for duragraph.
If you want the quickest setup, duragraph is easier to run; temporal needs more configuration.
temporal is growing faster right now (+729 stars in 30 days).
Key differences
- License: duragraph is Apache-2.0, temporal is MIT.
- Platforms only duragraph lists: Go, Homebrew, Linux.
- Features only duragraph lists: CQRS, Event Sourcing, Fault Tolerance, Go SDK and 10 more.
- Features only temporal lists: Archival to blob storage, Durable workflow execution, Embedded server mode, gRPC API and 8 more.
duragraph details →temporal details →