UK managed hosting · £1 a day + VAT · old websites welcome01623 650333 · Client login
Order now

Self-Hosted n8n Hosting UK

dijitul hosts self-hosted n8n for UK businesses on a managed VPS, quoted to your workflows. We run n8n in Docker with PostgreSQL, HTTPS webhooks behind a reverse proxy, queue mode with Redis and workers when volumes grow, and backups that include the database and the encryption key. Your workflows and credentials stay on your own server.

Updated 2026-11-12 · by the dijihost team · reviewed by , founder, building websites since 1996

Key facts

  • Quoted per instance on a managed VPS or dedicated server
  • Runs the official n8nio/n8n Docker image, version pinned and updated by us
  • PostgreSQL database: n8n supports versions 16, 17 and 18 per its docs
  • Queue mode with Redis, workers and optional webhook processors
  • HTTPS webhooks through Nginx and Cloudflare
  • Backups cover the database and the N8N_ENCRYPTION_KEY
  • n8n is licensed under its Sustainable Use License, not an OSI open-source licence

What self-hosted n8n needs

n8n is a workflow automation tool: it connects apps, APIs and AI models, and runs jobs on triggers, schedules and webhooks. n8n's own documentation recommends Docker for most self-hosting, and says self-hosting needs knowledge of servers, containers, security and n8n configuration. That is the part we take on.

  • Docker: the official n8nio/n8n image, pinned to a tested version rather than "latest".
  • PostgreSQL instead of the default SQLite. n8n's docs list PostgreSQL 17 and 18, plus 16 for compatibility, as supported.
  • A reverse proxy (Nginx) with SSL, so the editor and webhooks are only reachable over HTTPS.
  • A persistent data volume for /home/node/.n8n, which holds the credential encryption key.
  • Monitoring of the containers, disk space and failed executions.

Queue mode: when one process is not enough

By default n8n runs everything in one process. When you have many workflows, heavy AI calls or bursts of webhooks, n8n's queue mode splits the work:

  1. The main instance serves the editor and receives triggers.
  2. Redis holds the queue of executions.
  3. Workers (started with n8n worker) pick up executions. n8n's docs give a default concurrency of 10 per worker.
  4. Optional webhook processors (n8n webhook) take incoming webhook traffic off the main instance.

Queue mode needs PostgreSQL, because n8n says running it over SQLite is not supported. Every worker must share the main instance's N8N_ENCRYPTION_KEY, and binary data must go to S3-compatible storage rather than the local filesystem. We size the VPS for the number of workers you need, so you are not paying for capacity you will not use.

Webhooks, HTTPS and security

  • The public webhook address is set with N8N_WEBHOOK_URL (n8n 2.30.0 and later; older versions use WEBHOOK_URL), so the URLs n8n shows match your real domain.
  • The editor sits behind HTTPS and can be limited to your office IP addresses or a VPN.
  • Cloudflare in front filters junk traffic before it reaches your webhooks.
  • API keys for the services your workflows call live in n8n's encrypted credential store, never in workflow JSON shared by email.
  • The server is firewalled, patched and watched by us, as on any managed VPS.

Backups that can actually restore n8n

n8n's backup guidance says to keep three things: the .n8n folder (it contains the encryption key), the PostgreSQL database, and any external storage or custom nodes. The CLI exports (n8n export:workflow --backup and n8n export:credentials --backup) are useful, but n8n's docs say they contain workflows and credentials only, not users, execution history, variables or the encryption key. Lose the key and your saved credentials cannot be decrypted. We back up the database and the key together, keep the CLI exports as a second copy, and test a restore before you rely on it. See website backups for how we approach backups generally.

Licence terms: read this before you build a product on n8n

n8n is "fair-code", not open source in the OSI sense. Its LICENSE.md on GitHub says most of the code is under the Sustainable Use License, which allows use or modification "only for your own internal business purposes or for non-commercial or personal use". Files with ".ee." in the name are under the separate n8n Enterprise License. Running n8n for your own company's automations fits the first case. Selling n8n itself as a service to your customers is a different matter, and you should check the licence and talk to n8n before doing it.

n8n's docs also list features that need a paid Business or Enterprise licence key when self-hosted, including SSO, environments, external secrets, log streaming and multi-main high availability. Queue mode and standard logging are in the free Community edition.

Sources, checked 11 November 2026: n8n Docker docs; n8n queue mode; n8n supported databases; n8n backup and restore; n8n editions; n8n LICENSE.md.

Frequently asked questions

Can I self-host n8n in the UK?

Yes. dijitul runs self-hosted n8n on managed UK servers using the official Docker image, PostgreSQL and HTTPS webhooks, and adds queue mode with Redis and workers when you need it. It is quoted per instance after we look at your workflows.

Is n8n free to self-host?

The Community edition is free to self-host under n8n's Sustainable Use License, which allows use for your own internal business purposes. Some features, such as SSO, environments and log streaming, need a paid Business or Enterprise licence key. You still pay for the server it runs on.

Does n8n need PostgreSQL?

Not for a small instance, because n8n uses SQLite by default. For production we use PostgreSQL, and n8n's docs say queue mode is not supported on SQLite. n8n currently lists PostgreSQL 16, 17 and 18 as supported versions.

What is n8n queue mode?

Queue mode splits n8n into a main instance, a Redis queue and one or more workers that run executions, with optional webhook processors. It lets n8n handle more workflows at once. Every process must share the same encryption key and use PostgreSQL.

What should I back up for n8n?

Back up the PostgreSQL database and the .n8n folder, which holds the credential encryption key, plus any external storage or custom nodes. n8n's CLI backup exports contain workflows and credentials only, so on their own they cannot fully restore an instance.

Can I offer n8n to my own clients?

Check the licence first. n8n's Sustainable Use License limits use to your own internal business purposes or non-commercial use. Hosting n8n for your own business is fine; reselling n8n as a service usually needs an agreement with n8n. We can host either once the licensing is clear.

Related

Tell us what you need to run

We spec it, build it, host it and look after it. Clear quote, no jargon.

Call usOrder £1/day