A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 19.2 · decisive
A · leads
96.5
25,581 stars · MIT
B
77.3
2,639 stars · MIT
Activepieces versus shepherd 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; shepherd is written mainly in Python. The composite score is 96.5 for Activepieces and 77.3 for shepherd.
Activepieces has 25,581 GitHub stars to shepherd's 2,639, a gap of 22,942 (9.69×). Forks are 4,476 for Activepieces and 227 for shepherd. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 65.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and shepherd was last pushed on 09 September 2026 (69 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 13 for shepherd (0.005 per star). Issue-health scores are 70 and 96; activity scores are 100 and 58.
Both Activepieces and shepherd are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and shepherd (2,639 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, shepherd is open source.
The lead is split. Activepieces is furthest ahead on recent activity (100 to 58), while shepherd is furthest ahead on issue health (96 to 70). Choose the dimension a rollout cannot compromise on.
Activepieces finishes ahead at 96.5 against shepherd at 77.3, a 19.2 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 | shepherd |
|---|---|---|
| GitHub stars | 25,581 | 2,639 |
| Forks | 4,476 | 227 |
| Open issues | 961 | 13 |
| Adoption | 100 | 78 |
| Activity | 100 | 58 |
| Community | 100 | 65 |
| Issue health | 70 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 77.3 |
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.
A runtime substrate that turns an agent's execution into a reversible, Git-like trace, so meta-agents can observe, fork, replay, and revert any run. Couples agent and environments in a copy-on-write fork ~5x faster than docker commit, with ~95% KV-cache reuse on replay. Framework built for meta-agents to supervise, optimize, and train other agents
Activepieces has more GitHub stars: 25,581 versus 2,639 for shepherd. The gap is 22,942 stars.
Activepieces was pushed more recently: 17 November 2026 versus 09 September 2026 for shepherd. That is 69 days apart.
Yes. This catalog marks both Activepieces and shepherd 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. shepherd 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Activepieces scores 96.5 and shepherd scores 77.3. This page calls that a decisive lead for Activepieces.