Hosted automation platforms are the right default. You sign up, connect two apps, and it works. The case for running your own automation stack is not that it is easier — it is not — but that at a certain point hosted pricing and hosted constraints stop fitting.
This covers where that line actually sits, and what self-hosting costs you.
Where Hosted Automation Stops Fitting
Cost scales with volume in the wrong direction. Hosted platforms bill per task or per step. A workflow that runs ten thousand times a month gets expensive in a way that feels disproportionate, because the marginal cost to the provider is close to zero. If your volume is high and your per-task value is low, the maths stops working.
Your data passes through someone else. Customer records, contracts, anything under an NDA or a data residency requirement. Most providers handle this properly — but "handled properly" is a policy, and some industries require that the data never leave your infrastructure at all.
You need something the platform does not do. A custom transformation, an internal API, a specific retry behaviour. Hosted platforms give you an escape hatch (usually a code step), and you end up working around the tool rather than with it.
Zapier: The Right Default
Zapier has the largest app catalogue and the fastest path from idea to working automation. If your workflow touches mainstream SaaS tools and runs at moderate volume, this is where you should start and quite possibly where you should stay.
Strengths:
- Breadth of integrations — if a tool exists, it probably has a Zapier connector
- Zero maintenance — no servers, no updates, no on-call
- Fast to build — most workflows take minutes
Best fit: moderate volume, mainstream tools, no data residency constraint, no dedicated engineering time.
n8n: Self-Hosted, Source-Available
n8n is a workflow automation tool you run yourself — on your own server, your own data, with your own resource limits. It is source-available with a fair-code licence, and the self-hosted version is free.
Strengths:
- No per-task billing when self-hosted — you pay for infrastructure instead
- Data stays on your infrastructure, which settles residency and NDA questions outright
- Real code steps — write JavaScript when the built-in nodes are not enough
- Complex branching — loops, error handling and conditionals that hosted builders handle awkwardly
Best fit: high volume, sensitive data, engineering capacity, or workflows that outgrew a hosted builder.
What Self-Hosting Actually Costs
Do not decide this on licence fees alone. The real costs are:
- Setup: a server, a database, TLS, backups, and somewhere to run it
- Maintenance: version upgrades, which automation tools ship frequently
- Reliability: hosted platforms have redundancy you will have to build yourself
- On-call: when a workflow fails at 3am, that is now your problem
A useful test: if nobody on your team would be comfortable debugging a failing cron job, self-hosting will cost you more than it saves, regardless of volume.
How to Decide
| Situation | Choose |
|---|---|
| Moderate volume, mainstream apps | Zapier |
| High volume, low value per task | n8n |
| Data must not leave your infrastructure | n8n |
| No engineering time available | Zapier |
| Workflow needs custom logic or branching | n8n |
A common and sensible pattern: run on a hosted platform until a specific workflow becomes expensive or constrained, then move that workflow to self-hosted. There is no need to migrate everything at once, and the two can coexist.
Where Agents Fit
Worth separating two things that get conflated. Workflow automation runs a defined sequence reliably: when X happens, do Y. An agent decides what to do when the path is not known in advance.
If your task is deterministic, automation is the right tool and cheaper. If you cannot specify the steps — triage this inbox, research this question — you want something like OpenClaw, which can run on the same infrastructure as your self-hosted workflows.
More options are in our Productivity category.
Frequently Asked Questions
Is self-hosting actually cheaper?
At low volume, no — infrastructure and maintenance cost more than a hosted subscription. The crossover comes with volume: hosted platforms bill per task, and self-hosted infrastructure does not.
How much technical skill does n8n need?
Less than writing code, more than using Zapier. You will be comfortable if you can run a Docker container and read logs. Expect to spend an afternoon on setup and an hour a month on maintenance.
Can I move workflows between the two?
Not automatically — they are different tools with different node models. Most people rebuild the workflow in the new tool, which is why migrating one high-volume workflow at a time is the practical approach.
What happens when a self-hosted workflow fails?
You find out because you set up alerting, and you fix it because nobody else will. Hosted platforms handle retries, alerting and visibility for you; self-hosted means building that yourself.
Do I need self-hosting for data compliance?
Depends on your obligation. Some frameworks require that regulated data never leave infrastructure you control, which only self-hosting satisfies. Others accept a vetted processor, which most hosted platforms are.