ActivepiecesvsCasibase
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Activepieces | Casibase | |
|---|---|---|
| Score | 81/100 | 66/100 |
| Rank in category | #3 of 31 in Workflow Automation | #43 of 208 in AI Agents |
| GitHub stars | 25 559 | 5 745 |
| Stars, last 30 days | +534 | +58 |
| Stable releases, 12 months | 41 | 100 |
| Latest release | 0.93.0 · 8 Nov 2026 | v2.95.1 · 5 Oct 2026 |
| Setup | Easy | Easy |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Typescript | Go |
Which one should you pick?
Activepieces scores 81/100 against 66/100 for Casibase, so it is the safer default.
Casibase ships more often: 100 stable releases in the past year, against 41 for Activepieces.
Activepieces is growing faster right now (+534 stars in 30 days).
Key differences
- License: Activepieces is MIT, Casibase is Apache-2.0.
- Language: Activepieces is written mainly in Typescript, Casibase in Go.
- Platforms only Activepieces lists: Kubernetes.
- Platforms only Casibase lists: Docker, Linux, Windows.
- Features only Activepieces lists: Automatic Retries, Branching, Custom integrations framework (pieces), Flow versioning and 9 more.
- Features only Casibase lists: Autonomous agent loops, File & media management, MCP tool integration, Multi-Provider LLM Support and 10 more.
- Both offer: Audit Logs.
Activepieces details →Casibase details →
Swap a project
Keep Activepieces, compare it with
Keep Casibase, compare it with