A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 10.9 · clear
A · leads
96.5
25,581 stars · MIT
B
85.6
21,625 stars · GPL-3.0
Activepieces versus Obtainium is a Workflow Automation comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Activepieces is written mainly in TypeScript; Obtainium is written mainly in Dart. The composite score is 96.5 for Activepieces and 85.6 for Obtainium.
Activepieces has 25,581 GitHub stars to Obtainium's 21,625, a gap of 3,956 (1.18×). Forks are 4,476 for Activepieces and 704 for Obtainium. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 78.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and Obtainium was last pushed on 01 November 2026 (16 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 403 for Obtainium (0.019 per star). Issue-health scores are 70 and 84; activity scores are 100 and 78.
Activepieces is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Obtainium is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for Activepieces and 64 for Obtainium. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and Obtainium (21,625 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: Activepieces is open source, Obtainium is open source.
The lead is split. Activepieces is furthest ahead on license flexibility (96 to 64), while Obtainium is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Activepieces finishes ahead at 96.5 against Obtainium at 85.6, a 10.9 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | Activepieces | Obtainium |
|---|---|---|
| GitHub stars | 25,581 | 21,625 |
| Forks | 4,476 | 704 |
| Open issues | 961 | 403 |
| Adoption | 100 | 98 |
| Activity | 100 | 78 |
| Community | 100 | 78 |
| Issue health | 70 | 84 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 85.6 |
Activepieces is a TypeScript workflow tool positioned as a self-hosted automation builder. It focuses on connecting business apps with a visual builder and an MIT-licensed core.
Get Android app updates straight from the source.
Activepieces has more GitHub stars: 25,581 versus 21,625 for Obtainium. The gap is 3,956 stars.
Activepieces was pushed more recently: 17 November 2026 versus 01 November 2026 for Obtainium. That is 16 days apart.
Yes. This catalog marks both Activepieces and Obtainium as self-hostable. Confirm each project's deploy docs before you plan a migration.
Activepieces is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Obtainium is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Activepieces scores 96.5 and Obtainium scores 85.6. This page calls that a clear lead for Activepieces.