One of the biggest reasons Australian businesses choose n8n over cloud-only automation tools is the ability to self-host. Running the platform on your own infrastructure means your workflows, credentials, and data stay exactly where you put them, which for many Australian organisations means on Australian soil, under Australian jurisdiction.
This guide explains what self-hosting n8n actually involves, when it is the right choice, and the trade-offs to weigh before you commit.
Why Self-Hosting Matters for Australian Businesses
When you use a cloud automation platform, your data flows through that vendor's infrastructure, often overseas. For some businesses that is fine. For others, it creates real problems:
- Privacy Act obligations. Sending personal information to overseas infrastructure can constitute disclosure to an overseas recipient under Australian Privacy Principle 8, with the responsibilities that carries. Our data sovereignty guide covers this in detail.
- Industry and contractual requirements. Healthcare, financial services, government contractors, and many enterprise clients impose data-residency conditions that cloud-only tools cannot satisfy.
- Sensitivity of the data. Some information is simply too sensitive to route through third-party infrastructure, regardless of certifications.
Self-hosting removes the question entirely. If the platform runs on infrastructure you control, in a region you choose, the data never leaves that boundary.
What Self-Hosting n8n Actually Means
n8n is open and designed to be self-hosted. In practice, you run it as a container (typically Docker) on infrastructure of your choosing. For Australian data residency, that infrastructure lives in an Australian region:
- AWS Sydney (ap-southeast-2) and Melbourne (ap-southeast-4)
- Microsoft Azure Australia East and Australia Southeast
- Google Cloud Sydney (australia-southeast1) and Melbourne (australia-southeast2)
- On-premises servers, for organisations that want everything physically in-house
The core components are modest: the n8n application itself, a database (usually PostgreSQL) to store workflows and execution data, and sensible networking and backups around it. For most SMEs this runs comfortably on a small virtual machine.
The Cost Picture
Self-hosting changes the economics as well as the compliance posture. As we noted in our n8n versus Zapier comparison, self-hosted n8n has no per-execution fee, you pay for infrastructure, not for usage.
| Item | Typical cost (AUD/month) |
|---|---|
| Small virtual machine (Australian region) | $15–40 |
| Managed PostgreSQL (or self-managed on the same VM) | $0–30 |
| Backups and storage | $5–15 |
| Typical total | ~$20–85/month |
For a business running thousands of workflow executions, this is dramatically cheaper than per-task cloud pricing, often by 80 to 95 percent. The cost you take on instead is operational: someone has to run, secure, and maintain it.
The Trade-Offs to Weigh
Self-hosting is not automatically the right answer. It trades convenience for control.
What You Gain
- Full data residency. Everything stays in your chosen Australian region.
- No per-execution costs. Unlimited workflows and executions for the price of the infrastructure.
- No vendor lock-in. Your workflows and data live in your own database.
- Custom security. Integrate with your existing authentication, VPN, and network controls.
- No rate limits. Process as much as your infrastructure can handle.
What You Take On
- Operational responsibility. Updates, security patches, backups, and uptime are now yours to manage.
- Initial setup. Standing up the environment properly, secured, backed up, monitored, takes expertise.
- Recovery planning. You own the disaster-recovery plan; there is no vendor to fall back on.
For organisations with capable IT support or a delivery partner, these are manageable. For a business with no technical resource and only simple, low-sensitivity automations, managed n8n Cloud may be the more sensible starting point.
n8n Cloud or Self-Hosted: A Quick Comparison
Self-hosting is the right answer for many Australian businesses, but not all. This is the trade-off at a glance:
| Consideration | n8n Cloud | Self-Hosted |
|---|---|---|
| Data residency | Limited control over region | Full control, your chosen region |
| Setup effort | Minimal, sign up and go | Moderate, requires expertise |
| Ongoing maintenance | Handled by n8n | Your responsibility |
| Cost at high volume | Per-execution, scales with use | Fixed infrastructure cost |
| Security model | n8n's controls | Your own controls and integrations |
| Best for | Simple, lower-sensitivity automation | Regulated data, high volume, customisation |
If you have a genuine data-residency requirement, high execution volume, or the need to integrate with internal systems and security, self-hosting wins clearly. If you have none of those and limited technical resource, Cloud may get you started faster.
A Simple Reference Setup
For most Australian SMEs, a sound self-hosted setup is not complicated:
- A small virtual machine in an Australian region (for example, AWS Sydney or Azure Australia East).
- n8n running in Docker, behind a reverse proxy with HTTPS and authentication.
- A PostgreSQL database for workflows and execution history, either on the same machine for smaller setups or managed separately as you grow.
- Automated daily backups of the database and credentials, stored securely and tested periodically.
- Basic monitoring and alerting so you know immediately if the instance or a critical workflow fails.
This is well within reach for a business with competent IT support, and entirely routine for an experienced delivery partner. The goal is a setup that is secure, recoverable, and observable from day one, not one that is bolted together and forgotten.
Doing It Properly
If you self-host, a few things are non-negotiable:
Secure it from day one. Put n8n behind proper authentication, restrict network access, and never expose the editor to the open internet without protection.
Encrypt credentials and back up regularly. Your n8n instance holds the keys to your connected systems. Treat it as the sensitive asset it is, with encrypted credentials and tested, automated backups.
Keep it patched. Self-hosting means you are responsible for applying updates. Build a routine for it rather than letting the instance drift.
Monitor it. Know when a workflow fails or the instance is unhealthy before your business processes do.
Configure AI endpoints for residency too. Self-hosting n8n keeps your orchestration onshore, but if a workflow calls an overseas AI API, that data still travels. Use Australian-region AI endpoints, or self-hosted models, to keep the whole pipeline compliant.
What to Watch For
- Underestimating the operational load. Self-hosting is not "set and forget". Budget for ongoing maintenance, or have a partner handle it.
- Securing the orchestration but not the AI calls. Data residency is only as strong as its weakest link. Check where every external call sends data.
- Skipping backups until it is too late. The first time you need a backup is the wrong time to discover you do not have one.
- Self-hosting when Cloud would do. If you have no residency requirement and little technical resource, the managed option may serve you better. Match the choice to the actual need.
Getting It Right
Self-hosting n8n gives Australian businesses something cloud-only tools cannot: complete control over where their data lives and how it is handled, at a fraction of the per-execution cost. The price is operational responsibility, which is very manageable with the right setup and support.
At IOTAI, we deploy and manage self-hosted n8n on Australian infrastructure for clients with data-residency and compliance requirements, handling the setup, security, and maintenance so you get the control without the operational burden. Our free assessment includes a data-residency review, or book a consultation to discuss your requirements.
For businesses that take data sovereignty seriously, self-hosting is not the hard option. It is the obvious one.