Technical · Guide 10 min read

Self-hosted n8n for business: VPS cost, security, backups and GDPR

“Self-hosted n8n is free” is true only about the licence. This article is about the rest — the server, the backups, the updates, and how much time it actually takes.

Self-hosted n8n for business: VPS cost, security, backups and GDPR
Author: Maksym Kamenchuk, Nexflow — Banská Bystrica Published Updated

The n8n Community Edition carries no licence fee when self-hosted — the source code is public and deploying it on your own server costs nothing.

Running it is not zero, though. Budget for a small VPS (on the order of single-digit to low tens of euros a month), time for updates and working backups. At low workflow volume, n8n Cloud often works out cheaper on total cost once you count your own time.

Self-hosting pays off when you have at least one of these three reasons: the data must not leave your infrastructure, the execution volume would be expensive in the cloud, or you need custom code and libraries the cloud does not allow. If you have none of them, do not buy self-hosting.

The real cost of self-hosting

An honest comparison has to include the items that do not appear on an invoice. Here is the list I use when designing:

ItemSelf-hostedn8n Cloud
Licence€0 (Community Edition)included in the subscription
Servera small VPS, single-digit to low tens of € / month€0
Domain and certificatedomain annually, HTTPS certificate free€0
Backupsstorage + setuphandled by the provider
Updatesyour time or a supplier'shandled by the provider
Monitoring and outagesyour timehandled by the provider
Subscription€0from €20 / month on annual billing (Starter, 2,500 executions)
Scaling as you growa bigger server, one-off worka higher plan

n8n Cloud prices per the official n8n.io price list as at 5 September 2026. VPS prices depend on the provider and configuration — check both before deciding.

A simple rule: if maintenance takes you an hour a month and your cost rate is €20/h, self-hosting carries a hidden cost of €20 a month — roughly what the lowest cloud plan costs. The difference only starts to show at larger volumes, where cloud plans grow and a server does not.

Self-hosted vs CloudSelf-hosted vs CloudItemSelf-hosted n8nCloudLicence€0 (Community Edition)in the subscriptionServera small VPS€0Backupsstorage + setuphandled by providerUpdatesyour time or a supplier'shandled by providerMonitoring and outagesyour timehandled by providerSubscription€0from €20 / monthn8n Cloud prices per n8n.io as at 5 September 2026.
Diagram. Process illustration: cost items compared, as in the article table.

What server you need

For ordinary company load — tens to low hundreds of executions a day, mostly API calls and text handling — a small VPS is enough. It gets more demanding in three cases:

Do not start with a big server “just in case”. It is more sensible to start small, watch the load and grow it when the numbers show it — with a VPS that is a matter of minutes.

Security — the minimum that is not optional

n8n has access to your systems and holds the credentials to them. That makes it a sensitive piece of infrastructure, not “another app”.

  1. HTTPS and your own domain. The interface must never be reachable over an unencrypted connection.
  2. Strong authentication. Access to the interface protected and restricted, ideally at the network or IP level too.
  3. Credentials in environment variables. Never hard-coded in a workflow. Whoever has access to a workflow should not automatically see passwords.
  4. Updates. n8n releases often and some releases address security. An un-updated instance is the biggest risk in the whole solution.
  5. A separate environment for testing. Do not debug on the production instance that has access to live data.

The most common mistake I see: an instance exposed to the internet with no access restriction, holding the credentials to every company system. That is not automation, that is a single point that opens everything at once.

Backups: what to back up and how to verify it

With n8n there are three things to back up, and each is different:

Workflows

They export as JSON. Ideally automatically and into versioned storage — then you know what changed and when.

Credentials

Stored encrypted and tied to the instance's encryption key. Without a backup of that key they are unusable after a restore.

Database and history

Execution records. Useful for tracing, but bulky — decide how long to keep them.

A backup you have never restored is not a backup. Try a restore on a clean server at least once and time how long it takes. That is the only way to find out you are not missing exactly that encryption key.

Three things to back upThree things to back up1 · Workflows• export as JSON• versioned storage2 · Credentials• stored encrypted• back up the encryption key3 · Database and history• execution records• decide how long to keep4 · Verify the restore• restore on a clean server• time how long it takes
Diagram. Process illustration: what to back up in n8n and how to verify it.

GDPR and where the data goes

Self-hosting is often sold as “the GDPR solution”. That is a simplification that can be dangerous, so more precisely:

Nexflow does not provide legal advice. This is a technical description of where data travels; assessing GDPR compliance belongs to your DPO or lawyer. I will gladly supply a technical description of the data flow for that.

When it is not worth self-hosting — choose the cloud

When there is nobody to administer a server. An un-updated instance is worse than a subscription.

When the volume is small. At tens of executions a day the cloud is simpler and often cheaper on total cost.

When nothing in the data is sensitive. Without that reason, self-hosting's main advantage is wasted.

When you need a result this week. The cloud runs immediately; preparing a server, HTTPS and backups takes time.

I recommend a pragmatic route: start in the cloud, confirm the automation makes sense, and move to self-hosting only when there is a substantive reason. Workflows export as JSON, so moving does not mean building again from scratch.

Frequently asked questions

Is self-hosted n8n really free?

The Community Edition licence is — the source code is public and deploying it costs nothing. Running it is not free: you need a server, backups and time for updates. At low volume the cloud usually works out cheaper on total cost once you count your own time.

What server do I need for n8n?

For ordinary company load — tens to low hundreds of executions a day, mostly API calls — a small VPS is enough. More capacity is needed for processing large files, for many concurrent executions, and for a production deployment with a separate database.

Is self-hosted n8n more secure?

It can be, but not automatically. It is more secure when it sits behind HTTPS, with restricted access, with credentials in environment variables and regularly updated. A neglected instance exposed to the internet is markedly riskier than the cloud.

What needs backing up in n8n?

Three things: the workflows (exported as JSON), the credentials together with the instance's encryption key, and the database with execution history. Without a backup of the encryption key, backed-up credentials are unusable after a restore — that is the most common nasty surprise.

Does self-hosting mean we are GDPR compliant?

No. It means the data does not pass through the automation platform provider's infrastructure. But if a workflow calls an external service, a language model for instance, the data goes there. GDPR compliance also depends on the lawfulness of the processing and on contractual relationships — that is for your DPO or lawyer to assess.

How does n8n count executions?

Per the official documentation, one execution is one run of a whole workflow regardless of the number of steps and the volume of data. That is why n8n works out better for long scenarios than tools that bill each module action separately.

Can we move from the cloud to self-hosting later?

Yes. Workflows export as JSON and import into your own instance; the credentials have to be set up again. That is why I recommend starting in the cloud and moving only when there is a substantive reason.

Who looks after the instance after deployment?

Either you or the supplier. What matters is that it is agreed in advance — the most common cause of trouble is an instance both sides believe the other one is updating.

Sources

Related services

Servicen8n automation ServiceBusiness process automation

Related articles

Comparisonn8n vs Make.com: which tool to choose PaybackHow to calculate the payback of automation

Not sure whether to go self-hosted?

Tell me what data would pass through the automation and roughly how many executions you expect. I will tell you whether self-hosting pays off — including an estimate of the monthly cost.

Get a free consultation →