Open-Source Zapier Alternative (2026, Free Self-Hosted)

Listed OSI projects: Activepieces (activepieces/activepieces) and Automatisch (automatisch/automatisch). Source-available (SUL, not OSI): n8n — n8n vs Zapier. Identification: Zapier. Other tools: Dev & Coding.

Sourced snapshot

Field	Activepieces (2026-10-17)	Automatisch (2026-10-17)
Repository	github.com/activepieces/activepieces	github.com/automatisch/automatisch
Stars / Forks	24,955 / 4,313	13,996 / 1,063
License	MIT (core); enterprise directory separately licensed	AGPL-3.0 (community edition); enterprise edition separately licensed
Created	2022-12-03	2021-09-30
Integrations	280+ (all open-source on npm)	Not quoted in README (described as “other existing solutions”)
Deployment	Docker, Helm (self-hosted); cloud version available	Docker (self-hosted); cloud version available
Credit system	None (unlimited runs in community edition)	Not detailed in seed data
Key features	MIT core, no credit system, unlimited flows/users, 60% community-contributed integrations, 280+ MCP toolkit for LLMs	AGPL-3.0 community edition, business automation, Docker deployment
Homepage	activepieces.com	automatisch.io
Quality vs Zapier	Not independently tested	Not independently tested

Why Activepieces is on a Zapier hub

“Open source Zapier alternative” is a durable query. The most-starred open-source workflow automation platform with an OSI-approved license we could source on 2026-10-17 from a public GitHub repository is Activepieces (activepieces/activepieces): MIT core, 24,955 stars, created 2022-12-03. It is an open-source workflow automation platform with 280+ integrations, all published as open-source on npm, with unlimited flows and users in the community edition and no credit system. That is the same job family as a hosted automation product, not a proof that it substitutes for Zapier’s connector quality, UI, or customer support.

Zapier is Zapier Inc.’s hosted automation platform. We use the Zapier mark only to identify the search. We did not copy Zapier pricing or feature names into a quality table.

Activepieces: MIT core with 280+ integrations

Activepieces (activepieces/activepieces) is an MIT-licensed core open-source automation platform. 24,955 stars, created 2022-12-03. Key features:

• MIT core: The core is MIT; only the enterprise directory is licensed separately. Community edition runs unlimited flows and users, with nothing metered.
• 280+ integrations: Every integration is open-source and published on npm. 60% community-contributed.
• No credit system: Community edition has no credit system and no cap on runs.
• Largest open-source MCP toolkit: All 280+ pieces are available as MCP servers for LLMs (Claude Desktop, Cursor, Windsurf).
• Intuitive interface: Loved by both technical and non-technical users with a quick learning curve.
• Deployment: Self-host with Docker or Helm; hosted cloud version at activepieces.com.

The README quotes: “As simple as Zapier but with the more advanced options of Make, and cheaper.” “The completely customizable and fluid builder is much better than Zapier.” Those are user testimonials, not a sourced benchmark.

Tech stack: All integrations are versioned and published directly to npmjs.com upon contribution. You can create your own integration using the TypeScript framework. Read more on the pricing page.

Automatisch: AGPL-3.0 community edition

Automatisch (automatisch/automatisch) is an AGPL-3.0 open-source business automation tool. 13,996 stars, created 2021-09-30. It lets you connect different services like Twitter, Slack, and more to automate business processes.

The README says: “There are other existing solutions in the market, like Zapier and Integromat, so you might be wondering why you should use Automatisch.” Key differences:

• AGPL-3.0 community edition (all files except those containing “.ee.” in their name)
• Enterprise edition is separately licensed (files with “.ee.” in the name)
• Single repository: Maintains both licenses in one repo for development ease
• Deployment: Self-host with Docker; hosted cloud version at automatisch.io

The repository contains both AGPL-licensed and Enterprise-licensed files. All files that contain “.ee.” in their name fall under the Enterprise license. All other files fall under the AGPL-3.0 license. See the LICENSE file for more information.

MIT core versus AGPL-3.0

Activepieces: MIT core (most permissive). The enterprise-licensed code sits in one clearly marked directory and needs a subscription only for production use. Community edition is unlimited: no credit system, no cap on runs, no metered usage. All 280+ integrations are open-source MIT and published on npm.

Automatisch: AGPL-3.0 community edition. AGPL requires releasing your modified source code if you provide the software as a network service (i.e., if you host Automatisch for others). Enterprise edition is separately licensed. Integration count and community edition feature limits are not detailed in the README we checked.

Not legal advice.

Self-hosted versus cloud

The code is on GitHub. Activepieces and Automatisch both support self-hosting with Docker (Activepieces also Helm). If your requirement is “run workflow automation on hardware I control,” start from the respective repository and follow the deployment instructions. If your requirement is “a free automation UI without DevOps,” both projects offer hosted cloud versions (activepieces.com, automatisch.io), which are different artifacts and are not what this hub ranks.

What we left out

n8n (n8n-io/n8n) is a popular automation tool but uses the Sustainable Use License (SUL), not an OSI-approved open-source license. SUL allows internal business and personal use but prohibits hosting for others or offering as a competing service. We excluded it from this list because the license is source-available, not open-source.

Other open automation platforms (including Pipedream, Windmill, Temporal, and others) will join this list when we attach them explicitly. Activepieces is the MIT-core option with 280+ npm integrations and no credit system. Automatisch is the AGPL-3.0 community edition with Docker deployment.

Self-reported benchmark data on each README is quoted on the respective project pages and labeled self-reported. They are not a Zapier comparison.

How to choose

• Need MIT-licensed core with unlimited flows/users and no credit system: Activepieces (activepieces/activepieces, 25K stars).
• Need 280+ open-source integrations all published on npm: Activepieces.
• Need MCP servers for LLMs (Claude Desktop, Cursor, Windsurf): Activepieces (280+ MCP toolkit).
• Need AGPL-3.0 community edition with Docker deployment: Automatisch (automatisch/automatisch, 14K stars).
• Need commercial-friendly license for a hosted SaaS product (no source disclosure for network service): Activepieces (MIT core); avoid Automatisch (AGPL-3.0 requires source disclosure).
• Need to fork and customize without releasing modified code: Activepieces (MIT); avoid Automatisch (AGPL requires disclosure).

What “open” does not mean

Activepieces and Automatisch code is open-source and not gated. That is a “download and deploy” story. It is still your responsibility to set up the infrastructure (Docker, databases, reverse proxies, SSL), configure integrations (API keys, OAuth apps), and manage updates. “Free” on this hub means the code’s license is not a SaaS SKU; it does not mean zero DevOps effort or no API costs for third-party services. We have not published a one-click deployment recipe for either.

README testimonials and comparison tables (“better than Zapier,” “cheaper than Make”) stay user-reported. Treating any of those as “beats Zapier” would be editorial malpractice.

See also Dev & Coding, ChatGPT alternatives, and GitHub Copilot alternatives.