ActivepiecesvsTrinity
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Activepieces | Trinity | |
|---|---|---|
| Score | 80/100 | 57/100 |
| Rank in category | #4 of 32 in Workflow Automation | #60 of 209 in AI Agents |
| GitHub stars | 25 276 | 713 |
| Stars, last 30 days | +557 | +2 |
| Stable releases, 12 months | 40 | 4 |
| Latest release | 0.87.3-hotfix.1 · 29 Oct 2026 | v1.0.0 · 20 Oct 2026 |
| Setup | Easy | Advanced |
| Official Docker image | Yes | Yes |
| License | Other | Apache-2.0 |
| Main language | Typescript | Python |
Which one should you pick?
Activepieces scores 80/100 against 57/100 for Trinity, so it is the safer default.
Activepieces ships more often: 40 stable releases in the past year, against 4 for Trinity.
If you want the quickest setup, Activepieces is easier to run; Trinity needs more configuration.
Activepieces is growing faster right now (+557 stars in 30 days).
Activepieces details →Trinity details →