Self-Host vs n8n Cloud: An Australian Cost and Compliance Guide

Updated May 2026. Rewritten to reflect the dramatic cost savings and compliance benefits our clients are realising with self-hosted n8n in 2026.

Self-hosting n8n has become the standard move for Australian businesses that run more than a handful of automation workflows. Cloud platforms charge per execution. Self-hosted n8n does not. That difference alone cuts automation costs by 70% or more once you move beyond basic volumes.

We are a Brisbane-based automation consultancy that has deployed self-hosted n8n for ASX-listed companies, healthcare providers, insurance firms, and professional services. Every one of them asked the same question: “When does it make sense to self-host instead of staying on Zapier or Make?” The answer came down to cost, compliance, and control. This guide walks through the real numbers and the decision framework so you can answer it for yourself.

If you are running automation workflows on a cloud platform and want to understand the cost and compliance case for self-hosting, this will give you everything you need to make that decision. We cover the Australian regulatory landscape, the actual AUD pricing at scale, and the honest situations where self-hosting is the wrong choice.

Why Self-Hosting n8n Matters for Australian Businesses

Self-hosting n8n is not a technical preference. It is a business decision driven by three things: cost, compliance, and operational control. Each one matters, but the way they combine is what makes the case so compelling.

Cloud automation platforms (Zapier, Make, n8n Cloud) run on shared infrastructure. Their business model is built on charging you for every execution, every operation, and every resource your workflows consume. They keep your data on their servers, in their data centres, under their security model. You get ease of setup and zero infrastructure overhead. You also get per-execution costs that scale with your business, data stored overseas, and limited integration options.

Self-hosted n8n flips that model. You run n8n on your own infrastructure (or infrastructure you fully control). You pay fixed monthly costs for the server, database, and backups. You pay zero per-execution fees. Your data never leaves your infrastructure. You can integrate with anything—internal APIs, legacy systems, government platforms, all without exposure to the public internet.

Australian Data Sovereignty and Compliance

This is the driver that moves most regulated Australian businesses off cloud platforms fastest. When you use Zapier, Make, or n8n Cloud, your workflow data is processed and stored overseas. That creates a compliance problem under Australian law that ranges from inconvenient to disqualifying depending on what data your workflows handle.

APP 8 and the Privacy Act 1988

The Australian Privacy Principles under the Privacy Act 1988 do not forbid overseas data transfer. But APP 8 requires that if you disclose personal information to an overseas recipient, you take reasonable steps to ensure they comply with the APPs. In practice, this means contractual safeguards with your cloud platform provider, due diligence on their data handling practices, and ongoing monitoring of how they treat your data.

Or you can self-host n8n on Australian infrastructure and sidestep APP 8 entirely. Your data never leaves the country. There is no overseas recipient to monitor. No contractual obligations to negotiate. No compliance risk from a third party’s security breach or change in data handling practices. We work with healthcare providers and financial services firms in Australia where that simplification is worth the cost difference alone.

APRA CPS 234 and Financial Services

If you operate in financial services, APRA’s Prudential Standard CPS 234 (Information Security) requires that APRA-regulated entities maintain information security capabilities commensurate with the threats to their information assets. This includes explicit requirements around third-party and outsourcing arrangements. Running your automation workflows through a US-based cloud platform introduces a third-party dependency that needs formal assessment, documentation, and reporting.

Self-hosting on your own infrastructure, or on Australian cloud infrastructure under your direct control, cuts through most of that overhead. You control the security posture, the access controls, the audit trail, and the incident response. Your compliance team can verify the setup once and be done, instead of ongoing monitoring of a third party’s security practices.

My Health Records and Healthcare Data

Healthcare organisations handling data under the My Health Records Act face some of the strictest data handling requirements in Australia. Workflows that process patient data, medical records, or health information cannot legally be sent to cloud automation platforms that store data overseas. Self-hosting n8n on Australian infrastructure gives you direct control over data location, access controls, audit logging, and breach response. No third party involved. No overseas processing. This is not optional for most healthcare providers.

We have worked with practices and clinics that moved from Zapier to self-hosted n8n specifically because their legal and compliance teams flagged cloud platforms as a breach of their obligations under health data legislation.

The Cost Reality: Cloud vs Self-Hosted in 2026

The financial case for self-hosting starts to make sense once you move beyond basic automation volumes. Cloud platforms charge per execution, per task, or per operation. Self-hosted n8n charges nothing per execution. You pay for the infrastructure, and that cost stays relatively flat regardless of how many workflows you run.

Here is what the actual numbers look like for an Australian mid-size business in 2026.

Cloud Platform Costs for Mid-Size Automation

