Self-hosting an automation tool looks like a cost decision and behaves like an operations decision. The invoice stops growing with usage, and something else starts growing instead: the work of keeping a service running that other processes depend on.
That trade is worth it for some teams and a trap for others. This page compares n8n, Activepieces, and Windmill as self-hosted options, including the maintenance each one actually demands.
The short answer
n8n is the visual-first option with the largest connector surface. Activepieces is the cleanest open-source Zapier analogue, MIT-licensed and simpler to reason about. Windmill is code-first: functions become scheduled jobs and endpoints, with less visual canvas.
What self-hosting actually requires
| Requirement | What it means in practice |
|---|---|
| A host | A small VPS is usually enough; memory matters more than CPU |
| A database | Postgres for n8n and Windmill; SQLite works for small installs |
| Backups | Database plus the file store that holds credentials and executions |
| Upgrades | Pinning versions and reading release notes before updating |
| Monitoring | Something that notices when a scheduled workflow stops firing |
The last row is the one people skip, and it is the failure that hurts: a backup job that silently stopped three weeks ago is worse than not having the job.
n8n: breadth and the canvas
n8n's strength is the node library and the visual canvas, which makes it a direct replacement for a Zapier-shaped process. Self-hosting it means a Postgres database, a queue for long executions, and a backup routine that includes the encryption key used for credentials.
That key detail is easy to miss. Restoring a database without it leaves you with workflows and unusable credentials.
Activepieces: the clean analogue
Activepieces is MIT-licensed and smaller in scope, which makes it easier to read and deploy. The connector list is shorter than n8n's, so the question is whether your important apps are covered.
For a team that needs a handful of standard connectors and values a simple codebase over breadth, it is the least surprising option. The trade is exactly that: fewer pieces, fewer surprises, fewer integrations.
Windmill: code as the unit
Windmill starts from scripts: a Python or TypeScript function becomes a scheduled job, a workflow step, or an internal app. That suits teams whose automation is already code and who want a UI, retries, and secrets management without adopting a SaaS.
It is the least Zapier-like of the three. If nobody on the team writes code, the abstractions will not be worth their overhead.
The migration path
Moving from a hosted tool to a self-hosted one is not automatic: workflows are not portable, and each tool's authentication model differs. The practical sequence is to run both for a month, move the highest-volume workflow first, and keep the hosted tool for the long-tail connectors.
That period is also when you learn whether the maintenance burden is real for your team. A staging install that nobody touches is not evidence; a production workflow that has to stay up is.
The security surface
Self-hosting moves responsibility for updates and secrets to you. That means a defined answer for three questions: who can access the admin UI, where credentials are encrypted at rest, and how a compromised instance is contained.
A reverse proxy with authentication in front of the UI is the minimum. The default install assumes a trusted network, and a public IP is not that.
When not to self-host
If the workflow is small, the team has no operations capacity, or the automation touches a regulated system with its own audit requirements, a hosted plan is usually the better answer. The invoice is visible and the maintenance is someone else's job.
Self-hosting pays off when volume is high, logic is complex, or data cannot leave your infrastructure. Those are real reasons; "it is cheaper" alone usually is not.
Frequently asked questions
How much does a self-hosted n8n cost to run? A small VPS plus backups, plus the hours someone spends maintaining it. The hours are the part to estimate honestly.
Can I use these for customer-facing automation? Yes, with a queue, monitoring, and a rollback plan. A single instance with no monitoring is fine for internal jobs, not for customers.
Which is easiest to start? Activepieces and n8n both start from a container; Windmill rewards teams already comfortable with code. See automation tools for hosted alternatives.
Last checked: 9 November 2026.
Related: n8n vs Zapier vs Make, AI workflow builders, and automation tools.