Activepiecesvsflowise-ai
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Activepieces | flowise-ai | |
|---|---|---|
| Score | 81/100 | 74/100 |
| Rank in category | #3 of 32 in Workflow Automation | #22 of 209 in AI Agents |
| GitHub stars | 25 426 | 55 561 |
| Stars, last 30 days | +520 | +72 |
| Stable releases, 12 months | 40 | 5 |
| Latest release | 0.87.3-hotfix.1 · 29 Oct 2026 | flowise@3.1.4 · 29 Jul 2026 |
| Setup | Easy | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Typescript | Typescript |
Which one should you pick?
Activepieces scores 81/100 against 74/100 for flowise-ai, so it is the safer default.
Activepieces ships more often: 40 stable releases in the past year, against 5 for flowise-ai.
Activepieces is growing faster right now (+520 stars in 30 days).
flowise-ai is archived, so it won't get fixes. Prefer the other one for anything long-lived.
Key differences
- License: Activepieces is MIT, flowise-ai is Apache-2.0.
- Platforms only flowise-ai lists: Docker, Node.js.
- Features only Activepieces lists: Audit Logs, Automatic Retries, Branching, Custom integrations framework (pieces) and 10 more.
- Features only flowise-ai lists: Broad LLM/vector-store support, Custom MCP tool support, Execution traces and metrics, Horizontal scaling with queue and 6 more.
Activepieces details →flowise-ai details →
Swap a project
Keep Activepieces, compare it with
Keep flowise-ai, compare it with