A8gent
GlossaryAutomation mechanics

What is self-hosting?

Also called: self-hosted, on-premise automation

Self-hosting means running automation software on infrastructure you control rather than using the vendor's cloud, so your data and credentials stay inside your own environment.

Written by A8gent
Contents
  1. At a glance
  2. What self-hosting means here
  3. What it genuinely costs
  4. When it is the right call
  5. What you should know
  6. FAQ
  7. Related terms

At a glance

Category
Automation mechanics
Supported by
n8n, Windmill, Activepieces and most code frameworks; not Zapier or Make
Real cost
Updates, backups with tested restores, monitoring, TLS, and someone on call
Strongest reason
Contractual or regulatory requirements that data stay in your infrastructure
Important caveat
Calling a hosted model API still sends data out, even from a self-hosted platform
Check
The licence - fair-code and source-available terms restrict hosting for third parties

What self-hosting means here

Self-hosting means you run the automation platform yourself - on a virtual server, in a container, or on hardware in your office - instead of using the vendor's hosted service. n8n, Windmill, Activepieces and several agent frameworks support it; Zapier and Make do not. The workflows and the interface are the same; what changes is who operates the thing.

The decision is usually framed as cost and is usually actually about control. Self-hosting means credentials, execution logs and the customer data flowing through your workflows all stay inside infrastructure you own, which is the deciding factor for anyone with a data residency commitment or a client contract that forbids third-party processing.

What it genuinely costs

The server is the cheap part - a modest virtual machine runs a small business's automation comfortably. The real costs are operational: updates and security patches, backups and a tested restore, monitoring and alerting so you find out the service is down before your customers do, TLS certificates, and someone competent being available when it breaks at an inconvenient time.

That last item is the one that decides it. A hosted platform's uptime is somebody's full-time job. Yours is somebody's evening. If nobody on the team can confidently restore the service from a backup, self-hosting is a saving on the invoice and a liability everywhere else. Where volume is genuinely high, though, the arithmetic can flip hard: per-execution pricing at scale buys a lot of virtual machine.

When it is the right call

Four situations. Regulatory or contractual requirements that customer data not leave your infrastructure. Volume high enough that cloud billing exceeds the fully loaded cost of running it. Integrations with internal systems that have no public endpoint, where a self-hosted instance inside the network is far simpler than opening a tunnel. And a genuine need for customisation the hosted product does not allow.

Note that self-hosting the orchestrator does not make everything local. If your workflows call a hosted model API, customer text still leaves your network on every call - see zero data retention. Self-hosting the platform and using a hosted model is a common and perfectly sensible arrangement, but be accurate about it when answering a client's security questionnaire.

What you should know

Check the licence. Several platforms use a source-available or fair-code licence that permits internal self-hosting but restricts offering the product as a service to others, which matters if you are an agency planning to host on behalf of clients. Read the specific terms rather than assuming open source, because the categories are genuinely different.

Start hosted if you are unsure. Prove the automation is worth having on the vendor's cloud, then migrate to self-hosted if cost or compliance demands it. Doing it in that order means the infrastructure work is justified by a system you already know is valuable, rather than being the reason the project stalled in month one.

Self-hosting FAQ

What does self-hosting an automation platform mean?

Running the software on your own server or container instead of using the vendor's cloud. The workflows and interface are the same; the difference is that credentials, logs and the data passing through stay in infrastructure you control, and you are responsible for keeping it running.

Is self-hosting cheaper?

On the invoice, usually. In total, only at meaningful volume, because you take on updates, backups, monitoring and being available when it breaks. At high execution volume the arithmetic flips decisively, since per-run cloud pricing at scale buys a lot of virtual machine.

Does self-hosting keep my data private?

It keeps workflow data and credentials inside your infrastructure, which is often the point. It does not make everything local: if your workflow calls a hosted model API, that text still leaves your network. Be precise about this when answering a client security questionnaire.

What do I actually have to maintain?

Software updates and security patches, backups with a restore you have actually tested, monitoring and alerting for downtime, TLS certificates, and the availability of someone who can fix it. The server itself is the cheapest item on that list by a wide margin.

Can I self-host Zapier or Make?

No, both are cloud-only. If self-hosting is a requirement, the realistic options are n8n, Windmill, Activepieces, or building on a code framework you deploy yourself. That requirement alone frequently decides the platform choice.

Is n8n open source?

It uses a fair-code licence rather than a standard open-source one. Internal self-hosting is permitted, but there are restrictions around offering it as a service to others, which matters for agencies planning to host on clients' behalf. Read the current licence terms directly rather than assuming.

Primary source

n8n - self-hosting and scaling documentation

Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.

Want this built rather than explained?

Knowing what self-hosting means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.