Short version: Self-hosting n8n in an Australian region — AWS Sydney (ap-southeast-2) is the common choice — keeps your automation data onshore for roughly A$5–A$50/month. The software is free; the cost is a small server plus setup. The one thing to watch under the Privacy Act 1988 (APP 8) is any node that calls an offshore service like a US-based LLM — that is a cross-border disclosure you should map, redact, or move onshore. Below: the deployment stack we ship, the AUD costs, and the four mistakes that break self-hosted n8n.
Why self-host in Australia at all?
Three reasons, in order of how often they decide it: data residency (keeping personal or financial data onshore for the Privacy Act, client contracts, or peace of mind), cost at scale (self-hosting is flat-rate, not per-task — see the n8n vs Zapier AUD breakdown), and control (SSO, network restrictions, and full ownership of the deployment). For an SMB handling customer or patient data, the first reason alone is usually enough.
What it costs in AUD
n8n is source-available and free to run. Your real cost is the server and a domain:
| Component | Indicative cost (AUD) |
|---|---|
| AWS Sydney t3.small (2 vCPU / 2 GB) or equivalent VPS | ~A$20–A$40 / month |
| Local VPS (e.g. small onshore host) | ~A$5–A$20 / month |
| Domain + TLS (Let's Encrypt) | ~A$20 / year + free TLS |
| External API calls (e.g. LLM), if used | usage-based |
For context, n8n Cloud starts around A$35–A$40/month and bills on executions, so self-hosting onshore is usually both cheaper at volume and better for residency. Full local pricing: n8n pricing in Australia.
The deployment stack we ship
Every self-hosted build we hand over is the same proven stack: Docker Compose running n8n, Postgres for persistence (never the default SQLite in production), and Caddy (or Nginx) as a reverse proxy terminating TLS via Let's Encrypt. Secrets live in environment variables, not the compose file; the editor is locked behind auth and an IP allow-list or VPN; nightly Postgres dumps and workflow-JSON exports go to onshore object storage. The full walkthrough — adapted here for an Australian region — is in the Field Note: Self-hosting n8n — the 30-minute setup we ship to clients.
The Privacy Act, APP 8, and offshore LLM calls
Hosting onshore keeps the engine, queue, and database in Australia — but it does not automatically make every data flow onshore. The moment a workflow calls a US-based LLM or a foreign SaaS API, personal information may cross the border, which engages Australian Privacy Principle 8 (cross-border disclosure). The practical controls: map every external call, redact personal information before it leaves the country, or run an onshore/self-hosted model (e.g. Ollama) for sensitive steps. We cover the procurement-review angle in depth in AI agents for Australian SMBs — Privacy Act + NAIC compliance.
The four mistakes that break self-hosted n8n
- Leaving SQLite in production. It corrupts under concurrency. Use Postgres from day one.
- No backups, or untested ones. Automate nightly dumps and rehearse a restore — a backup you've never restored is a guess.
- Exposing the editor publicly. Put it behind auth/SSO and an IP allow-list or VPN; disable public sign-up.
- Ignoring the offshore data path. The server is onshore but an unredacted LLM call isn't — map it before go-live, not after an audit.
Common questions
How much does it cost to self-host n8n in Australia?
Roughly A$5–A$50/month for a small instance in AWS Sydney or a local VPS, plus a domain. A 2 vCPU / 4 GB box runs tens of thousands of executions a month; n8n itself is free, so beyond the server your only variable cost is external API calls.
Does self-hosting keep my data in Australia?
Yes, if you host in an Australian region — the engine, queue, and database run onshore. Watch any node that calls an offshore service; that step is a cross-border disclosure to document, redact, or move onshore.
How does this relate to the Privacy Act and APP 8?
APP 8 governs cross-border disclosure of personal information. Self-hosting onshore keeps core processing in Australia, but APP 8 still applies to any step sending personal information overseas — so map external calls and redact or use an onshore model for sensitive data.
Self-host or use n8n Cloud?
Cloud for zero-ops with no residency requirement; self-host for data residency, predictable cost at scale, network/SSO control, and ownership. Many SMBs self-host because it's both cheaper at volume and keeps data onshore.
Need n8n running onshore, locked down, and backed up?
Book a 15-minute map (US$50, credited to a build). We'll scope an AWS-Sydney deployment with the data flows mapped for APP 8.