head to head · open source
ActivePieces vs Vibe-Workflow
ActivePieces has 25,364 GitHub stars, 4,428 forks, 573 open issues and last shipped yesterday. Vibe-Workflow has 637 stars, 162 forks, 1 open issues and last shipped 2 months ago. ActivePieces leads on adoption by 3,882% (25,364 vs 637 stars). ActivePieces is written in TypeScript under a custom or non-standard licence; Vibe-Workflow is written in JavaScript under MIT. ActivePieces has attracted 17% as many forks as stars, Vibe-Workflow 25%. ActivePieces was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| ActivePieces | Vibe-Workflow | |
|---|---|---|
| GitHub stars | ★ 25K | ★ 637 |
| License | Custom / other | MIT |
| Written in | TypeScript | JavaScript |
| Last push | 2026-11-04 | 2026-09-17 |
| Forks | ⑂ 4.4K | ⑂ 162 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick ActivePieces if
- You weight community size — 25K stars and counting
- You want the Custom / other license terms
- Your stack matches TypeScript
- You value the larger contributor base for long-term maintenance
pick Vibe-Workflow if
- You want the Vibe-Workflow feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches JavaScript
- You evaluated both and Vibe-Workflow fits your workflow better
About ActivePieces
An open source replacement for Zapier Documentation 🌪️ Create a Piece 🖉 Deploy 🔥 Join Discord 🤯 Welcome to Activepieces All in one AI automation designed to be extensible through a type safe pieces framework written in TypeScript . When you contribute pieces to Activepieces they become automatically available as MCP servers that you can use with LLMs through Claude Desktop, Cursor or Windsurf! 🔥 Why Activepieces is Different: 💖 Loved by Everyone : Intuitive interface and great experience for both technical and non technical users with a quick learning curve. 🌐 Open Ecosystem: All pieces are open source…
read the full ActivePieces overview →
About Vibe-Workflow
Vibe Workflow — Open Source Alternative to Weavy AI, Freepik Spaces, Krea Nodes & FloraFauna AI Vibe Workflow is a free, open source node based AI workflow builder — the self hostable alternative to Weavy AI, Freepik Spaces, Krea Nodes, and FloraFauna AI. Designed around "Artistic Intelligence," it gives creators and developers a visual, modular pipeline editor for designing, editing, and composing AI generated images and video — with no vendor lock in. Read the full story: I built Open Weavy because paid AI creative tools were getting ridiculously expensive. 🚀 Prefer a hosted version? Try Vibe Workflow…
read the full Vibe-Workflow overview →
More in Productivity & Utilities
Related comparisons
More Automation projects
Compare either of these against the rest of the Automation field.
Frequently asked questions
Is ActivePieces or Vibe-Workflow more popular?
ActivePieces has 25,364 GitHub stars and Vibe-Workflow has 637. ActivePieces has the larger community by that measure.
Are ActivePieces and Vibe-Workflow free?
Both are open source. ActivePieces has no licence declared in this registry, and Vibe-Workflow is licensed under MIT. Both are free to self-host.
What is the difference between ActivePieces and Vibe-Workflow?
ActivePieces is written in TypeScript and Vibe-Workflow in JavaScript. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, ActivePieces or Vibe-Workflow?
Choose ActivePieces if you want the larger community (25,364 stars) or its Custom / other licence terms. Choose Vibe-Workflow if its feature set, stack or MIT licence fits better. Both are self-hostable.