A mid-size Australian business running 20 to 30 active workflows with moderate volume (50,000 to 100,000 total executions per month) can expect to pay:

Self-Hosted n8n Costs for the Same Workload

At the low end, you are saving $80 per month compared to n8n Cloud. Compared to Zapier, you are saving $250 to $1,050 per month. Over a full year, that is $3,000 to $12,600 in cost reduction, just from eliminating per-execution fees.

The gap widens as your automation usage grows. A business running 200,000 executions per month on Zapier might be paying $2,000+ AUD monthly. Self-hosted? Still $70 to $150. You might need to bump the server up one tier for heavy workloads, but the cost increase is linear and modest, not exponential.

We built a weather data pipeline for an insurance tech company that ingests Bureau of Meteorology data via FTP and processes it continuously. That kind of workflow running on Zapier would cost thousands per month. Self-hosted, the infrastructure cost is a fraction of what a cloud platform would charge at that volume. Similarly, we automated patient data entry for a medical practice using n8n with OCR and AI. The workflows process referrals from email and Healthlink continuously. On a per-execution cloud plan, the monthly cost scales with every referral. Self-hosted, it does not.

No More Per-Execution Throttling

Every cloud automation platform imposes execution limits. Zapier limits tasks per month. Make limits operations. Even n8n Cloud has execution-based tiers. Hit your limit and you either pay overage fees, get throttled, or have workflows silently fail.

Self-hosted n8n has no execution limits. Your workflows run as many times as your server can handle them. No throttling. No rate limiting. No surprise invoices. Reliability is straightforward: properly size your server for your workload, and the system will process whatever you throw at it.

This matters for more than just cost. Cloud execution caps force you to build conservative workflows. You batch operations instead of running in real time. You delay non-critical workflows to stay within quota. You add logic to count executions and pause when approaching limits. All of that complexity disappears with self-hosting. Your automation infrastructure simply does what you ask it to do.

Infrastructure Control and Security

Self-hosting gives you security controls that cloud platforms structurally cannot offer. You can run n8n on a private subnet with no public internet access. Workflows that process sensitive data never touch the public internet. You can integrate with your existing identity provider, enforce multi-factor authentication, apply IP whitelisting, and configure session policies that match your security standards.

Audit logging is under your control. You decide what gets logged, where it lives, how long it is retained, and who can access it. Critical for compliance audits and incident investigation. You can encrypt data at rest and in transit to meet your specific requirements rather than accepting a cloud platform’s defaults. You can scan and patch on your schedule. No waiting for a cloud provider to address a vulnerability in their shared infrastructure.

For businesses where security and control are operational requirements rather than compliance checkboxes, self-hosting is the only model that gives you real control over your automation infrastructure.

Custom Integrations and Extensibility

n8n is open source. You can build custom nodes for any system, API, or internal tool your business uses. Cloud platforms limit you to their pre-built integrations and whatever you can hack together with generic HTTP request modules.

Custom nodes can integrate with proprietary internal APIs, legacy systems running SOAP or XML-RPC, government platforms with specific authentication requirements, and industry-specific systems with non-standard APIs. Internal databases behind firewalls that cloud platforms simply cannot reach. These are not workarounds. They are real extensions of the platform that sit alongside built-in nodes in the n8n interface.

Our weather data pipeline project required custom n8n workflows to ingest Bureau of Meteorology data via FTP and process .tar archives. No cloud automation platform supports that out of the box. Self-hosted n8n made it straightforward. The custom nodes sit in the palette like any other integration, and the team uses them exactly like built-in nodes with proper input/output configuration, error handling, and credential management.

Direct Network Access to Internal Systems

This is a benefit that is impossible to replicate on any cloud platform. Self-hosted n8n runs inside your network. It can talk directly to internal databases, ERP systems, file servers, and APIs that are not exposed to the public internet. If your business runs systems behind a VPN, a private cloud, or an air-gapped network, cloud automation platforms are simply not an option. They cannot reach your internal systems without you punching holes in your firewall or setting up tunnelling arrangements that introduce their own security risks.

Self-hosted n8n sits alongside those systems on the same network. It connects to your PostgreSQL database on the local network. It queries your internal REST API on a private IP. It writes files to your NAS. None of that traffic leaves your infrastructure. None of it is exposed to the internet. For organisations with strict network security requirements, self-hosted is the only option that makes sense.

When Self-Hosting Is NOT the Right Choice

Self-hosting n8n is not the right choice for every business. Being honest about this is important.

You should consider n8n Cloud or another managed platform if your team has no technical capacity for server management. Self-hosted n8n requires someone to handle updates, monitor uptime, manage backups, and troubleshoot infrastructure issues. If you are a small team running five simple workflows and paying $30 per month on Zapier, the overhead of managing your own infrastructure does not make sense. If you need to be running automation workflows within days, not weeks, cloud platforms get you live faster. Self-hosting requires setup, testing, hardening, and configuration before you go live.

