A · leads
Activepieces
96.5
25,581 stars · MIT
Workflow Automation
Activepieces leads by 5.3 · narrow
A · leads
96.5
25,581 stars · MIT
B
91.2
23,434 stars · AGPL-3.0
Activepieces versus skyvern 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; skyvern is written mainly in Python. The composite score is 96.5 for Activepieces and 91.2 for skyvern.
Activepieces has 25,581 GitHub stars to skyvern's 23,434, a gap of 2,147 (1.09×). Forks are 4,476 for Activepieces and 2,246 for skyvern. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 92.
Push history: Activepieces was last pushed on 17 November 2026 (0 days ago), and skyvern was last pushed on 17 November 2026 (0 days ago). Open issues stand at 961 for Activepieces (0.038 per star) and 301 for skyvern (0.013 per star). Issue-health scores are 70 and 84; 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for Activepieces and 52 for skyvern. This is a procurement signal, not legal advice.
In Workflow Automation, both Activepieces (25,581 stars) and skyvern (23,434 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, skyvern is open source.
The lead is split. Activepieces is furthest ahead on license flexibility (96 to 52), while skyvern is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
Activepieces finishes ahead at 96.5 against skyvern at 91.2, a 5.3 point narrow 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 | skyvern |
|---|---|---|
| GitHub stars | 25,581 | 23,434 |
| Forks | 4,476 | 2,246 |
| Open issues | 961 | 301 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 70 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 91.2 |
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.
Automate browser based workflows with AI
Activepieces has more GitHub stars: 25,581 versus 23,434 for skyvern. The gap is 2,147 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Activepieces and skyvern 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. skyvern is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Activepieces scores 96.5 and skyvern scores 91.2. This page calls that a narrow lead for Activepieces.