supabase-automated-self-hostvstemporal
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| supabase-automated-self-host | temporal | |
|---|---|---|
| Score | 48/100 | 82/100 |
| Rank in category | #13 of 15 in Backend as a Service | #1 of 1 in Workflow |
| GitHub stars | 506 | 24 063 |
| Stars, last 30 days | +0 | +785 |
| Stable releases, 12 months | 0 | 11 |
| Latest release | — | v1.30.8 · 12 Oct 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Shell | Go |
Which one should you pick?
temporal scores 82/100 against 48/100 for supabase-automated-self-host, so it is the safer default.
temporal ships more often: 11 stable releases in the past year, against 0 for supabase-automated-self-host.
If you want the quickest setup, supabase-automated-self-host is easier to run; temporal needs more configuration.
temporal is growing faster right now (+785 stars in 30 days).
supabase-automated-self-host details →temporal details →