A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 20.9 · decisive
A · leads
96.5
25,581 stars · MIT
B
75.6
2,919 stars · license n/a
Activepieces versus LoopForge 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; LoopForge is written mainly in Go. The composite score is 96.5 for Activepieces and 75.6 for LoopForge.
Activepieces has 25,581 GitHub stars to LoopForge's 2,919, a gap of 22,662 (8.76×). Forks are 4,476 for Activepieces and 423 for LoopForge. On the log scale used inside this pair, adoption is 100 versus 79, and the fork community is 100 versus 72.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and LoopForge was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 176 for LoopForge (0.060 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
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. LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for Activepieces and 30 for LoopForge. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and LoopForge (2,919 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, LoopForge is unpriced in this catalog.
Activepieces is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 66 points (96 vs 30), and the tightest is self-hosting at 0 points (100 vs 100).
Activepieces finishes ahead at 96.5 against LoopForge at 75.6, a 20.9 point decisive 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 | LoopForge |
|---|---|---|
| GitHub stars | 25,581 | 2,919 |
| Forks | 4,476 | 423 |
| Open issues | 961 | 176 |
| Adoption | 100 | 79 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 70 | 52 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 75.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.
Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
Activepieces has more GitHub stars: 25,581 versus 2,919 for LoopForge. The gap is 22,662 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and LoopForge 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. LoopForge is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Activepieces scores 96.5 and LoopForge scores 75.6. This page calls that a decisive lead for Activepieces.