What self-hosting really changes
Moving to n8n is not a choice of tool, it is a choice of operation. You no longer have a per-operation invoice, you have a server to look after, updates to apply and monitoring to ensure. It is a transfer of cost, not its removal.
When it is worth it
Three situations justify it. A high, regular volume, where a hosted platform’s per-operation billing ends up exceeding the cost of a server. Regulated or sensitive data that must not pass through a third-party service. And a need for processing consumer platforms do not allow.
When it is not worth it
If you have five simple automations and nobody technical. You will pay in time what you save on the subscription, and the first incident will cost more than the year of savings. We will say so rather than sell you a bigger project.
What we put in place
An instance on your infrastructure or on ours, depending on your policy. Versioned flows, so we can roll back. Monitoring that warns a human, not merely a log nobody opens. And a written recovery procedure, tested at least once.
The question that decides
Who looks after it in a year. A self-hosted instance with no identified owner ends up with security updates overdue, which is a far more concrete risk than the invoice you wanted to avoid.
