Lorixen.
EN

Self-Hosting n8n or Paying for Cloud: A Small-Business Cost Check

Short answer: For most small businesses the paid cloud plan costs less overall, because the expensive part of self-hosting is not the server. It is the hours spent on updates, backups, access control and night-time fixes. Self-hosting makes sense when someone on your team already runs servers comfortably, when customer data must stay in a particular location, or when your workflow volume would make a cloud plan expensive. Work out the monthly total with your own hourly figure before you decide, and include the cost of a failure that nobody notices until Monday.

What self-hosting actually includes

Running n8n yourself is more than starting one container. A reliable setup needs a server with enough memory for your workflows, a domain name, an HTTPS certificate, a database for workflow and execution data, a reverse proxy in front of the editor, scheduled backups stored somewhere other than the server, and monitoring that tells you when the service stops. Each item is simple on its own. Together they become a small system that needs care.

The official hosting documentation covers the supported options. Read it before you choose a host, because the defaults for storage and the encryption settings affect how you back things up later.

A monthly cost comparison

The figures below are invented examples to show the shape of the calculation. Replace them with your own quotes and your own hourly rate.

Cost item Self-hosted (example) Cloud plan (example)
Server rental 12 EUR Included
Backup storage 3 EUR Included
Domain and certificate 1 EUR (certificate issued free) Included
Subscription None 50 EUR
Admin time, 3 hours at 40 EUR 120 EUR Under 1 hour, about 40 EUR
Total 136 EUR 90 EUR

If your admin time is only 20 minutes a month, the self-hosted total falls to about 29 EUR, and the picture changes. The decision is really about hours. Track how long the last three upgrades, restores or incidents took before you trust any estimate. Most owners underestimate the time by a wide margin, because they count the first setup and forget the maintenance.

The duties you take on

Self-hosting moves four duties onto your side:

  • Upgrades. n8n releases often. Read the release notes, test a copy of your workflows on a staging instance, and then update production. Skipping updates for a year makes the jump harder and leaves security fixes unapplied.
  • Backups. Back up the database and the encryption key together. Credentials are stored encrypted, so a database backup without the key cannot restore them. Test a restore on a second machine at least once a quarter, because an untested backup is only a hope.
  • Access control. Do not expose the editor to the open internet without authentication and access rules. Keep secrets out of workflow nodes and use the credentials store.
  • Monitoring. A workflow that fails at 02:00 can sit unnoticed until a customer complains. Set up alerts for failed executions and for the service going down.

Cloud plans take most of these off your desk. You still need to design good workflows, handle your own credentials carefully and watch the failure alerts, but you do not patch the operating system or restore the database.

Who should pick which

Choose the cloud plan if:

  1. Nobody in the business is comfortable with Linux, Docker and certificates.
  2. Your automations support sales, bookings or customer messages, where downtime costs money the same day.
  3. You want a predictable monthly figure and a vendor who handles incidents.

Consider self-hosting if:

  1. A developer or systems administrator already runs your servers and has spare time.
  2. Your data rules require storage in a specific country or on your own hardware.
  3. You run very large volumes of executions and have measured that the cloud cost is higher than the server.

Many teams start in the cloud, then move to self-hosting once they have a stable workflow list and a person who owns it.

Steps to decide

  1. List your active workflows and note which ones touch customer data or money.
  2. Count executions per month for the last quarter, so the volume figure is real.
  3. Write down any data location requirements from your contracts or your privacy policy.
  4. Name the person who will receive the failure alert at night and confirm they accept the job.
  5. Run the cloud trial for one month, or a free test on a sample workflow, before you commit.
  6. If you choose self-hosting, rehearse a full restore on a spare server before the first real workflow goes live.

Moving later

Moving from cloud to self-hosted is possible, and so is the reverse. Export your workflows, then move credentials deliberately. Credentials are tied to the encryption key, so you must bring that key across securely, or re-enter the credentials on the new instance. Check the official documentation for the current export and import steps, because the process has changed between versions. Keep a short written list of which workflows depend on which credentials, since that list tells you in advance how much re-entry work the move will create, and it doubles as a checklist for the cut-over day.

FAQ

Is self-hosting n8n free?

The software is available to run yourself, but the server, domain, backups and your time are real costs. "Free" describes the licence, not the total monthly spend.

Can we switch from cloud to self-hosted later?

Yes. Plan the move around the credentials, since they must be re-encrypted or re-entered. Run both versions in parallel for a short period and compare execution results before you switch the production triggers.

What happens if we lose the encryption key?

The stored credentials cannot be decrypted, so workflows that rely on them stop working until each credential is entered again. Keep the key in a password manager or secrets vault, with two people able to reach it.

How often should a self-hosted instance be updated?

Update when you have read the release notes and tested your key workflows on a copy. Waiting for a convenient month is fine. Waiting for years is not, because security fixes stop reaching you.

If you want an honest comparison based on your own workflows and hours, tell us what you run and how much time your team can give to upkeep, and we will work through it with you: contact us here.

Sources

WhatsAppBook a call