What are the best alternatives to n8n for self-hosted automation?
Quick Answer: The strongest self-hosted alternatives to n8n as of July 2026 are ActivePieces (MIT-core licence, 700+ pieces), Windmill (AGPLv3, code-first across 12 languages), and Kestra (Apache 2.0, engineering-grade orchestration). Huginn (MIT, 49,000+ stars) remains a proven agent-based option, and Trigger.dev covers code-first TypeScript jobs. Automatisch is no longer recommended without caveats: its hosted cloud shut down and repository activity stalled in January 2026.
Best Self-Hosted Alternatives to n8n
n8n is the most widely deployed self-hosted automation platform (196,000+ GitHub stars as of July 2026), licensed under its fair-code Sustainable Use License — free for internal business use, with enterprise features under a paid licence. It is not the only option. Teams that need a more permissive licence, a code-first model, or a different automation paradigm have several actively maintained alternatives; the licence, connector count, and maintenance figures below were verified 14 July 2026.
ActivePieces: Closest to the n8n Experience
ActivePieces provides a visual workflow builder similar to n8n's with a clean interface that non-technical users find approachable. The core is MIT-licensed (enterprise features under packages/ee/ carry a commercial licence), and the official catalog lists 755 pieces as of July 2026 — the project promotes "700+ integrations", a large share community-contributed, and its open-source pieces double as MCP servers for AI-agent use (the official MCP catalog lists 700+).
- License: MIT core (Community Edition); commercial licence for
ee/enterprise features - Deployment: Docker and Docker Compose
- Integrations: 700+ pieces (755 listed in the official catalog, July 2026)
- Activity: 23,000+ GitHub stars, commits daily as of July 2026
- Best for: Teams wanting n8n-like visual building with an MIT-core licence
Windmill: Code-First Multi-Language Platform
Windmill puts code first: scripts become workflows, UIs, and scheduled jobs. Language coverage has expanded well beyond its original set and now spans Python, TypeScript (Bun/Deno), Go, Bash, SQL, GraphQL, PowerShell, Rust, PHP, C#, Java, and Ansible as of July 2026.
- License: AGPLv3 (client libraries Apache 2.0; enterprise-flag code proprietary)
- Deployment: Docker and Kubernetes with production-ready configurations
- Languages: 12 supported, from Python and TypeScript through Rust, Java, and Ansible
- Activity: 17,000+ GitHub stars, commits daily as of July 2026
- Best for: Developer teams who prefer writing code over dragging nodes
Kestra: Engineering-Grade Orchestration
Kestra has grown into one of the most active open-source orchestrators (Apache 2.0, 27,000+ GitHub stars as of July 2026). Workflows are declared in YAML and triggered by events or schedules, with installation via Docker, Docker Compose, Kubernetes/Helm, or a standalone JAR. It sits closer to Airflow-style data and infrastructure orchestration than to Zapier-style app connecting — the right fit when workflows are owned by an engineering team.
- License: Apache 2.0
- Deployment: Docker, Docker Compose, Kubernetes/Helm, standalone JAR (2 vCPU / 4 GiB minimum)
- Model: Declarative YAML flows, event-driven triggers, plugin ecosystem
- Best for: Engineering-led automation and data/infrastructure orchestration
Huginn: Agent-Based Monitoring and Automation
Huginn is the original self-hosted automation tool, predating n8n by years. Specialized agents monitor websites, process data, and trigger actions, connected in directed graphs. It remains maintained (last commit July 2026) as a community-run Ruby on Rails project with modest velocity rather than a commercial product.
- License: MIT
- Deployment: Docker, Heroku, or manual Ruby on Rails installation
- GitHub Stars: 49,000+ (July 2026)
- Best for: Developers wanting an agent-based system for web monitoring and event processing
Trigger.dev: Code-First TypeScript Jobs
Trigger.dev (Apache 2.0, 15,000+ stars) targets TypeScript teams building background jobs, durable workflows, and AI agents in code. Official self-hosting guides cover Docker Compose and Kubernetes. It is not a visual no-code builder; it competes with n8n only where the team is happy writing TypeScript.
- License: Apache 2.0
- Deployment: Self-hosted via Docker Compose or Kubernetes, or managed cloud
- Best for: TypeScript teams replacing queue infrastructure rather than visual workflows
Automatisch: Caution Advised as of 2026
Automatisch offers a Zapier-style trigger-and-action model under AGPL-3.0 (with .ee. files under an enterprise licence) and ships 92 app integrations in its repository (about 79 external-service connectors plus built-in utilities, July 2026). However, its hosted cloud was shut down (registration disabled and a shutdown alert added in December 2025) and the repository has had no meaningful commits since January 2026. Self-hosting still works, but teams should treat it as unmaintained until activity resumes.
- License: AGPL-3.0 with enterprise-file exceptions
- Status: Cloud discontinued; development stalled since January 2026
- Integrations: 92 apps in-repo (July 2026)
- Best for: Only teams comfortable adopting a currently dormant project
Comparison Table
| Tool | License | Approach | Integrations / Languages | Activity (Jul 2026) | Best For |
|---|---|---|---|---|---|
| ActivePieces | MIT core | Visual builder | 700+ pieces | Very active | n8n-like experience, permissive core |
| Windmill | AGPLv3 | Code-first | 12 languages | Very active | Developer teams |
| Kestra | Apache 2.0 | Declarative YAML | Plugin ecosystem | Very active | Data/infra orchestration |
| Huginn | MIT | Agent-based | Agent graph | Maintained (community) | Web monitoring |
| Trigger.dev | Apache 2.0 | Code-first (TS) | SDK-based | Very active | TypeScript background jobs |
| Automatisch | AGPL-3.0 | Trigger-action | 92 apps | Stalled since Jan 2026 | Not currently recommended |
Choosing Among Them
Teams wanting the closest visual experience to n8n with a permissive core licence should evaluate ActivePieces first. Engineering-heavy teams that prefer code get the broadest language coverage from Windmill, declarative orchestration from Kestra, or TypeScript-native jobs from Trigger.dev. Huginn remains dependable for agent-style web monitoring. Automatisch, previously an easy recommendation for simple setups, carries maintenance risk until its development resumes.
Related Questions
Related Tools
n8n
Workflow automation for technical teams
Workflow AutomationActivepieces
No-code workflow automation with self-hosting and AI-powered features
Workflow AutomationWindmill
Build internal tools, workflows, and scripts with a visual flow builder and auto-generated UIs
Workflow AutomationPipedream
Connect APIs, remarkably fast
Workflow AutomationRelated Rankings
Best Automation Platforms for AI Orchestration 2026
This ranking answers one question: how many real business applications can an AI agent act on out of the box? It evaluates nine platforms as of August 2026 on the reach they give an agent, not on the workflow logic they can express. That boundary is deliberate, because two neighbouring pages on this site answer different questions. Best Process Orchestration Platforms 2026 scores multi-step process control, error handling and state management. Best AI Agent Platforms 2026 scores building and hosting the agent itself. This page scores the layer between them: the connective tissue that lets an agent already built elsewhere reach the applications a business actually runs on. A platform that leads one of those pages can place low here, and two of them do. Scores derive from application and action catalogue counts, the exposure model each platform uses to publish those catalogues to an agent, setup effort, failure handling and cost per agent action. Every figure was retrieved from a vendor-owned surface on 11 August 2026 unless an earlier date is stated against it.
Best Durable Workflow Engines for Production in 2026
A ranked list of the best durable workflow engines for production deployments in 2026. Durable workflow engines persist execution state to a database so that long-running workflows survive process restarts, deployments, and infrastructure failures. The ranking covers Temporal, Prefect, Apache Airflow, Camunda, Windmill, and n8n. Tools were evaluated on production reliability, developer experience, scalability, open-source health, and documentation quality. The shortlist intentionally mixes code-first engines (Temporal, Prefect, Airflow) with hybrid visual platforms (Camunda, Windmill, n8n) to reflect how production teams actually choose workflow engines in 2026.
Dive Deeper
Client Portals vs Workflow Orchestration Platforms: What Changes When External Parties Act Inside a Process
What changes when a client or supplier has to act inside your process, not just watch it? This guide compares four client portals with four orchestration platforms on how outsiders get in, whether you pay for them and what the audit log records, from vendor sources read 14 and 15 September 2026.
Moxo vs Zapier in 2026: Human Approval Steps, External Participants and Pricing
Moxo and Zapier both put a person in front of an automated decision, from opposite ends: Moxo builds the process out of human steps and attaches AI, while Zapier pauses an automation for a reviewer through its Human in the Loop app. This guide compares approvers, rejection, AI approval, audit logs, governance and pricing, verified 14 and 15 September 2026.
Keystroke vs n8n in 2026: Agent-Built TypeScript vs the Visual Canvas
Keystroke, launched in July 2026 by Y Combinator W24 company Sprint Labs, is a code-first automation platform where AI coding agents write workflows as TypeScript in the user's repository. n8n, founded in 2019, is the most widely deployed source-available visual workflow platform, with 200,000+ users and a $2.5 billion valuation. This comparison covers the agent-authored versus canvas building models, durable execution, licensing (Elastic License 2.0 vs the Sustainable Use License), verified July 2026 pricing including Keystroke's usage metering, and the maturity gap between a days-old platform and an established ecosystem.