Updated May 2026. Rewritten with current VPS pricing, Australian hosting options, and production deployment patterns.

Self-hosting n8n means running your workflow automation platform on infrastructure you control, rather than paying n8n Cloud to host it. The concept is straightforward. The execution is where most teams get value, or get stuck.

We are a Brisbane-based automation consultancy that has deployed self-hosted n8n for Australian financial services firms, healthcare technology businesses, professional service providers, and regulated enterprises. We have built workflows that process thousands of executions per day on self-hosted instances in Sydney data centres. This guide comes from that hands-on experience.

This article is aimed at technical teams evaluating whether self-hosting makes sense, and operators planning their first deployment. We walk through the decision framework, hosting options, real cost comparisons in AUD, security hardening, and production maintenance. If you want to skip to a specific deployment method, our guides for Docker, Fly.io, and Coolify have step-by-step instructions.

What Self-Hosted n8n Actually Is

When you self-host n8n, you own the entire stack. The n8n application runs on a server you rent or operate. The database lives on infrastructure you control. Your execution logs, credentials, and workflow history are all in your hands. Compare this to n8n Cloud, where you pay a monthly subscription and n8n manages hosting, backups, and updates for you.

n8n’s Community Edition operates under a sustainable use licence. You do not pay n8n licence fees for the software itself. You pay for compute: a VPS, managed database, or Kubernetes cluster. For most businesses this costs between $10 and $100 AUD per month, with no per-execution charges.

This fundamentally changes the economics. At high execution volumes, self-hosting is dramatically cheaper than cloud. It also gives you compliance options if you operate in regulated industries where data must stay in Australian jurisdiction. But it places operational responsibility on your team.

Self-Hosted vs n8n Cloud: The Honest Comparison

Neither approach is universally correct. Both work for the right use case. Here is how they stack up on the factors that actually matter.

Cost and Scale

n8n Cloud Starter costs around $35 AUD per month for 2,500 executions. Pro tier is roughly $80 AUD per month for 10,000 executions. Enterprise is custom pricing, typically $300+ AUD monthly for high volumes.

Self-hosted on a VPS costs $15 to $50 AUD per month for the server, with no execution limits. A business running 5,000 monthly executions on Cloud Pro pays $80. On self-hosted, that same business pays $25 for a server and runs unlimited workflows. At 50,000 executions monthly, Cloud Enterprise becomes $300+, while self-hosted remains under $50. The crossover point is roughly 3,000 to 5,000 executions per month, depending on your infrastructure choices.

Control and Customisation

Self-hosting gives you full control: pin specific n8n versions, install community nodes, tune PostgreSQL parameters, run custom code nodes with specific dependencies. n8n Cloud manages versions for you and restricts certain customisations. If you need non-standard configuration, self-hosting is the only path.

Data Location and Compliance

This is where self-hosting becomes non-optional for many Australian organisations. n8n Cloud processes your workflow data on their infrastructure. For businesses subject to the Privacy Act 1988, Australian Privacy Principles, healthcare regulations under the My Health Records Act, or government contracts requiring data sovereignty, this creates compliance constraints.

Self-hosting on Australian infrastructure, whether in a Sydney data centre or your office, means workflow data never leaves Australian jurisdiction. This addresses compliance frameworks that prohibit or restrict overseas data processing.

Operational Responsibility

n8n Cloud handles updates, backups, and uptime. Self-hosting puts this on your team. Updates need testing before deployment. Backups require automation and periodic restore testing. You need monitoring to know when things fail. This is ongoing work, not a one-time task.

Hosting Options Explained

There are several proven ways to run self-hosted n8n. Each involves different complexity and cost trade-offs.

VPS with Docker

Rent a VPS from Vultr, Hetzner, DigitalOcean, or Linode AU. Install Docker and run n8n as a container. Setup takes under an hour for experienced operators. This is our default recommendation for most businesses.

Typical cost: $15 to $40 AUD per month. Best for: Most businesses. Predictable cost, straightforward management, easy backups. Australian options: Vultr and DigitalOcean both offer Sydney data centres. Linode has Melbourne. Hetzner has Melbourne and Sydney. For data sovereignty, choose a Sydney or Melbourne VPS explicitly.

Fly.io

Fly.io is a container platform that abstracts away much infrastructure management. Deploy n8n as a container image and Fly.io handles networking, TLS, and scaling. It sits between raw VPS and fully managed platforms.

Typical cost: $20 to $60 AUD per month. Best for: Teams wanting simpler infrastructure without sacrificing control. Useful if you need global distribution or multi-region failover. Limitation: Data centres are not all in Australia, which may conflict with data sovereignty requirements.

Coolify

Coolify is an open-source platform-as-a-service you install on your own server. It gives you a web interface for deploying and managing applications, automatic SSL, and basic monitoring all on infrastructure you control.

Typical cost: $15 to $40 AUD per month for the underlying VPS. Coolify itself is free. Best for: Teams managing multiple self-hosted applications who want a unified management interface. Particularly suited to organisations already running other services on their own infrastructure.

Kubernetes

