Activepieces vs flyto-core
Two of the top projects in Workflow automation with AI, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.
Activepieces
Self-hosted workflow automation with TypeScript integrations, alternative to Zapier
flyto-core
Python engine that runs YAML workflows of browser, API and file steps
Verdict
Activepieces ranks higher, 88 to 55. Of the 4 score parts we measure for both, Activepieces leads on 2, flyto-core on none and 2 are even.
- AdoptionActivepieces leads by 81 points, 81 to 0: a wide gap.
- FreshnessEven at 100.
- MaintenanceEven at 83.
- Agent-readyActivepieces leads by 85 points, 85 to 0: a wide gap.
Pick Activepieces if you are
Teams self-hosting Zapier-style automation with LLM and MCP integrations
- Pieces are open-source TypeScript npm packages with hot reloading for local development
- 280+ pieces usable as MCP servers from Claude Desktop, Cursor or Windsurf
Pick flyto-core if you are
Engineers scripting repeatable browser, API and file workflows
- Per-step run records, with checkpoints and replay where safe
- Usable from Python, YAML, local HTTP API or MCP
| What we compare | Activepieces | flyto-core |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 81, widely used | 0, niche |
| Freshness | 100, active | 100, active |
| Maintenance | 83, healthy | 83, healthy |
| Agent-ready | 85, ready | 0, none |
| Facts from GitHub and the README | ||
| Stars | 25.7k | 483 |
| License | custom license (read the license) | Apache-2.0 (permissive) |
| Last commit | Nov 2026 | Nov 2026 |
| Last release | Nov 2026 | Nov 2026 |
| Language | TypeScript | Python |
| Docker | Yes | Yes |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
Activepieces
Activepieces is a no-code workflow builder with loops, branches, auto retries, HTTP calls and npm-backed code steps, and flows are versioned. Integrations are called pieces: TypeScript npm packages, 280+ of which are exposed as MCP servers for Claude Desktop, Cursor or Windsurf. It also has AI pieces for several providers, human-in-the-loop approvals, and chat and form triggers.
Who it is for: Teams self-hosting Zapier-style automation with LLM and MCP integrations
Strengths
- Pieces are open-source TypeScript npm packages with hot reloading for local development
- 280+ pieces usable as MCP servers from Claude Desktop, Cursor or Windsurf
- Flows are versioned and support loops, branches and auto retries
- Built-in approval, delay, chat and form triggers for human-in-the-loop flows
Weaknesses
- Enterprise features sit under a separate commercial license, not MIT
- Automation-first; AI agents are one feature rather than the core design
- README claims of 200+ and 280+ pieces are inconsistent
- no GPU
- Docker + Compose
- Compose runs PostgreSQL, Redis
- Models: OpenAI
flyto-core
flyto-core is the Python execution engine behind Flyto2. It ships 482 registered modules and 41 built-in recipes covering browser automation, APIs, files and data, and can be driven from Python, YAML workflows, a local HTTP API or an MCP server. Each run keeps a per-step record, with checkpoints and replay where safe.
Who it is for: Engineers scripting repeatable browser, API and file workflows
Strengths
- Per-step run records, with checkpoints and replay where safe
- Usable from Python, YAML, local HTTP API or MCP
- 482 modules and 41 built-in recipes ready to run
- Checks reported tool evidence against the action's contract
Weaknesses
- ROS 2 robot support still lacks full end-to-end hardware sign-off
- Physical device actions need a trusted host to approve them
- Browser recipes need Playwright and a Chromium install
- README gives no LLM or model integration details
- no GPU
- Docker
- Needs Python, Playwright, Chromium
More in Workflow automation with AI
Building with these?
We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.