#1★ TOP PICK
n8n
Powerful, self-hostable workflow automation with a large node library.
82
SOURCE-AVAILABLESustainable Use License (source-available, fair-code; not OSI-approved)SELF-HOSTLOCAL-FIRST
n8n is the tool most people mean by "self-hosted Zapier." It offers a visual workflow editor with 400+ integration nodes, branching logic, and code steps, plus AI/agent nodes for LLM-driven automations. You can self-host it for free with Docker and keep every workflow and credential on your own server, or use n8n's paid cloud. Note the license: n8n uses the source-available Sustainable Use License, not an OSI-approved open-source license.
Strengths
- +Runs entirely on your own server via Docker; workflows and credentials stay on your infrastructure
- +Very large node library (400+ integrations) plus HTTP and code nodes to reach almost any API
- +Strong branching, error handling, and built-in AI/agent nodes for LLM workflows
- +Very active project and large community (190k+ GitHub stars, near-daily commits)
- +Workflows export as JSON, so they are portable between your own n8n instances
Trade-offs
- −License is source-available (Sustainable Use License), not OSI open-source; it permits internal/self-hosted business use but restricts offering n8n itself as a hosted service to third parties
- −Self-hosting requires running and maintaining a server and database
- −Fewer prebuilt app integrations than Zapier's 7,000+ catalog; some connections need HTTP/API setup
- −Steeper learning curve than a pure no-code tool for complex flows
Free to self-host; paid n8n Cloud tiers available #2
Node-RED
Fully open-source, flow-based programming that runs on hardware as small as a Raspberry Pi.
95
OPEN SOURCEApache-2.0SELF-HOSTLOCAL-FIRST
Node-RED is a mature, Apache-2.0 flow-based automation tool built on Node.js. You wire together "nodes" in a browser editor to move and transform data between APIs, webhooks, MQTT, databases, and thousands of community-contributed integrations. It is the most sovereign option here on licensing and hardware: it runs locally, stores flows as open JSON files, and is light enough for a Raspberry Pi. Its roots are in IoT and event automation rather than SaaS-to-SaaS connectors.
Strengths
- +Fully open-source under Apache-2.0, an OSI-approved license
- +Runs entirely locally on modest hardware, including a Raspberry Pi
- +Flows are stored as open JSON files you own and can version-control
- +Huge library of community nodes and a long, stable track record
- +Excellent for IoT, webhooks, MQTT, and custom logic
Trade-offs
- −Flow-based, developer-leaning model; less turnkey than Zapier's app-picker for connecting SaaS tools
- −Many SaaS integrations rely on community nodes that vary in quality and maintenance
- −You maintain the runtime, updates, and any exposed endpoints yourself
- −Building polished multi-app business automations takes more effort than a no-code UI
#3
Activepieces
No-code automation with a Zapier-like UI and an MIT-licensed core.
88
OPEN SOURCEMIT (core); enterprise modules under a separate commercial licenseSELF-HOSTLOCAL-FIRST
Activepieces is a no-code automation platform whose builder feels close to Zapier: pick a trigger, add action steps, connect apps. Its core is MIT-licensed and self-hostable via Docker, and it has a growing catalog of community "pieces" (integrations) plus AI steps. Some advanced/enterprise features sit under a separate commercial license, so read the LICENSE if you need those. For teams that want a familiar no-code experience they can host themselves, it is a strong balance of openness and ease.
Strengths
- +MIT-licensed core, OSI-approved and genuinely open
- +No-code builder that is close in feel to Zapier, easing the transition
- +Self-hostable with Docker; workflows and data stay on your infrastructure
- +Active project with a fast-growing library of community integrations and AI steps
Trade-offs
- −Some advanced/enterprise features are under a separate commercial license, not MIT
- −Integration catalog, while growing quickly, is smaller than Zapier's
- −Self-hosting means you run and update the stack yourself
- −Younger project than Node-RED, so some pieces are still maturing
Free to self-host (MIT core); paid cloud and enterprise tiers available #4
Automatisch
AGPL-licensed, self-hosted automation focused on data privacy.
85
OPEN SOURCEAGPL-3.0 (core); enterprise (.ee) files under a separate commercial licenseSELF-HOSTLOCAL-FIRST
Automatisch is an open-source automation tool that positions itself as a privacy-focused, self-hosted alternative for connecting apps and building workflows. Its core is AGPL-3.0 licensed and runs on your own server via Docker, keeping data in the EU or wherever you host. Some enterprise files are under a separate commercial license. Its connector library is smaller and its release cadence has been slower than the busiest projects here, so check that it covers the apps you need.
Strengths
- +Core is AGPL-3.0, a strong copyleft OSI-approved license
- +Self-hosted by design, with an explicit data-privacy and data-residency focus
- +Straightforward Docker deployment; your data stays on your infrastructure
- +Clear, approachable no-code interface for common app-to-app flows
Trade-offs
- −Noticeably smaller integration catalog than Zapier, n8n, or Activepieces
- −Slower development cadence than the busiest projects here (last major repo activity earlier in 2026)
- −Some enterprise features sit under a separate commercial license
- −AGPL-3.0 copyleft terms may need review for certain commercial redistribution scenarios
Free to self-host; paid cloud tier available #5
Huginn
Fully MIT-licensed, agent-based automation for power users.
84
OPEN SOURCEMITSELF-HOSTLOCAL-FIRST
Huginn is a long-standing, MIT-licensed system for building "agents" that watch for events and act on your behalf: scraping sites, monitoring feeds, sending alerts, and chaining actions. It is entirely self-hosted and open, giving you complete data ownership. The trade-off is that it is more technical than a no-code builder: you configure agents through forms and JSON, and it targets developers and tinkerers rather than non-technical users.
Strengths
- +Fully MIT-licensed and open-source, with complete data ownership
- +Self-hosted; all agents and data live on your own server
- +Very flexible for monitoring, scraping, feeds, and event-driven alerts
- +Established project with a large community and long history
Trade-offs
- −Development cadence has slowed to mostly maintenance in recent years
- −Configuration is JSON- and form-driven; far more technical than a no-code UI
- −Ruby-and-database stack is heavier to run than the lightest options here
- −Fewer polished, prebuilt SaaS integrations than Zapier or n8n