Self-hosting comes up whenever costs climb or data is sensitive. It is a real option, often presented as free when it merely moves the expense from one place to another.
Definition
Self-hosting means installing and running software on a server you control, instead of using the online version offered by the vendor.
You keep the same application, but you become responsible for the machine, the updates, the backups and the security.
The shortcut "self-hosted therefore free" is the most common and the most wrong. You do not pay a subscription, you pay for a server, storage, backups and human time. The question is not whether it is free, but whether the total is lower.
What you gain, what you take on
| What you gain | What you take on |
|---|---|
| Data does not leave | Updates and security patches |
| Fixed cost whatever the volume | Backups and restoration |
| No operation limits | Availability and monitoring |
| Independence from a vendor | The time of whoever looks after it |
The most underestimated line is the last. A server hosting your automations becomes a critical piece of your organisation. The day it stops responding, someone has to know what to do, and that someone is you.
When it is justified
When confidentiality is a real constraint, not a comfort. Health data, legal files, information under a non-disclosure agreement.
When volume makes the subscription absurd. Some platforms bill per operation: past a certain threshold, a fifty-euro server replaces a several-hundred-euro subscription.
When dependence becomes a risk. A vendor can change pricing, limits, or disappear. See Vendor lock-in.
Conversely, if you are starting out, if your volume is low and nobody with you is comfortable with a server, the online version remains the right choice by a wide margin.
A poorly maintained self-hosted service becomes a way in. Security patches are no longer applied by the vendor, they are applied by you. Without discipline on that point, self-hosting degrades your security instead of improving it.
Frequently asked questions
Do you need to be a system administrator?
Not necessarily at the start: ready-made images install in a few commands. Knowing how to diagnose a failure and restore a backup becomes essential as soon as the tool is critical.
Does it settle the GDPR question?
It simplifies part of the subject, since the data stays under your control. It does not remove the other obligations, and it makes you directly responsible for their security. See GDPR and AI.
Can you start online and migrate later?
That is the best approach: confirm the tool suits you, then move it when volume or confidentiality justifies it. Tools offering both modes, such as n8n, make that step simple.
How do you judge whether the maths works?
By comparing the total monthly cost, human time included, with your current subscription. Our n8n course covers that choice at the point where it genuinely arises, with both installation modes.