Self-hosting tends to work best for businesses running 10 or more workflows, processing sensitive or regulated data, wanting to scale automation without scaling costs, and with either internal technical capacity or a partner (like us) to manage the infrastructure. If you are not sure where you fall, book a call with our team and we will give you a clear recommendation.

How to Get Started with Self-Hosted n8n

If the benefits align with your business requirements, getting started is less involved than most people assume. We have written step-by-step guides covering the most common deployment approaches:

• How to Self-Host n8n covers the fundamentals and decision framework
• How to Host n8n with Docker is the approach we recommend for most businesses
• How to Host n8n on Fly.io suits teams that want managed hosting without full cloud infrastructure
• How to Host n8n with Coolify is an excellent option for teams that want a self-hosted PaaS layer

For a broader look at how we work with n8n across deployment models, visit our n8n consultants hub page. If you want help designing a self-hosted n8n infrastructure for your business or want to understand whether self-hosting makes sense for your specific situation, talk to our team.

Frequently Asked Questions

What are the main benefits of self-hosting n8n?

The primary benefits are cost savings (70% or more once you move past basic volumes), no per-execution throttling, full control over your data and infrastructure, direct network access to internal systems, and the ability to build custom integrations. For Australian businesses handling regulated data, self-hosting eliminates the compliance burden of overseas data transfer under the Privacy Act and industry-specific regulations.

How much cheaper is self-hosted n8n in Australia?

Infrastructure costs range from $70 to $150 AUD per month for most businesses. Compare that to Zapier at $400–$1,200 AUD monthly, Make at $150–$500, or n8n Cloud at $150–$400. The savings increase with automation volume. A business running 200,000 executions per month might pay $2,000+ AUD on Zapier but $70–$150 self-hosted. If you are currently paying more than $200 per month on a cloud platform, self-hosting will almost certainly save you money within the first few months.

Is self-hosted n8n compliant with Australian Privacy requirements?

Running n8n on Australian infrastructure ensures your workflow data never leaves the country, which simplifies compliance with the Privacy Act 1988, Australian Privacy Principles (especially APP 8), APRA CPS 234, and sector-specific regulations like the My Health Records Act. It is the most direct way to meet Australian data sovereignty requirements without complex contractual arrangements with overseas cloud providers.

What infrastructure do I need to self-host n8n?

A standard setup requires a virtual private server (4 vCPU, 8 GB RAM is a good starting point) and a PostgreSQL database. Most businesses deploy on Hetzner, Vultr, AWS Sydney, or DigitalOcean Sydney. Docker Compose simplifies deployment significantly. You will need basic Linux administration skills or a managed service provider (like us) to handle setup and maintenance.

Can self-hosted n8n connect to internal systems behind my firewall?

Yes. That is one of the primary advantages. Self-hosted n8n runs on your network, so it has direct access to internal databases, APIs, file servers, and any system on your local network. Cloud platforms cannot reach internal systems without you exposing them to the internet, which creates security risks. Self-hosted n8n can talk to private PostgreSQL databases, internal REST APIs, and NAS storage without any public internet exposure.

Do I need DevOps experience to self-host n8n?

You need someone to handle basic server administration (updates, monitoring, backups, troubleshooting). If your team does not have that capacity, working with a managed service provider is a sensible investment. Many non-technical teams run self-hosted n8n successfully with support from an external partner who handles infrastructure while the team focuses on building workflows.

Does self-hosted n8n get updates and new features?

Yes. Self-hosted n8n uses the same codebase as n8n Cloud. New features, bug fixes, and security patches are released regularly. You control when you update. We recommend testing new releases in a staging environment before deploying to production, and we handle this process for all of our managed clients to ensure zero downtime.

How often do I need to maintain self-hosted n8n?

Regular maintenance includes monthly security patches, quarterly n8n version updates (tested in staging first), and ongoing monitoring of disk space and database performance. The most common issue we see in production is execution logs consuming all available disk space, which is entirely preventable with proper execution data pruning configuration. Once set up correctly, self-hosted n8n requires minimal ongoing attention beyond regular updates and monitoring.

Self-hosting n8n is the standard move for Australian businesses that run significant automation workloads, handle regulated data, or want to control costs at scale. The decision usually comes down to whether you have the technical capacity to manage infrastructure or the budget to engage a partner who does. If you want help evaluating self-hosting for your business or building the infrastructure to support it, get in touch with our team. We are based in Brisbane and have built self-hosted automation systems for organisations across Australia.