Activepieces logo

Activepieces

MIT-licensed no-code automation and AI agents builder, an open Zapier alternative

23k TypeScript MIT 6 days ago

Overview

Activepieces is an open-source, no-code automation tool with a visual flow builder and a growing library of community-contributed "pieces" (connectors) written in TypeScript. It positions itself as an MIT-licensed Zapier alternative with strong AI/MCP support for building agents. The community edition is genuinely open source, with enterprise features available separately.

Key features

  • Visual no-code flow builder for automations
  • Community-contributed library of connectors ("pieces") written in TypeScript
  • AI agent and MCP support for building agentic workflows
  • Deployable via Docker, Docker Compose, Kubernetes, or manually

Our take

Activepieces is a credible open-source take on Zapier, with a clean visual flow builder and a community-driven library of TypeScript "pieces" that you can extend when a connector doesn't yet exist. The MIT-licensed community edition is genuinely open source rather than a crippled teaser, and the deployment options are broad, covering everything from a single Docker container to Kubernetes. Its current bet on AI agents and MCP support is a real plus if that's where you're headed. The caveat is the usual open-core split: some enterprise features live outside the community edition, and the connector catalog, while growing, is still smaller and less battle-tested than a mature commercial iPaaS, so you may end up writing pieces yourself. For self-hosters who want control and an open license that's a reasonable price; just verify the specific integrations you depend on actually exist before you commit.

Ideal for: Teams that want a self-hostable, genuinely MIT-licensed Zapier alternative and don't mind building their own connectors when one is missing.

Where it falls short of Zapier

  • Smaller connector catalog than Zapier/Make; many niche apps still missing.
  • Enterprise features (SSO, audit logs, projects/RBAC, embedding) require the paid edition.
  • Self-hosting needs Postgres and Redis, so it is not a single-container setup.
  • Younger ecosystem means fewer pre-built templates and community examples.

We list the gaps honestly so you can decide if the trade-off is worth owning your data.

Tags

no-code
workflow
ai-agents
mcp
integrations
self-hosted
Maintain Activepieces?

Claim this listing to keep it accurate, add a deploy template, or feature it on relevant pages.

Show off your self-host difficulty score

Embed the Activepieces difficulty badge in your README — it links back here.

Self-host difficulty badge← add this to your README
[![Self-host difficulty](https://openreplace.com/api/badge/activepieces)](https://openreplace.com/activepieces)

Similar open-source projects

Other self-hostable tools in the same space worth comparing.

Sponsored

Fair-code workflow automation with 400+ integrations and native AI nodes

115k TypeScript Sustainable Use License 4 days ago
2/5
1-click
Activepieces vs n8n

Programmatically author, schedule, and monitor workflows as Python DAGs

46k Python Apache-2.0 4 days ago
4/5
Activepieces vs Apache Airflow

Event-driven orchestration platform for scheduled and API-triggered workflows

27k Java Apache-2.0 6 days ago
3/5
Activepieces vs Kestra

Flow-based low-code programming for wiring together APIs, services, and devices

23k JavaScript Apache-2.0 6 days ago
2/5
Activepieces vs Node-RED