For large-scale deployments with high execution volumes and strict uptime requirements, Kubernetes provides auto-scaling and redundancy. n8n publishes official Helm charts, and queue mode allows distributed workflow processing across multiple worker nodes.

Typical cost: $100 to $500+ AUD per month depending on cluster size. Best for: Enterprise deployments processing 100,000+ executions monthly. Not necessary for most organisations.

Server Specifications by Workload

n8n is not resource-intensive for small to medium deployments. Here is what we recommend based on years of live deployments.

Small Deployment

Under 20 active workflows, light execution volume.

1 vCPU
2 GB RAM
20 GB SSD
Cost: $10 to $15 AUD per month

Medium Deployment

20 to 100 active workflows, moderate execution volume (5,000 to 20,000 executions monthly).

2 vCPU
4 GB RAM
40 GB SSD
Cost: $20 to $40 AUD per month

Large Deployment

100+ active workflows, high execution volume (20,000+ monthly).

4+ vCPU
8+ GB RAM
80+ GB SSD
Cost: $50 to $100+ AUD per month

Start small and scale up. Resizing a VPS takes five minutes. Beginning with a $15 server and upgrading when needed is better than over-provisioning from day one. We also strongly recommend PostgreSQL over SQLite for any production deployment. SQLite works for testing, but degrades noticeably once you have more than a handful of active workflows. PostgreSQL can run on the same server or as a managed service at minimal additional cost.

Deployment Security Requirements

Self-hosting means security is entirely your responsibility. Here are the non-negotiable areas.

Authentication

Enable basic authentication so n8n is not accessible to anyone who finds the URL. For organisations with existing identity systems, configure LDAP or SAML to enforce proper access control and audit trails. Never run n8n with authentication disabled in production.

HTTPS Everywhere

Every n8n instance must use HTTPS. Deploy a reverse proxy like Caddy or Nginx with Let’s Encrypt certificates. There is no legitimate reason to run n8n over unencrypted HTTP in production.

Firewall Lockdown

Open only ports 80 and 443 to the internet for web interface and webhooks. Restrict SSH access to known IP addresses or use key-based authentication only. Close everything else. Configure security groups or firewall rules to explicitly deny inbound traffic except where needed.

Credential Encryption

n8n encrypts stored credentials using an encryption key you set via the N8N_ENCRYPTION_KEY environment variable. Set this during initial setup and back it up securely. If you lose this key, every credential in your instance becomes inaccessible.

Network Isolation for Sensitive Deployments

For organisations handling regulated data, consider running n8n on a private network segment with VPN access. Expose only webhook endpoints through a reverse proxy while keeping the main interface behind the VPN. This is a pattern we use for most regulated clients.

Ongoing Maintenance Work

Setting up n8n is a day’s work. Maintaining it is an ongoing responsibility. Most teams underestimate this part.

Update Management

n8n releases new versions frequently, sometimes weekly. Not every update requires immediate action, but security patches do. We recommend checking for updates monthly, testing in a staging environment, and deploying to production deliberately. Pin your n8n version in your Docker Compose configuration so updates only happen when you choose to apply them, not automatically.

Backup Strategy

Automate daily database dumps stored off-server. For every client deployment, we set up automated backup scripts retaining 30 days of backups. Test your restore process quarterly. A backup you have never tested is not a backup, it is just a file that costs you storage.

Monitoring and Alerting

Know when n8n goes down before your team discovers it through missing automations. Use Uptime Robot or Better Stack for basic uptime monitoring. Configure n8n’s error workflow feature to send alerts when workflows fail. Set up log aggregation to track execution issues and performance problems.

Database Maintenance

n8n generates execution logs that grow continuously. Configure execution data pruning to automatically clean up old execution records. Without this, your database grows indefinitely and eventually slows everything down. We set retention to 90 days for most clients, with longer retention for regulated industries.

Real Cost Comparison in AUD

Here is a realistic financial comparison for different business scales.

Small Business: 500 Executions Monthly

n8n Cloud Starter: $35 AUD per month
Self-hosted VPS: $15 AUD per month
Verdict: Marginal difference. n8n Cloud is easier unless you have compliance requirements.

Growing Business: 10,000 Executions Monthly

n8n Cloud Pro: $80 AUD per month
Self-hosted VPS: $25 AUD per month
Annual savings: ~$660 AUD with no execution limits

Scaling Business: 50,000+ Executions Monthly

n8n Cloud Enterprise: $300+ AUD per month
Self-hosted VPS: $50 to $80 AUD per month
Annual savings: $2,640 to $3,000+ AUD

These figures exclude managed support costs. If you do not have in-house technical capability and need someone to manage the infrastructure, budget $200 to $500 AUD per month. Even with managed support, self-hosting at scale is typically cheaper than n8n Cloud once you pass 5,000 executions monthly. The cost difference alone funds the support overhead.

Self-Host or Use Cloud: Decision Framework

Neither approach is universally better. Use this framework to decide what fits your situation.

Choose Self-Hosting If

You operate in regulated industries with data sovereignty requirements
You handle sensitive personal, financial, or health information in your workflows
Your execution volume makes cloud pricing uneconomical (over 5,000 monthly)
You have in-house technical capability or a partner managing infrastructure
You need custom community nodes or specific server configurations

