n8n self-hosted automation costs approximately £20 per month in server fees compared to £250-£940 per month for equivalent Make or Zapier plans at 50,000 automation tasks. n8n is open-source and runs on a Linux virtual private server, keeping all your workflow data on UK or EU servers with no third-party data processors - a significant advantage for UK healthcare, legal and financial services businesses with data residency requirements. The trade-off is technical complexity: self-hosted n8n requires Docker setup, Linux comfort and ongoing server maintenance. For businesses that cannot manage infrastructure themselves, n8n cloud or a managed hosting provider closes this gap at £20-£50 per month extra.
Last updated: 18 May 2026
Published 18 May 2026n8n is an open-source workflow automation platform that lets you connect any application to any other application using a visual node-based editor. Unlike Zapier and Make, you can run n8n entirely on your own servers - meaning your data never leaves your infrastructure, you pay only for the server rather than a per-task subscription, and you retain full control over every aspect of your automation environment.
n8n was founded in Berlin in 2019 by Jan Oberhauser and has grown to become the leading open-source automation alternative to Zapier and Make. The platform now offers more than 350 native integrations - covering everything from Salesforce, HubSpot and Stripe to Slack, Gmail and Notion - plus an unlimited HTTP request node that allows connection to any REST or GraphQL API without a dedicated integration. The community has contributed hundreds of additional nodes, and the n8n team releases major updates roughly every four to six weeks.
The visual workflow editor works on a canvas where each step in your automation is represented as a node. You drag nodes onto the canvas, connect them with arrows and configure each node with the relevant credentials and logic. Conditional branching, loops, error handling and sub-workflows are all first-class features. This makes n8n genuinely comparable to Make in terms of complexity and expressiveness, while being considerably more powerful than Zapier's linear trigger-action model.
What distinguishes n8n from all cloud competitors is the self-hosted deployment option. You provision a Linux virtual private server - a virtual machine running Ubuntu on infrastructure from providers such as Hetzner, DigitalOcean, Vultr or AWS - install Docker and Docker Compose, and run n8n as a containerised service. Your workflows, credentials and execution logs are stored in a database (SQLite for single-instance setups, PostgreSQL for production scale) that lives entirely on your server. n8n's servers never see your data.
For UK businesses that have reached a meaningful automation volume or operate in regulated sectors, this architecture changes the compliance calculus entirely. There is no Standard Contractual Clause paperwork for US data transfers, no data processing agreement to negotiate with a cloud vendor, and no question about where patient or client data is processed. We cover the GDPR implications in detail in section three, but the architectural point is worth stating clearly upfront: self-hosted n8n is a fundamentally different data model from cloud automation platforms.
One area where n8n has moved ahead of Zapier and Make in 2025 and 2026 is native AI integration. n8n ships with built-in nodes for GPT-4o and GPT-4.5, Claude 4, Gemini 2.5 and LangChain, allowing you to build AI agents and multi-step AI workflows directly inside the visual editor without custom code. Zapier offers AI features through its Zapier AI add-on, and Make offers HTTP-based AI connections, but neither matches n8n's native LangChain integration for building sophisticated agentic workflows that chain multiple AI calls, maintain memory between steps and use tools dynamically.
| Feature | n8n self-hosted | n8n cloud | Zapier | Make |
|---|---|---|---|---|
| Monthly cost at 50k tasks | ~£20 (server only) | ~£50 | ~£940 | ~£250 |
| Data location | Your servers (UK/EU) | n8n EU servers | US-based | EU or US |
| Self-hosted option | Yes (core feature) | No | No | No |
| AI nodes native | GPT-4o/4.5, Claude 4, LangChain | Same | Add-on only | HTTP nodes only |
| Integration count | 350+ native, unlimited custom | Same | 6,000+ | 1,500+ |
| Technical skill required | Linux + Docker | None | None | Low |
| Support model | Community forum + paid plans | Email support | Chat + phone | Chat support |
The table above summarises the key trade-offs. The self-hosted option delivers a dramatic cost advantage and complete data sovereignty at the cost of requiring server management capability. The following section quantifies exactly when those cost savings make the switch financially worthwhile.
n8n self-hosted becomes financially superior to Make at around 10,000 tasks per month and beats Zapier at virtually any meaningful automation volume. The exact crossover point depends on how many operations your workflows consume per task, but the cost trajectory is decisive: n8n's server cost is flat regardless of task volume, while Zapier and Make charge per operation or task bundle.
Let us work through the numbers in detail. At 50,000 automation tasks per month - a typical volume for a 20-person business running five to ten automations daily across CRM updates, invoice processing, lead routing, Slack notifications and reporting pipelines - the cost comparison breaks down as follows.
Zapier's Professional plan at 50,000 tasks costs approximately £940 per month when billed monthly (£735 annually). Make's Team plan at 50,000 operations costs approximately £250 per month. A self-hosted n8n instance on a Hetzner CX22 VPS (2 vCPU, 4GB RAM, based in Helsinki with EU data residency) costs £8.29 per month plus approximately £10-12 per month for a managed PostgreSQL database or backup service - a total of approximately £20 per month. Over 12 months that represents a saving of £11,040 versus Zapier and £2,760 versus Make.
The saving compounds at higher volumes because n8n's server cost barely changes. A business at 200,000 tasks per month would need Zapier's Business plan at approximately £2,500 per month or Make's equivalent at £700-£900 per month. That same n8n instance on a slightly larger server (£15-£25 per month) handles 200,000 tasks without a pricing tier change.
For established UK businesses considering an n8n migration, Softomate typically builds self-hosted n8n infrastructure as part of an automation project costing £4,000-£15,000, depending on the number of workflows being migrated and built from scratch. That build cost is typically recovered within six to twelve months purely from the reduction in Zapier or Make subscriptions, before counting productivity gains from more sophisticated workflow logic.
There is one nuance worth flagging on the Make comparison: Make's free tier (1,000 operations/month) and Starter plan (£7/month for 10,000 operations) make Make the rational choice for very low-volume businesses. n8n self-hosted is overkill if you are running two or three simple automations. The crossover becomes compelling once you exceed 10,000-15,000 monthly tasks or once you need AI workflow nodes, complex branching or regulated-data handling.
| Monthly tasks | Make cost | n8n self-hosted cost | Monthly saving vs Make | Annual saving |
|---|---|---|---|---|
| 5,000 | ~£16 | ~£20 | -£4 (n8n costs more) | -£48 |
| 10,000 | ~£34 | ~£20 | +£14 | +£168 |
| 25,000 | ~£90 | ~£20 | +£70 | +£840 |
| 50,000 | ~£250 | ~£20 | +£230 | +£2,760 |
| 100,000 | ~£470 | ~£22 | +£448 | +£5,376 |
| 200,000 | ~£850 | ~£25 | +£825 | +£9,900 |
The breakeven point against Make sits clearly between 5,000 and 10,000 monthly tasks. Against Zapier, n8n self-hosted is cheaper from the very first paid Zapier tier. If your business is currently on Zapier's Starter plan (2,000 tasks/month at approximately £22/month) the numbers are marginal, but any business on Zapier's Professional plan or above - typically 20,000 tasks or more - is paying substantially more than they would with self-hosted n8n, before considering the compliance and data sovereignty benefits we explore next.
When you run an automation through Zapier or Make, the data you are processing - customer records, invoice details, patient information, legal case notes, financial transactions - passes through that company's servers. Under UK GDPR, that makes Zapier or Make a data processor, and your organisation a data controller. You need a Data Processing Agreement in place, and if that processor stores data in the United States (as Zapier does by default), you also need to rely on a transfer mechanism such as Standard Contractual Clauses or the UK-US Data Bridge. With self-hosted n8n, none of this applies: n8n the company never processes your data at all.
This distinction matters enormously for UK regulated industries. The Information Commissioner's Office (ICO) guidance on accountability and governance makes clear that data controllers are responsible for ensuring processors provide sufficient guarantees about technical and organisational measures. For a GP surgery automating patient appointment reminders, a law firm routing client documents through a workflow, or a financial adviser syncing client portfolio data between systems, the question of where that data is processed is not a procurement detail - it is a regulatory obligation.
Healthcare organisations regulated by the Care Quality Commission (CQC) and subject to NHS Data Security and Protection Toolkit requirements face specific restrictions on where patient data can reside and which processors can handle it. The NHS DSPT explicitly requires that data processing occurs within the UK or European Economic Area by default, with additional safeguards for any transfers beyond those borders. A self-hosted n8n instance running on a UK-based server satisfies this requirement without the need for additional contractual arrangements.
Solicitors and legal service businesses regulated by the Solicitors Regulation Authority (SRA) handle privileged communications and confidential client data. The SRA's Standards and Regulations require solicitors to keep client information confidential and to use appropriate technical controls. Routing client case data through a US-based automation platform introduces regulatory exposure that many practice managers would prefer to avoid altogether. Self-hosted n8n on a UK VPS eliminates that exposure.
Financial services firms regulated by the Financial Conduct Authority (FCA) face similar data handling obligations, particularly around client financial data, know-your-customer records and transaction monitoring. The FCA's operational resilience framework increasingly requires firms to understand and document data flows to third-party systems - and to demonstrate that those third-party systems meet equivalent standards. Keeping automation infrastructure in-house simplifies that mapping considerably.
At Softomate, when we assess automation requirements for clients in healthcare, legal and financial services, data residency is always the first question. For the majority of UK regulated businesses we work with, self-hosted n8n on a Hetzner Helsinki or DigitalOcean London server resolves the compliance question cleanly and without ongoing contractual overhead.
| GDPR consideration | Zapier/Make (cloud) | n8n self-hosted |
|---|---|---|
| Third-party DPA required | Yes - mandatory | No - no third-party processor |
| Data stays in UK/EU by default | Zapier: No (US default). Make EU: option available | Yes - you choose the server location |
| SCCs required for US transfer | Zapier: Yes. Make EU: No | No - no transfer occurs |
| ICO recommended for regulated industries | Requires additional safeguards | Clean - no third-party processor |
| Right to erasure complexity | Must request deletion from processor and verify | Delete from your own database directly |
One additional compliance benefit worth noting is the right to erasure (Article 17 UK GDPR). When a data subject requests erasure and their data has passed through a cloud automation platform, you must request deletion from that processor and verify it has been carried out. With self-hosted n8n, execution logs containing personal data are stored in your own database - deletion is direct, auditable and fully within your control. For businesses handling high volumes of data subject requests, this removes a recurring compliance friction point.
Setting up a self-hosted n8n instance requires Linux command line familiarity, comfort with Docker and basic knowledge of DNS and SSL configuration. The process takes approximately two to four hours for a developer who has done it before, or a full day for someone working through it for the first time. Here is the complete step-by-step process we follow at Softomate when provisioning n8n infrastructure for clients.
Step 1: Choose a VPS provider with UK or EU servers
We recommend Hetzner Cloud as the default choice for UK businesses. Hetzner's Helsinki data centre sits within the EU (EEA), meaning GDPR Article 44 restrictions on international transfers do not apply. A CX22 instance (2 vCPU, 4GB RAM, 40GB SSD) costs £8.29 per month - more than sufficient for most small and medium business n8n deployments. DigitalOcean's London region is a good alternative at approximately £12 per month for equivalent specs, with the advantage of UK data residency if your DPA or IT security policy requires servers specifically on UK soil. AWS London (eu-west-2) and Azure UK South are also viable for organisations that need enterprise cloud infrastructure, though costs are higher and the setup is more complex.
Step 2: Provision Ubuntu 22.04 LTS server
Create a new server instance with Ubuntu 22.04 LTS (Long Term Support). Minimum specifications for a reliable n8n deployment are 2GB RAM and 20GB storage, though 4GB RAM is recommended for production workloads with multiple concurrent workflow executions. Enable SSH key authentication and disable password login in /etc/ssh/sshd_config before exposing the server to the internet. Create a non-root sudo user for day-to-day operations.
Step 3: Install Docker and Docker Compose
Install Docker CE (Community Edition) using the official Docker repository rather than the Ubuntu default package, which is typically several versions behind. Install Docker Compose v2 as a Docker plugin. Add your non-root user to the docker group so you can run Docker commands without sudo. Test the installation with docker run hello-world before proceeding.
Step 4: Create the n8n docker-compose.yml with environment variables
Create a directory at /opt/n8n and create a docker-compose.yml file. Key environment variables to configure include: GENERIC_TIMEZONE=Europe/London (ensures workflow schedules run on UK time), N8N_BASIC_AUTH_ACTIVE=true with a strong username and password for initial access, N8N_HOST set to your subdomain (for example n8n.yourdomain.co.uk), N8N_PROTOCOL=https, WEBHOOK_URL set to your full domain URL, and N8N_LOG_LEVEL=info. For production deployments we also recommend switching from the default SQLite to PostgreSQL for better performance and reliability under concurrent load.
Step 5: Configure SSL certificate via Let's Encrypt and Nginx reverse proxy
Install Nginx and Certbot on the server. Configure Nginx as a reverse proxy that forwards HTTPS traffic to n8n's internal port (5678 by default). Use Certbot with the Nginx plugin to obtain a free Let's Encrypt SSL certificate for your subdomain. Enable automatic certificate renewal via the Certbot systemd timer. This step is the one most likely to trip up first-time deployers - the Nginx configuration needs correct proxy_pass headers including Upgrade and Connection headers for n8n's WebSocket connections to work properly.
Step 6: Point your domain to the server
Add an A record in your DNS provider pointing your n8n subdomain (for example n8n.yourdomain.co.uk) to your VPS IP address. DNS propagation typically takes five to thirty minutes. Verify propagation before attempting to obtain the SSL certificate, as Certbot's HTTP-01 challenge requires the domain to resolve to your server.
Step 7: Start n8n and verify access
Run docker compose up -d in your /opt/n8n directory to start the n8n container in detached mode. Check container logs with docker compose logs -f n8n. Navigate to your domain in a browser and complete the n8n initial setup wizard - create your owner account and set your encryption key. Store the encryption key securely as it is required to decrypt your credentials if you ever restore from a backup.
Step 8: Configure automated backups
For SQLite deployments, back up the database file daily using a cron job that copies it to an S3-compatible bucket (Backblaze B2 costs approximately £0.006 per GB/month). For PostgreSQL deployments, use pg_dump on a daily schedule. Retain a minimum of seven daily backups and one monthly backup. Test the restore procedure before considering the deployment production-ready.
Step 9: Configure email alerting for failed workflows
In n8n Settings, configure an SMTP connection for email alerts. Enable error workflow notifications so that any workflow execution that encounters an unhandled error sends an email alert to your designated operations address. Set up a global error workflow that captures the failing workflow name, execution ID and error message - this dramatically reduces the time to diagnose production issues.
Step 10: Plan your version update schedule
n8n releases updates frequently. Pin your docker-compose.yml to a specific version tag (for example n8nio/n8n:1.48.0) rather than using latest, so updates only happen when you deliberately test and apply them. Allocate a monthly maintenance window of approximately thirty minutes to test the new version in a staging environment before updating production.
If this process sounds complex or time-consuming for your team, Softomate provides managed n8n hosting from £150 per month. We handle the complete setup, keep n8n updated, maintain server security patches, run daily backups and provide monitoring with automated alerts. The managed service removes the infrastructure burden entirely so your team can focus on building workflows rather than running servers.
Self-hosted n8n has real limitations that matter for specific business situations. We want to be direct about these rather than undersell them - choosing the wrong automation platform is more expensive in time and friction than any monthly subscription cost. Here is an honest assessment of where n8n falls short and how those limitations can be mitigated.
The most significant limitation is the infrastructure management requirement. Running a self-hosted server means you are responsible for operating system security patches, Docker updates, SSL certificate renewals, disk space monitoring, backup verification and incident response when the server has a problem. For a business with no dedicated IT resource, this is a genuine burden. The mitigation is n8n cloud (hosted by n8n, approximately £50/month for most SME volumes) or a managed hosting provider like Softomate (£150/month including monitoring and updates). The managed options eliminate the infrastructure burden while retaining the cost and compliance advantages over Zapier.
The integration count gap versus Zapier is real but less limiting in practice than it first appears. Zapier lists over 6,000 integrations, n8n has 350+ native nodes. However, the vast majority of integrations businesses actually use are available in n8n natively - the 350 integrations cover essentially all mainstream business software. For the minority of applications not covered by a native n8n node, the HTTP request node allows connection to any REST API, and n8n's community node library adds hundreds of additional integrations contributed by the open-source community. In practice, we have encountered only a handful of niche applications in three years of building n8n automations that genuinely could not be integrated without custom code.
Support quality is different from Zapier and Make, not necessarily worse. Zapier and Make offer email and chat support with defined response time SLAs on paid plans. n8n's support model for self-hosted users is primarily the community forum, which is active and technically knowledgeable, plus paid support plans for enterprise customers. For businesses that need guaranteed support response times, the managed hosting option from Softomate or n8n's enterprise plan provides this. Softomate clients on our managed hosting or retainer plans receive direct support from the team that built their workflows - which typically means faster issue resolution than a generic helpdesk.
Version updates can occasionally break workflows when n8n makes changes to node schemas or execution behaviour. This is a genuine risk for self-hosted deployments on production workflows. The mitigation is the version pinning strategy described in the setup guide above - do not update automatically, test in staging first. n8n's release notes document breaking changes clearly, and the community typically identifies compatibility issues within days of a new release. Over three years of production n8n deployments, Softomate has encountered three instances of breaking updates requiring workflow adjustments - manageable with a disciplined update process.
The learning curve for non-technical users is steeper than Zapier. Zapier is designed to be usable by non-developers with no automation experience, and it succeeds at this. n8n's visual editor is more powerful but also more complex - concepts like data transformation with expressions, error handling branches and sub-workflow calls require comfort with data structures and basic logic that Zapier largely abstracts away. For businesses where automation is owned by a non-technical team member, Make is often the better fit at low volumes, with n8n becoming appropriate when that person has developed enough automation experience to handle more complexity. Softomate addresses this through the training component of every n8n build engagement - we document workflows clearly and train the client team on how to make common modifications without external support.
| Limitation | Impact | Workaround or mitigation |
|---|---|---|
| Requires server management | Time and technical cost for IT | Use n8n cloud or Softomate managed hosting (£150/month) |
| 350 integrations vs Zapier 6,000+ | Some niche apps not covered natively | HTTP request node covers most REST APIs; community nodes fill gaps |
| No phone support on self-hosted | Slower resolution for critical incidents | Community forum + Softomate managed support plan |
| Version updates can break workflows | Maintenance burden, potential downtime | Pin version, maintain staging environment, test before updating |
| Steeper learning curve | Slower adoption for non-technical users | Softomate builds, documents and trains your team on every engagement |
Taken together, these limitations point to a clear profile of the businesses for whom n8n self-hosted is the right choice: organisations with ten or more employees, meaningful automation volume (10,000+ tasks/month), an IT-capable person in-house or a managed hosting arrangement, and either cost sensitivity or data compliance requirements that cloud platforms do not satisfy cleanly. For sole traders and very small businesses with low automation volumes and no regulated data, Make or even Zapier's lower tiers remain the more practical starting point.
Yes for initial setup - you need Linux command line comfort, Docker knowledge and the ability to configure Nginx. Ongoing operation is manageable for a technically confident business owner once set up. Alternatively, Softomate provides managed n8n hosting from £150 per month, covering setup, updates, backups and monitoring.
Self-hosted n8n gives you full version control - you update only when ready. We recommend running a test environment first and pinning to a stable version for production. n8n provides release notes for breaking changes. Softomate manages version updates for all hosted clients with a 48-hour test window before production deployment.
Yes - GoHighLevel connects via webhook triggers and HTTP request nodes using the GHL API. Odoo connects via the Odoo XML-RPC or JSON-RPC API using n8n's HTTP request node. Both integrations are available in n8n without native modules and work reliably in production. Softomate has built GHL and Odoo integrations on n8n for UK clients.
Reliability depends on server quality and maintenance. A well-configured VPS with automated backups and monitoring is typically as reliable as Zapier or Make. The key risk is self-hosted infrastructure going down without monitoring - which is why server health alerting and automated restarts (via Docker restart policies) are essential from day one.
Softomate offers three post-go-live options: managed hosting (£150/month, covers server, updates, backups, monitoring), retainer support (from £350/month, covers workflow changes and new automations) and ad-hoc support (£120/hour for changes). All n8n builds include 30 days of hypercare support as standard, regardless of which ongoing option the client chooses.
Migration cost depends on the number and complexity of existing Zapier workflows. Simple trigger-action automations typically take one to two hours each to rebuild in n8n; complex multi-step workflows with conditional logic take three to six hours. Softomate quotes migrations individually, but most small business Zapier migrations (ten to twenty workflows) fall in the £2,000-£6,000 range and pay back within four to eight months from the Zapier subscription saving alone.
n8n can run on Windows via Docker Desktop, but this is not recommended for production business workloads. Windows introduces additional Docker networking complexity, and Docker Desktop is licensed commercially for businesses with more than 250 employees or £10 million revenue. For production deployments, a Linux VPS (Ubuntu 22.04) is the supported and recommended environment - it is also significantly cheaper than running Windows Server licences alongside Docker.
Yes - n8n has a first-class webhook node that creates a unique HTTPS endpoint your external applications can POST data to, triggering a workflow instantly. Webhook-triggered workflows in n8n fire in real time with no polling delay, unlike some Zapier plans where trigger polling runs every one to fifteen minutes depending on your subscription tier. This makes n8n self-hosted particularly well suited to time-sensitive automations such as payment notifications, form submissions, CRM lead routing and appointment booking confirmations.
n8n self-hosted automation makes clear financial sense once a UK business reaches 10,000 or more automation tasks per month, where the server cost of approximately £20 per month compares favourably to Make at £80-250 or Zapier at £200-940. For regulated industries - healthcare, legal and financial services - the data residency advantage of keeping all workflow data on UK servers adds compliance value that cloud platforms cannot match without complex contractual arrangements. The main barrier is technical complexity, which managed hosting services from providers including Softomate resolve.
Interested in self-hosted n8n for your business? Book a free consultation with Softomate - we will assess your automation volume, data requirements and technical capability and recommend whether self-hosted n8n, n8n cloud, Make or Zapier is the right fit for your situation.
Written by the Softomate Solutions AI Development Team, Barking, East London. We build, host and manage n8n automations for UK businesses in regulated industries including healthcare, legal, financial services and property management.We protect the real names of all clients featured in examples and case studies. Every testimonial is from a real client.
More from the blog
Work with us
Every project we take on has a measurable outcome. Talk to our London team and we will show you exactly how we would approach your challenge.
Softomate Solutions Limited
Deen Dayal Yadav
Online
