ActivepiecesvsWuzAPI
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Activepieces | WuzAPI | |
|---|---|---|
| Score | 81/100 | 57/100 |
| Rank in category | #4 of 32 in Workflow Automation | #7 of 14 in Messaging |
| GitHub stars | 25 265 | 1 046 |
| Stars, last 30 days | +565 | — |
| Stable releases, 12 months | 37 | 3 |
| Latest release | 0.92.3-hotfix.2 · 28 Oct 2026 | v1.1.0 · 26 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | No |
| License | Other | MIT |
| Main language | Typescript | Go |
Which one should you pick?
Activepieces scores 81/100 against 57/100 for WuzAPI, so it is the safer default.
Activepieces ships more often: 37 stable releases in the past year, against 3 for WuzAPI.
If you want the quickest setup, Activepieces is easier to run; WuzAPI needs more configuration.
Activepieces is growing faster right now (+565 stars in 30 days).
Activepieces details →WuzAPI details →
Swap a project
Keep Activepieces, compare it with
Keep WuzAPI, compare it with