Use n8n Cloud If

You want to start quickly without managing infrastructure
Your execution volume is low to moderate
You have no compliance requirements around data location
You lack DevOps expertise internally and do not want to outsource it
You want guaranteed uptime and automatic updates handled by n8n

Many of our clients start on n8n Cloud for validation, then migrate to self-hosted as their execution volumes grow. That path works well. Deploy on cloud, prove your use case, then move to self-hosted once the scale economics justify it.

Getting Started with Deployment

If you have decided self-hosting is right for you, here is the path we recommend.

Choose your hosting method. For most businesses, a VPS with Docker is the right starting point. If you need Australian data sovereignty, select a VPS explicitly in Sydney or Melbourne.
Provision your server. Start with 2 GB RAM and a single vCPU. Vultr (Sydney), DigitalOcean (Sydney), Linode AU (Melbourne), and AWS (ap-southeast-2 Sydney) all have Australian presence. We typically use Vultr for clients wanting cost efficiency and Hetzner for clients wanting European infrastructure as a secondary option.
Set up the foundation. Install Docker, configure PostgreSQL, set your encryption key, and configure a reverse proxy with SSL. This is the step where most first-time deployments encounter issues.
Secure the instance. Configure firewall rules, enable authentication, restrict SSH access. Do not skip this step.
Configure backups and monitoring. Automated database backups and uptime monitoring from day one, not after your first data loss.
Build and test workflows. Start with one or two workflows and validate everything works before migrating your full load.
Set a maintenance routine. Monthly update checks, quarterly backup restore tests, regular review of logs and server resources.

If you would rather have experienced operators handle this, we deploy self-hosted n8n for Australian businesses and offer both one-time setup and ongoing managed support. Our n8n consulting team has deployed workflows across financial services, healthcare technology, recruitment, and professional services.

Frequently Asked Questions

Is self-hosted n8n completely free?

The n8n Community Edition is free under the Sustainable Use Licence for most business use cases. You pay for your hosting infrastructure, typically $15 to $80 AUD per month, but not for the software itself. There are no per-execution charges or licence fees for the Community Edition. The Enterprise Edition, which adds LDAP, SAML, and advanced role-based access control, requires a paid licence.

What technical knowledge is required to self-host n8n?

You need comfort with the Linux command line, Docker, and basic server administration. If you can SSH into a server, edit configuration files, and follow a deployment guide, you can set up self-hosted n8n. Ongoing maintenance requires understanding Docker container management, database backups, and basic networking. If that sounds unfamiliar, consider using n8n Cloud or working with a consultant who can handle the infrastructure.

Can I migrate from n8n Cloud to self-hosted without losing my workflows?

Yes. n8n allows you to export workflows as JSON files and import them into a different instance. Credentials must be recreated on the new instance for security reasons, and webhook URLs need updating if external services call them. We have handled this migration for several clients and it is straightforward with proper planning.

What happens if my self-hosted n8n instance goes down?

Your workflows stop executing until the instance restarts. Webhook-triggered workflows will miss incoming events unless you have a queueing mechanism. Scheduled workflows will run their next scheduled execution once the instance recovers, but will not retroactively run missed schedules. This is why uptime monitoring and a maintenance plan matter. If downtime is unacceptable for your use case, consider a Kubernetes deployment with redundancy or a managed support arrangement.

Is self-hosted n8n compliant with Australian privacy regulations?

Self-hosting gives you the ability to comply, but compliance depends on your overall implementation. Running n8n on Australian infrastructure addresses data sovereignty concerns, but you also need proper access controls, encrypted connections, audit logging, and data retention policies. If your organisation is subject to specific frameworks like the Australian Privacy Principles, APRA standards, or health records legislation, we recommend getting specific advice on your deployment configuration.

What are typical n8n server requirements and what should I expect to pay?

For small deployments with under 20 active workflows, 1 vCPU and 2 GB RAM suffices at $10 to $15 AUD per month. For medium deployments with 20 to 100 workflows, use 2 vCPU and 4 GB RAM at $20 to $40 AUD per month. For high-volume deployments over 100 workflows, use 4+ vCPU and 8+ GB RAM at $50 to $100+ AUD monthly. Always use PostgreSQL instead of SQLite for production. Start small and resize your server upward as you grow.

How often should n8n be updated?

n8n releases new versions frequently, sometimes weekly. Not every update requires immediate action. We recommend checking for updates monthly and applying security patches promptly. Always test updates in a staging environment before applying them to production. Pin your n8n version in your Docker configuration so updates only happen when you deliberately choose to apply them, never automatically.

Self-hosting n8n is a practical choice for Australian businesses with clear compliance requirements or high execution volumes. The decision is not about whether self-hosting is technically superior, but whether it makes sense for your specific situation. If you want to explore self-hosting for your organisation, book a call with our team. We are based in Brisbane and have deployed n8n across Australian financial services, healthcare, recruitment, and professional services.

Self-Host n8n: A Production Deployment Guide