Book a call Get in touch
n8n

Deploy n8n with Coolify: An Easier Self-Hosting Setup

Deploy n8n with Coolify: a self-hosted PaaS approach to running workflow automation. Setup walkthrough, costs, and the patterns we use in production.

Deploy n8n with Coolify: An Easier Self-Hosting Setup

What happens if my server fails? How do I recover?

Your workflows and execution history are stored in PostgreSQL. If you have configured Coolify’s automated backups (as we recommend), your database is backed up regularly to off-server storage. To recover, spin up a new VPS, install Coolify, restore the PostgreSQL backup, and redeploy n8n with the same encryption key. Your workflows, credentials, and execution history will all be intact. The critical piece is storing your encryption key safely outside the server. Without it, your credentials are unrecoverable even with a database backup.

Do I need DevOps experience to use Coolify?

A basic understanding of Docker and Linux helps, but Coolify abstracts most of the complexity. You do not need to write Dockerfiles or manage containers from the command line. The Docker Compose configuration in this guide is the most Docker-like thing you will interact with, and you can copy it directly. If something breaks at the infrastructure level, familiarity with docker ps, docker logs, and docker exec is useful for debugging. If you prefer to skip the technical work entirely, get in touch and we will handle the entire setup and handoff.

Can Coolify host n8n with Australian data residency?

Completely. Coolify runs on your own VPS in a region you choose. If you deploy on a Vultr or DigitalOcean instance in Sydney, your data stays in Sydney. No cloud provider logs. No data transfer to overseas regions. For Australian organisations in regulated industries (healthcare, finance, government), this data residency control is often the primary reason to self-host in the first place. Managed platforms like n8n Cloud do not offer this guarantee.

This guide is maintained by the n8n consulting team at Osher Digital. We update it as Coolify and n8n release new versions. If you are considering n8n deployment and want to discuss options specific to your organisation, book a free call with our team. We work with businesses across Australia and have deployed n8n in healthcare, finance, property, and professional services.

Containerisation forbidden: Some regulated industries do not allow containers. If your compliance requirements demand bare-metal or specifically approved virtual machines, Coolify does not work. You would need to install n8n and PostgreSQL directly on the OS.

For everyone else, Coolify works well.

Getting Help with Deployment

If you would rather have experienced people handle this, that is what we do. As n8n consultants based in Brisbane, we have deployed n8n across Australian healthcare providers, financial services firms, and property tech companies. We can have your instance running in production within a day, with backups configured, monitoring in place, and full documentation for your team.

Book a free n8n consultation if you want to discuss your deployment options, understand the trade-offs between Coolify and raw Docker, or get a time estimate and cost breakdown for your specific use case.

Frequently Asked Questions

Is Coolify actually free for n8n hosting?

Yes, Coolify is completely free open-source software. You pay only for the VPS underneath. Coolify does offer a cloud-hosted version of their platform, but for hosting n8n you want the self-hosted version on your own VPS, which costs nothing beyond the VPS bill itself.

What is the best VPS for Coolify and n8n?

For Australian teams, Vultr Sydney or DigitalOcean Sydney offer the best combination of latency and cost. Both support automated backups and integrate cleanly with Coolify. Hetzner offers better value if cost is the primary concern. Minimum specs: 2 vCPU, 4 GB RAM. We recommend 4 GB RAM even if you think 2 GB might work. The extra cost is minimal and you avoid memory pressure once you run concurrent workflows or store execution history.

Can I run other services alongside n8n on the same Coolify server?

Yes, this is one of Coolify’s strengths. You can deploy multiple services on the same server with isolated networking, separate domains, and separate SSL certificates. Common additions alongside n8n include Uptime Kuma for monitoring, NocoDB for database frontends, and MinIO for S3-compatible file storage. Just monitor resource usage. A 4 GB VPS can comfortably run n8n plus two lightweight services. If you need more capacity, add more RAM or move to a larger instance.

How much does n8n cost on Coolify per month?

Approximately AUD $40-60 per month for a production-ready, fully backed up deployment. This covers the VPS (AUD $36-42), backup storage (negligible), and nothing else. No per-execution fees, no overage charges, no hidden costs. Your bill is predictable and fixed regardless of how many workflows you run or how often they execute.

What happens if my server fails? How do I recover?

Your workflows and execution history are stored in PostgreSQL. If you have configured Coolify’s automated backups (as we recommend), your database is backed up regularly to off-server storage. To recover, spin up a new VPS, install Coolify, restore the PostgreSQL backup, and redeploy n8n with the same encryption key. Your workflows, credentials, and execution history will all be intact. The critical piece is storing your encryption key safely outside the server. Without it, your credentials are unrecoverable even with a database backup.

Do I need DevOps experience to use Coolify?

A basic understanding of Docker and Linux helps, but Coolify abstracts most of the complexity. You do not need to write Dockerfiles or manage containers from the command line. The Docker Compose configuration in this guide is the most Docker-like thing you will interact with, and you can copy it directly. If something breaks at the infrastructure level, familiarity with docker ps, docker logs, and docker exec is useful for debugging. If you prefer to skip the technical work entirely, get in touch and we will handle the entire setup and handoff.

Can Coolify host n8n with Australian data residency?

Completely. Coolify runs on your own VPS in a region you choose. If you deploy on a Vultr or DigitalOcean instance in Sydney, your data stays in Sydney. No cloud provider logs. No data transfer to overseas regions. For Australian organisations in regulated industries (healthcare, finance, government), this data residency control is often the primary reason to self-host in the first place. Managed platforms like n8n Cloud do not offer this guarantee.

This guide is maintained by the n8n consulting team at Osher Digital. We update it as Coolify and n8n release new versions. If you are considering n8n deployment and want to discuss options specific to your organisation, book a free call with our team. We work with businesses across Australia and have deployed n8n in healthcare, finance, property, and professional services.

Updated May 2026. Refreshed for commercial intent queries and expanded FAQ coverage for deployment decision-making.

Self-hosting n8n gives you what managed platforms cannot: complete data control, execution limits that vanish, and the ability to install community nodes without restrictions. We have deployed n8n across Australian healthcare providers, property tech firms, and financial services companies that chose self-hosting specifically because they could not tolerate per-execution pricing at scale.

The catch is infrastructure. Raw Docker deployments mean writing Compose files, configuring reverse proxies, managing SSL certificates, handling backups yourself. Most teams do not have a DevOps engineer on staff. Coolify fixes this. It is a self-hosted PaaS (Platform as a Service) that lets you deploy applications, databases, and services through a clean web interface. Think Heroku or Vercel, except you own the hardware and there are no per-app fees.

We have built n8n deployments on Coolify for dozens of clients now. It is become our standard recommendation for Australian organisations that want n8n running reliably without ops overhead. This guide walks through the entire process, from VPS choice through production hardening with SSL and automated backups.

This guide is aimed at technical decision-makers and developers evaluating n8n deployment options and looking to understand the real costs and effort involved in self-hosting. We have also published guides on raw Docker self-hosting and Docker Compose specifically, which provide deeper technical detail for teams that need more control than Coolify provides.

What Coolify Actually Is

Coolify is open-source deployment infrastructure that runs on your VPS. You install it once, and it handles the rest: pulling application images, networking containers, provisioning SSL certificates, managing databases, scheduling backups, handling rollbacks. It is a private PaaS, which is a layer of abstraction above raw Docker but below fully managed cloud platforms like Heroku or Railway.

Where Coolify shines for n8n is that it automates the operational tasks that kill DIY self-hosting setups. You do not manually update certificates. You do not write backup scripts and wonder if they actually worked. You do not configure Nginx. The platform handles it, and you get a dashboard where you can monitor everything without SSH.

  • One-click deployment of Docker-based applications and databases
  • PostgreSQL, MySQL, Redis provisioning through the UI (no separate installation)
  • Automatic SSL via Let’s Encrypt with renewal handled by Coolify
  • Persistent volumes with Docker management built in
  • Scheduled backups with S3-compatible destinations (Backblaze B2, AWS S3, MinIO)
  • Container logs, resource monitoring, deployment history in one dashboard
  • Rollback to any prior deployment version in seconds
  • Multiple applications per server with isolated networking

The project is actively maintained with a solid community, and the self-hosted version is free. You pay only for the VPS underneath.

Coolify vs Dokku vs CapRover vs Raw Docker

Several platforms claim to simplify self-hosted deployments. It is worth understanding where each sits and when Coolify makes sense.

Raw Docker / Docker Compose: Maximum control, zero abstraction. You write YAML, manage networking, handle SSL renewal scripts, back up volumes manually. This is the right choice if you have a DevOps engineer on staff and need very specific configurations that a platform would constrain. For n8n specifically, most teams find this overkill once they realise they need SSL, database monitoring, and reliable backups.

Dokku: A lightweight PaaS in approximately 100MB of code. Dokku is excellent if you want git-push-to-deploy and do not need fancy features. The downside is that Dokku’s database management and backup story are thin compared to Coolify. You will still write scripts for important stuff. Dokku is often deployed by agencies for client projects where they want zero infrastructure cost. It works, but it requires more ops knowledge than Coolify to run reliably.

CapRover: A Docker-based platform closer in spirit to Coolify. CapRover is mature and has a good UI. The main limitation is that CapRover development has slowed. Coolify is currently more actively maintained and has broader integrations (Coolify’s backup destinations are more flexible, for example). If you prefer CapRover’s interface, it will work fine for n8n. We have deployed both and do not see a major difference in outcomes.

Managed platforms (Fly.io, Railway, Render): These platforms handle everything but charge per resource (CPU, RAM, storage, bandwidth). A small n8n instance costs roughly $50-80 AUD monthly before execution fees. Scaling costs money linearly. There is also vendor lock-in and data residency questions (your data is on their servers in their region). For Australian organisations with data sovereignty concerns, this is a non-starter. Managed platforms win on simplicity and zero ops. They lose on cost and control.

n8n Cloud: The official hosted n8n. Start free. Pay per execution once you exceed limits. Costs become unpredictable at scale. Your data lives on n8n’s servers in their region. No community nodes. This is fine for individuals and small teams testing workflows. For any production use by a business, the combination of per-execution pricing and data residency concerns makes self-hosting the obvious choice.

For most Australian organisations that want n8n running reliably without hiring a DevOps engineer, Coolify lands in the sweet spot. You own the infrastructure. You own the data. You get a clean UI for common operations. You pay a fixed VPS cost and nothing else.

Prerequisites: VPS Sizing and Cost

Before you start, you need the right VPS. Undersizing is a common mistake. We recommend a minimum of 2 vCPUs and 4 GB RAM. This gives Coolify room to breathe alongside n8n, PostgreSQL, and monitoring services. You can deploy to 2 GB RAM in a pinch for light workloads (a handful of workflows), but you will hit memory pressure once you run more than a few concurrent workflows or store significant execution history.

For Australian teams, the best VPS providers are those with data centres in Sydney or nearby Asia-Pacific regions. We consistently recommend three options.

  • Vultr (Sydney): 2 vCPU, 4 GB RAM, 80 GB SSD is approximately AUD $36 per month. 4 vCPU, 8 GB RAM is approximately AUD $72 per month. Reliable, good Australian bandwidth, straightforward API for automating deployments.
  • DigitalOcean (Sydney): Similar pricing to Vultr at approximately AUD $42 per month for the base 2 vCPU / 4 GB configuration. Larger community than Vultr, which means more guides and open-source integrations. DigitalOcean also offers S3-compatible spaces for backups at lower cost than AWS.
  • Hetzner (Singapore or planned Sydney): Significantly cheaper at approximately AUD $20 per month for 4 vCPU / 8 GB configurations due to infrastructure economics in Asia. Network latency to Sydney is still excellent. If you are cost-conscious, Hetzner offers the best value.

Beyond the VPS, you will need a domain (or subdomain) pointed at your server, SSH access with sudo privileges, and ideally a fresh Ubuntu 22.04 or 24.04 instance. Coolify installs cleanly on a blank server and can conflict with other services on existing machines.

Installation and Initial Setup

Coolify installation is a single command. SSH into your VPS and run:

curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash

This script installs Docker if missing, pulls Coolify’s containers, and starts the platform. The process takes two to three minutes. Once complete, navigate to http://YOUR_SERVER_IP:8000 and create your admin account.

During initial setup, Coolify asks you to configure a server. Select “Localhost” since you are running everything on the same machine. Coolify validates the Docker connection and confirms it can communicate with the daemon.

After setup, point your Coolify dashboard domain (e.g., coolify.yourdomain.com.au) at your server and configure it in Coolify under Settings > General > Instance’s Domain. Coolify automatically provisions an SSL certificate for its own dashboard via Let’s Encrypt.

Deploying PostgreSQL Database

n8n defaults to SQLite, but SQLite degrades under concurrent load and makes your instance fragile once execution history grows beyond a few thousand records. We always configure PostgreSQL for production workloads. PostgreSQL handles concurrent access cleanly and scales with your data. For the cost of a few milliseconds of latency (which users never notice), you get reliability that matters when your workflows run business-critical operations.

In the Coolify dashboard, create a new project (e.g., “n8n Production”). Within the project, click + New > Database and select PostgreSQL. Configure it with database name n8n, username n8n, and a strong password that you save somewhere secure. You will need this password for n8n’s environment variables later.

Click Deploy. Coolify handles container creation, networking, and persistent volume attachment. The database will be accessible to other services in the same project via Coolify’s internal Docker network. Note the internal connection URL that Coolify displays after deployment (it looks like postgresql://n8n:password@postgresql-xxxxx:5432/n8n). You will use this when configuring n8n.

Deploying n8n Through Coolify

In the same Coolify project, click + New > Docker Compose. You will see an editor for your docker-compose.yml. Paste this configuration and adjust as needed:

services:
  n8n:
    image: n8nio/n8n:1.75.0
    restart: always
    ports:
      - "5678:5678"
    environment:
      - N8N_HOST=${N8N_HOST}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - WEBHOOK_URL=https://${N8N_HOST}/
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=${DB_HOST}
      - DB_POSTGRESDB_PORT=5432
      - DB_POSTGRESDB_DATABASE=${DB_NAME}
      - DB_POSTGRESDB_USER=${DB_USER}
      - DB_POSTGRESDB_PASSWORD=${DB_PASSWORD}
      - N8N_ENCRYPTION_KEY=${ENCRYPTION_KEY}
      - EXECUTIONS_DATA_PRUNE=true
      - EXECUTIONS_DATA_MAX_AGE=168
      - GENERIC_TIMEZONE=Australia/Brisbane
    volumes:
      - n8n_data:/home/node/.n8n
volumes:
  n8n_data:

Note on the image tag: We pin to version 1.75.0 rather than using latest. This is deliberate. n8n occasionally introduces breaking changes in minor updates that cause workflow failures. Pinning versions lets you test updates on a staging instance before rolling them to production. Check the n8n release notes before upgrading.

Save the Compose file and proceed to environment variables.

Environment Variables and Encryption

In Coolify’s service settings, navigate to Environment Variables and add the following:

  • N8N_HOST = n8n.yourdomain.com.au (your n8n subdomain)
  • DB_HOST = Internal hostname from your PostgreSQL deployment (e.g., postgresql-xxxxx)
  • DB_NAME = n8n
  • DB_USER = n8n
  • DB_PASSWORD = The PostgreSQL password you generated earlier
  • ENCRYPTION_KEY = A random 32+ character string generated with openssl rand -hex 32

The encryption key deserves emphasis. This key encrypts all credentials stored in n8n (API keys, database passwords, OAuth tokens). If you lose this key, you lose access to those credentials even if you have a database backup. We strongly recommend storing this key in a password manager or secrets vault outside of your server. If your server fails and you need to restore from backup, you will need this key to decrypt your credentials.

The GENERIC_TIMEZONE setting in the Docker Compose file is set to Australia/Brisbane. If you are in a different Australian timezone (Melbourne, Sydney, Perth), change this to Australia/Melbourne, Australia/Sydney, or Australia/Perth respectively. This affects how n8n interprets cron triggers and scheduled workflows. A workflow set to trigger at 9am local time will fire at the wrong time if the timezone is wrong.

SSL, Domain, and Public Access

In the n8n service settings, go to the Domains section and enter your domain: https://n8n.yourdomain.com.au. Ensure your DNS A record points to your VPS IP address. Coolify will automatically request and install a Let’s Encrypt SSL certificate. There are no configuration files to edit, no Certbot to manage, no cron jobs for renewal. Coolify handles it all.

Once the domain is configured, deploy the service. After it is running, navigate to https://n8n.yourdomain.com.au and you should see the n8n setup screen asking you to create your owner account.

At this point, your n8n instance is publicly accessible, encrypted with TLS, backed by PostgreSQL, and running inside Coolify’s managed environment. The core deployment is complete.

Persistent Storage Volumes

The Docker Compose configuration includes a named volume (n8n_data) mapped to /home/node/.n8n. This is where n8n stores uploaded files, community node installations, and local configuration. Coolify manages Docker volumes and ensures they persist across container restarts and redeployments.

However, volumes are tied to the host machine. If your server fails, the volume data is lost unless you have backups. In production, verify the volume is correctly mounted by checking the Persistent Storage section in Coolify’s service settings. You should see the volume listed with its mount path. This is where uploaded file attachments from workflow executions live, so losing this volume means losing any files processed by your workflows.

Automated Backups and Disaster Recovery

Backups are where most self-hosted setups fail operationally. Coolify has strong backup support, which is one reason we recommend it over raw Docker.

PostgreSQL database backups: Navigate to your PostgreSQL service and go to the Backups tab. Configure automated backups with daily scheduling. For production workflows that process critical data, consider hourly. Storage is cheap. Data loss is not.

Set up a backup destination under Destinations in Coolify’s settings. We recommend S3-compatible storage (Backblaze B2 costs approximately AUD $0.008 per GB monthly for storage, which is negligible for database backups). Configure that destination on your PostgreSQL backup schedule. Your backups now live off-server automatically.

What backups do not cover: The n8n data volume (uploaded files, community nodes) and your encryption key are not backed up automatically. For the volume, set up a cron job on your host that copies the Docker volume contents to your backup destination. For the encryption key, store it in a password manager. This is the critical piece. Without it, your database backup is encrypted but unrecoverable.

To recover from a failure: spin up a new VPS, install Coolify, restore the PostgreSQL backup, redeploy n8n with the same encryption key, and restore the n8n volume. Your workflows, credentials, and execution history will all be intact. This process typically takes 30 minutes and has never failed us in practice.

Monitoring, Logs, and Updates

Coolify’s dashboard provides real-time container logs, CPU and memory graphs, and a deployment history showing every version change. This visibility is invaluable when debugging webhook issues or tracking down why execution suddenly spiked.

To update n8n, change the image tag in your Docker Compose configuration (e.g., from 1.75.0 to 1.76.0) and click Redeploy. Coolify pulls the new image, creates a fresh container, and switches traffic to it. If something breaks, roll back to the previous version through the deployment history.

Our recommendation: Test updates on a staging instance first. We have seen n8n introduce breaking changes in minor version bumps. Pinning versions and testing deliberately prevents unpleasant surprises in production.

Cost Breakdown, Australian Context

Here is the real cost of running n8n on Coolify with Australian data residency or local latency:

  • Vultr Sydney: 2 vCPU, 4 GB RAM, 80 GB SSD is approximately AUD $36 per month.
  • DigitalOcean Sydney: 2 vCPU, 4 GB RAM, 80 GB SSD is approximately AUD $42 per month. Also offered: S3-compatible spaces at AUD $0.003 per GB per month for backups.
  • Database backups: Backblaze B2 at approximately AUD $0.008 per GB per month. Negligible for typical database sizes.
  • Optional VPS snapshots: Typically 20 per cent of VPS cost for automated snapshots. Useful but not essential if you have database backups in place.

Total monthly cost: AUD $40-60 for a production-ready, fully backed up, SSL-encrypted n8n instance processing hundreds of workflows. No per-execution fees. No surprise bills as your workflow count grows.

Compare this to n8n Cloud (approximately AUD $110 monthly for Pro plus overage fees), Zapier (hundreds of dollars monthly for comparable volume), or managed platforms like Railway (AUD $50-80 monthly plus per-resource overages as you scale). Self-hosting with Coolify becomes the obvious choice for any organisation running more than a handful of production workflows.

Scaling and High Availability

As your workflow count grows, Coolify provides several scaling paths:

  • Vertical scaling: Upgrade your VPS to a larger instance. Coolify does not care about underlying hardware. Stop, resize, restart. Simple.
  • Worker mode: n8n supports queue mode with separate main and worker instances. Deploy multiple n8n worker containers through Coolify, all connected to the same PostgreSQL database and a Redis instance (also deployable through Coolify).
  • Service separation: Move PostgreSQL to a dedicated server for demanding workloads. Coolify supports managing remote servers, so your dashboard stays unified.

For most Australian small and medium businesses, a single 4 GB RAM VPS handles everything comfortably. We typically recommend considering vertical scaling when you hit 100+ active workflows or when execution data throughput pushes CPU above 70 per cent consistently.

When Coolify Is Not the Right Choice

Coolify is excellent for most cases, but there are scenarios where it does not fit.

Enterprise with strict change control: If your organisation has formal change request processes and audit requirements, Coolify’s flexibility can work against you. You need infrastructure as code with peer review and approval gates. Raw Docker with version-controlled Compose files is better. So is Kubernetes if you are truly enterprise-scale.

Multi-region high availability: If you need n8n running in multiple regions with failover, Coolify on a single VPS is not the answer. You need Kubernetes or a managed orchestration platform. This is rare for most organisations.

Containerisation forbidden: Some regulated industries do not allow containers. If your compliance requirements demand bare-metal or specifically approved virtual machines, Coolify does not work. You would need to install n8n and PostgreSQL directly on the OS.

For everyone else, Coolify works well.

Getting Help with Deployment

If you would rather have experienced people handle this, that is what we do. As n8n consultants based in Brisbane, we have deployed n8n across Australian healthcare providers, financial services firms, and property tech companies. We can have your instance running in production within a day, with backups configured, monitoring in place, and full documentation for your team.

Book a free n8n consultation if you want to discuss your deployment options, understand the trade-offs between Coolify and raw Docker, or get a time estimate and cost breakdown for your specific use case.

Frequently Asked Questions

Is Coolify actually free for n8n hosting?

Yes, Coolify is completely free open-source software. You pay only for the VPS underneath. Coolify does offer a cloud-hosted version of their platform, but for hosting n8n you want the self-hosted version on your own VPS, which costs nothing beyond the VPS bill itself.

What is the best VPS for Coolify and n8n?

For Australian teams, Vultr Sydney or DigitalOcean Sydney offer the best combination of latency and cost. Both support automated backups and integrate cleanly with Coolify. Hetzner offers better value if cost is the primary concern. Minimum specs: 2 vCPU, 4 GB RAM. We recommend 4 GB RAM even if you think 2 GB might work. The extra cost is minimal and you avoid memory pressure once you run concurrent workflows or store execution history.

Can I run other services alongside n8n on the same Coolify server?

Yes, this is one of Coolify’s strengths. You can deploy multiple services on the same server with isolated networking, separate domains, and separate SSL certificates. Common additions alongside n8n include Uptime Kuma for monitoring, NocoDB for database frontends, and MinIO for S3-compatible file storage. Just monitor resource usage. A 4 GB VPS can comfortably run n8n plus two lightweight services. If you need more capacity, add more RAM or move to a larger instance.

How much does n8n cost on Coolify per month?

Approximately AUD $40-60 per month for a production-ready, fully backed up deployment. This covers the VPS (AUD $36-42), backup storage (negligible), and nothing else. No per-execution fees, no overage charges, no hidden costs. Your bill is predictable and fixed regardless of how many workflows you run or how often they execute.

What happens if my server fails? How do I recover?

Your workflows and execution history are stored in PostgreSQL. If you have configured Coolify’s automated backups (as we recommend), your database is backed up regularly to off-server storage. To recover, spin up a new VPS, install Coolify, restore the PostgreSQL backup, and redeploy n8n with the same encryption key. Your workflows, credentials, and execution history will all be intact. The critical piece is storing your encryption key safely outside the server. Without it, your credentials are unrecoverable even with a database backup.

Do I need DevOps experience to use Coolify?

A basic understanding of Docker and Linux helps, but Coolify abstracts most of the complexity. You do not need to write Dockerfiles or manage containers from the command line. The Docker Compose configuration in this guide is the most Docker-like thing you will interact with, and you can copy it directly. If something breaks at the infrastructure level, familiarity with docker ps, docker logs, and docker exec is useful for debugging. If you prefer to skip the technical work entirely, get in touch and we will handle the entire setup and handoff.

Can Coolify host n8n with Australian data residency?

Completely. Coolify runs on your own VPS in a region you choose. If you deploy on a Vultr or DigitalOcean instance in Sydney, your data stays in Sydney. No cloud provider logs. No data transfer to overseas regions. For Australian organisations in regulated industries (healthcare, finance, government), this data residency control is often the primary reason to self-host in the first place. Managed platforms like n8n Cloud do not offer this guarantee.

This guide is maintained by the n8n consulting team at Osher Digital. We update it as Coolify and n8n release new versions. If you are considering n8n deployment and want to discuss options specific to your organisation, book a free call with our team. We work with businesses across Australia and have deployed n8n in healthcare, finance, property, and professional services.

Containerisation forbidden: Some regulated industries do not allow containers. If your compliance requirements demand bare-metal or specifically approved virtual machines, Coolify does not work. You would need to install n8n and PostgreSQL directly on the OS.

For everyone else, Coolify works well.

Getting Help with Deployment

If you would rather have experienced people handle this, that is what we do. As n8n consultants based in Brisbane, we have deployed n8n across Australian healthcare providers, financial services firms, and property tech companies. We can have your instance running in production within a day, with backups configured, monitoring in place, and full documentation for your team.

Book a free n8n consultation if you want to discuss your deployment options, understand the trade-offs between Coolify and raw Docker, or get a time estimate and cost breakdown for your specific use case.

Frequently Asked Questions

Is Coolify actually free for n8n hosting?

Yes, Coolify is completely free open-source software. You pay only for the VPS underneath. Coolify does offer a cloud-hosted version of their platform, but for hosting n8n you want the self-hosted version on your own VPS, which costs nothing beyond the VPS bill itself.

What is the best VPS for Coolify and n8n?

For Australian teams, Vultr Sydney or DigitalOcean Sydney offer the best combination of latency and cost. Both support automated backups and integrate cleanly with Coolify. Hetzner offers better value if cost is the primary concern. Minimum specs: 2 vCPU, 4 GB RAM. We recommend 4 GB RAM even if you think 2 GB might work. The extra cost is minimal and you avoid memory pressure once you run concurrent workflows or store execution history.

Can I run other services alongside n8n on the same Coolify server?

Yes, this is one of Coolify’s strengths. You can deploy multiple services on the same server with isolated networking, separate domains, and separate SSL certificates. Common additions alongside n8n include Uptime Kuma for monitoring, NocoDB for database frontends, and MinIO for S3-compatible file storage. Just monitor resource usage. A 4 GB VPS can comfortably run n8n plus two lightweight services. If you need more capacity, add more RAM or move to a larger instance.

How much does n8n cost on Coolify per month?

Approximately AUD $40-60 per month for a production-ready, fully backed up deployment. This covers the VPS (AUD $36-42), backup storage (negligible), and nothing else. No per-execution fees, no overage charges, no hidden costs. Your bill is predictable and fixed regardless of how many workflows you run or how often they execute.

What happens if my server fails? How do I recover?

Your workflows and execution history are stored in PostgreSQL. If you have configured Coolify’s automated backups (as we recommend), your database is backed up regularly to off-server storage. To recover, spin up a new VPS, install Coolify, restore the PostgreSQL backup, and redeploy n8n with the same encryption key. Your workflows, credentials, and execution history will all be intact. The critical piece is storing your encryption key safely outside the server. Without it, your credentials are unrecoverable even with a database backup.

Do I need DevOps experience to use Coolify?

A basic understanding of Docker and Linux helps, but Coolify abstracts most of the complexity. You do not need to write Dockerfiles or manage containers from the command line. The Docker Compose configuration in this guide is the most Docker-like thing you will interact with, and you can copy it directly. If something breaks at the infrastructure level, familiarity with docker ps, docker logs, and docker exec is useful for debugging. If you prefer to skip the technical work entirely, get in touch and we will handle the entire setup and handoff.

Can Coolify host n8n with Australian data residency?

Completely. Coolify runs on your own VPS in a region you choose. If you deploy on a Vultr or DigitalOcean instance in Sydney, your data stays in Sydney. No cloud provider logs. No data transfer to overseas regions. For Australian organisations in regulated industries (healthcare, finance, government), this data residency control is often the primary reason to self-host in the first place. Managed platforms like n8n Cloud do not offer this guarantee.

This guide is maintained by the n8n consulting team at Osher Digital. We update it as Coolify and n8n release new versions. If you are considering n8n deployment and want to discuss options specific to your organisation, book a free call with our team. We work with businesses across Australia and have deployed n8n in healthcare, finance, property, and professional services.

Updated May 2026. Refreshed for commercial intent queries and expanded FAQ coverage for deployment decision-making.

Self-hosting n8n gives you what managed platforms cannot: complete data control, execution limits that vanish, and the ability to install community nodes without restrictions. We have deployed n8n across Australian healthcare providers, property tech firms, and financial services companies that chose self-hosting specifically because they could not tolerate per-execution pricing at scale.

The catch is infrastructure. Raw Docker deployments mean writing Compose files, configuring reverse proxies, managing SSL certificates, handling backups yourself. Most teams do not have a DevOps engineer on staff. Coolify fixes this. It is a self-hosted PaaS (Platform as a Service) that lets you deploy applications, databases, and services through a clean web interface. Think Heroku or Vercel, except you own the hardware and there are no per-app fees.

We have built n8n deployments on Coolify for dozens of clients now. It is become our standard recommendation for Australian organisations that want n8n running reliably without ops overhead. This guide walks through the entire process, from VPS choice through production hardening with SSL and automated backups.

This guide is aimed at technical decision-makers and developers evaluating n8n deployment options and looking to understand the real costs and effort involved in self-hosting. We have also published guides on raw Docker self-hosting and Docker Compose specifically, which provide deeper technical detail for teams that need more control than Coolify provides.

What Coolify Actually Is

Coolify is open-source deployment infrastructure that runs on your VPS. You install it once, and it handles the rest: pulling application images, networking containers, provisioning SSL certificates, managing databases, scheduling backups, handling rollbacks. It is a private PaaS, which is a layer of abstraction above raw Docker but below fully managed cloud platforms like Heroku or Railway.

Where Coolify shines for n8n is that it automates the operational tasks that kill DIY self-hosting setups. You do not manually update certificates. You do not write backup scripts and wonder if they actually worked. You do not configure Nginx. The platform handles it, and you get a dashboard where you can monitor everything without SSH.

  • One-click deployment of Docker-based applications and databases
  • PostgreSQL, MySQL, Redis provisioning through the UI (no separate installation)
  • Automatic SSL via Let’s Encrypt with renewal handled by Coolify
  • Persistent volumes with Docker management built in
  • Scheduled backups with S3-compatible destinations (Backblaze B2, AWS S3, MinIO)
  • Container logs, resource monitoring, deployment history in one dashboard
  • Rollback to any prior deployment version in seconds
  • Multiple applications per server with isolated networking

The project is actively maintained with a solid community, and the self-hosted version is free. You pay only for the VPS underneath.

Coolify vs Dokku vs CapRover vs Raw Docker

Several platforms claim to simplify self-hosted deployments. It is worth understanding where each sits and when Coolify makes sense.

Raw Docker / Docker Compose: Maximum control, zero abstraction. You write YAML, manage networking, handle SSL renewal scripts, back up volumes manually. This is the right choice if you have a DevOps engineer on staff and need very specific configurations that a platform would constrain. For n8n specifically, most teams find this overkill once they realise they need SSL, database monitoring, and reliable backups.

Dokku: A lightweight PaaS in approximately 100MB of code. Dokku is excellent if you want git-push-to-deploy and do not need fancy features. The downside is that Dokku’s database management and backup story are thin compared to Coolify. You will still write scripts for important stuff. Dokku is often deployed by agencies for client projects where they want zero infrastructure cost. It works, but it requires more ops knowledge than Coolify to run reliably.

CapRover: A Docker-based platform closer in spirit to Coolify. CapRover is mature and has a good UI. The main limitation is that CapRover development has slowed. Coolify is currently more actively maintained and has broader integrations (Coolify’s backup destinations are more flexible, for example). If you prefer CapRover’s interface, it will work fine for n8n. We have deployed both and do not see a major difference in outcomes.

Managed platforms (Fly.io, Railway, Render): These platforms handle everything but charge per resource (CPU, RAM, storage, bandwidth). A small n8n instance costs roughly $50-80 AUD monthly before execution fees. Scaling costs money linearly. There is also vendor lock-in and data residency questions (your data is on their servers in their region). For Australian organisations with data sovereignty concerns, this is a non-starter. Managed platforms win on simplicity and zero ops. They lose on cost and control.

n8n Cloud: The official hosted n8n. Start free. Pay per execution once you exceed limits. Costs become unpredictable at scale. Your data lives on n8n’s servers in their region. No community nodes. This is fine for individuals and small teams testing workflows. For any production use by a business, the combination of per-execution pricing and data residency concerns makes self-hosting the obvious choice.

For most Australian organisations that want n8n running reliably without hiring a DevOps engineer, Coolify lands in the sweet spot. You own the infrastructure. You own the data. You get a clean UI for common operations. You pay a fixed VPS cost and nothing else.

Prerequisites: VPS Sizing and Cost

Before you start, you need the right VPS. Undersizing is a common mistake. We recommend a minimum of 2 vCPUs and 4 GB RAM. This gives Coolify room to breathe alongside n8n, PostgreSQL, and monitoring services. You can deploy to 2 GB RAM in a pinch for light workloads (a handful of workflows), but you will hit memory pressure once you run more than a few concurrent workflows or store significant execution history.

For Australian teams, the best VPS providers are those with data centres in Sydney or nearby Asia-Pacific regions. We consistently recommend three options.

  • Vultr (Sydney): 2 vCPU, 4 GB RAM, 80 GB SSD is approximately AUD $36 per month. 4 vCPU, 8 GB RAM is approximately AUD $72 per month. Reliable, good Australian bandwidth, straightforward API for automating deployments.
  • DigitalOcean (Sydney): Similar pricing to Vultr at approximately AUD $42 per month for the base 2 vCPU / 4 GB configuration. Larger community than Vultr, which means more guides and open-source integrations. DigitalOcean also offers S3-compatible spaces for backups at lower cost than AWS.
  • Hetzner (Singapore or planned Sydney): Significantly cheaper at approximately AUD $20 per month for 4 vCPU / 8 GB configurations due to infrastructure economics in Asia. Network latency to Sydney is still excellent. If you are cost-conscious, Hetzner offers the best value.

Beyond the VPS, you will need a domain (or subdomain) pointed at your server, SSH access with sudo privileges, and ideally a fresh Ubuntu 22.04 or 24.04 instance. Coolify installs cleanly on a blank server and can conflict with other services on existing machines.

Installation and Initial Setup

Coolify installation is a single command. SSH into your VPS and run:

curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash

This script installs Docker if missing, pulls Coolify’s containers, and starts the platform. The process takes two to three minutes. Once complete, navigate to http://YOUR_SERVER_IP:8000 and create your admin account.

During initial setup, Coolify asks you to configure a server. Select “Localhost” since you are running everything on the same machine. Coolify validates the Docker connection and confirms it can communicate with the daemon.

After setup, point your Coolify dashboard domain (e.g., coolify.yourdomain.com.au) at your server and configure it in Coolify under Settings > General > Instance’s Domain. Coolify automatically provisions an SSL certificate for its own dashboard via Let’s Encrypt.

Deploying PostgreSQL Database

n8n defaults to SQLite, but SQLite degrades under concurrent load and makes your instance fragile once execution history grows beyond a few thousand records. We always configure PostgreSQL for production workloads. PostgreSQL handles concurrent access cleanly and scales with your data. For the cost of a few milliseconds of latency (which users never notice), you get reliability that matters when your workflows run business-critical operations.

In the Coolify dashboard, create a new project (e.g., “n8n Production”). Within the project, click + New > Database and select PostgreSQL. Configure it with database name n8n, username n8n, and a strong password that you save somewhere secure. You will need this password for n8n’s environment variables later.

Click Deploy. Coolify handles container creation, networking, and persistent volume attachment. The database will be accessible to other services in the same project via Coolify’s internal Docker network. Note the internal connection URL that Coolify displays after deployment (it looks like postgresql://n8n:password@postgresql-xxxxx:5432/n8n). You will use this when configuring n8n.

Deploying n8n Through Coolify

In the same Coolify project, click + New > Docker Compose. You will see an editor for your docker-compose.yml. Paste this configuration and adjust as needed:

services:
  n8n:
    image: n8nio/n8n:1.75.0
    restart: always
    ports:
      - "5678:5678"
    environment:
      - N8N_HOST=${N8N_HOST}
      - N8N_PORT=5678
      - N8N_PROTOCOL=https
      - WEBHOOK_URL=https://${N8N_HOST}/
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=${DB_HOST}
      - DB_POSTGRESDB_PORT=5432
      - DB_POSTGRESDB_DATABASE=${DB_NAME}
      - DB_POSTGRESDB_USER=${DB_USER}
      - DB_POSTGRESDB_PASSWORD=${DB_PASSWORD}
      - N8N_ENCRYPTION_KEY=${ENCRYPTION_KEY}
      - EXECUTIONS_DATA_PRUNE=true
      - EXECUTIONS_DATA_MAX_AGE=168
      - GENERIC_TIMEZONE=Australia/Brisbane
    volumes:
      - n8n_data:/home/node/.n8n
volumes:
  n8n_data:

Note on the image tag: We pin to version 1.75.0 rather than using latest. This is deliberate. n8n occasionally introduces breaking changes in minor updates that cause workflow failures. Pinning versions lets you test updates on a staging instance before rolling them to production. Check the n8n release notes before upgrading.

Save the Compose file and proceed to environment variables.

Environment Variables and Encryption

In Coolify’s service settings, navigate to Environment Variables and add the following:

  • N8N_HOST = n8n.yourdomain.com.au (your n8n subdomain)
  • DB_HOST = Internal hostname from your PostgreSQL deployment (e.g., postgresql-xxxxx)
  • DB_NAME = n8n
  • DB_USER = n8n
  • DB_PASSWORD = The PostgreSQL password you generated earlier
  • ENCRYPTION_KEY = A random 32+ character string generated with openssl rand -hex 32

The encryption key deserves emphasis. This key encrypts all credentials stored in n8n (API keys, database passwords, OAuth tokens). If you lose this key, you lose access to those credentials even if you have a database backup. We strongly recommend storing this key in a password manager or secrets vault outside of your server. If your server fails and you need to restore from backup, you will need this key to decrypt your credentials.

The GENERIC_TIMEZONE setting in the Docker Compose file is set to Australia/Brisbane. If you are in a different Australian timezone (Melbourne, Sydney, Perth), change this to Australia/Melbourne, Australia/Sydney, or Australia/Perth respectively. This affects how n8n interprets cron triggers and scheduled workflows. A workflow set to trigger at 9am local time will fire at the wrong time if the timezone is wrong.

SSL, Domain, and Public Access

In the n8n service settings, go to the Domains section and enter your domain: https://n8n.yourdomain.com.au. Ensure your DNS A record points to your VPS IP address. Coolify will automatically request and install a Let’s Encrypt SSL certificate. There are no configuration files to edit, no Certbot to manage, no cron jobs for renewal. Coolify handles it all.

Once the domain is configured, deploy the service. After it is running, navigate to https://n8n.yourdomain.com.au and you should see the n8n setup screen asking you to create your owner account.

At this point, your n8n instance is publicly accessible, encrypted with TLS, backed by PostgreSQL, and running inside Coolify’s managed environment. The core deployment is complete.

Persistent Storage Volumes

The Docker Compose configuration includes a named volume (n8n_data) mapped to /home/node/.n8n. This is where n8n stores uploaded files, community node installations, and local configuration. Coolify manages Docker volumes and ensures they persist across container restarts and redeployments.

However, volumes are tied to the host machine. If your server fails, the volume data is lost unless you have backups. In production, verify the volume is correctly mounted by checking the Persistent Storage section in Coolify’s service settings. You should see the volume listed with its mount path. This is where uploaded file attachments from workflow executions live, so losing this volume means losing any files processed by your workflows.

Automated Backups and Disaster Recovery

Backups are where most self-hosted setups fail operationally. Coolify has strong backup support, which is one reason we recommend it over raw Docker.

PostgreSQL database backups: Navigate to your PostgreSQL service and go to the Backups tab. Configure automated backups with daily scheduling. For production workflows that process critical data, consider hourly. Storage is cheap. Data loss is not.

Set up a backup destination under Destinations in Coolify’s settings. We recommend S3-compatible storage (Backblaze B2 costs approximately AUD $0.008 per GB monthly for storage, which is negligible for database backups). Configure that destination on your PostgreSQL backup schedule. Your backups now live off-server automatically.

What backups do not cover: The n8n data volume (uploaded files, community nodes) and your encryption key are not backed up automatically. For the volume, set up a cron job on your host that copies the Docker volume contents to your backup destination. For the encryption key, store it in a password manager. This is the critical piece. Without it, your database backup is encrypted but unrecoverable.

To recover from a failure: spin up a new VPS, install Coolify, restore the PostgreSQL backup, redeploy n8n with the same encryption key, and restore the n8n volume. Your workflows, credentials, and execution history will all be intact. This process typically takes 30 minutes and has never failed us in practice.

Monitoring, Logs, and Updates

Coolify’s dashboard provides real-time container logs, CPU and memory graphs, and a deployment history showing every version change. This visibility is invaluable when debugging webhook issues or tracking down why execution suddenly spiked.

To update n8n, change the image tag in your Docker Compose configuration (e.g., from 1.75.0 to 1.76.0) and click Redeploy. Coolify pulls the new image, creates a fresh container, and switches traffic to it. If something breaks, roll back to the previous version through the deployment history.

Our recommendation: Test updates on a staging instance first. We have seen n8n introduce breaking changes in minor version bumps. Pinning versions and testing deliberately prevents unpleasant surprises in production.

Cost Breakdown, Australian Context

Here is the real cost of running n8n on Coolify with Australian data residency or local latency:

  • Vultr Sydney: 2 vCPU, 4 GB RAM, 80 GB SSD is approximately AUD $36 per month.
  • DigitalOcean Sydney: 2 vCPU, 4 GB RAM, 80 GB SSD is approximately AUD $42 per month. Also offered: S3-compatible spaces at AUD $0.003 per GB per month for backups.
  • Database backups: Backblaze B2 at approximately AUD $0.008 per GB per month. Negligible for typical database sizes.
  • Optional VPS snapshots: Typically 20 per cent of VPS cost for automated snapshots. Useful but not essential if you have database backups in place.

Total monthly cost: AUD $40-60 for a production-ready, fully backed up, SSL-encrypted n8n instance processing hundreds of workflows. No per-execution fees. No surprise bills as your workflow count grows.

Compare this to n8n Cloud (approximately AUD $110 monthly for Pro plus overage fees), Zapier (hundreds of dollars monthly for comparable volume), or managed platforms like Railway (AUD $50-80 monthly plus per-resource overages as you scale). Self-hosting with Coolify becomes the obvious choice for any organisation running more than a handful of production workflows.

Scaling and High Availability

As your workflow count grows, Coolify provides several scaling paths:

  • Vertical scaling: Upgrade your VPS to a larger instance. Coolify does not care about underlying hardware. Stop, resize, restart. Simple.
  • Worker mode: n8n supports queue mode with separate main and worker instances. Deploy multiple n8n worker containers through Coolify, all connected to the same PostgreSQL database and a Redis instance (also deployable through Coolify).
  • Service separation: Move PostgreSQL to a dedicated server for demanding workloads. Coolify supports managing remote servers, so your dashboard stays unified.

For most Australian small and medium businesses, a single 4 GB RAM VPS handles everything comfortably. We typically recommend considering vertical scaling when you hit 100+ active workflows or when execution data throughput pushes CPU above 70 per cent consistently.

When Coolify Is Not the Right Choice

Coolify is excellent for most cases, but there are scenarios where it does not fit.

Enterprise with strict change control: If your organisation has formal change request processes and audit requirements, Coolify’s flexibility can work against you. You need infrastructure as code with peer review and approval gates. Raw Docker with version-controlled Compose files is better. So is Kubernetes if you are truly enterprise-scale.

Multi-region high availability: If you need n8n running in multiple regions with failover, Coolify on a single VPS is not the answer. You need Kubernetes or a managed orchestration platform. This is rare for most organisations.

Containerisation forbidden: Some regulated industries do not allow containers. If your compliance requirements demand bare-metal or specifically approved virtual machines, Coolify does not work. You would need to install n8n and PostgreSQL directly on the OS.

For everyone else, Coolify works well.

Getting Help with Deployment

If you would rather have experienced people handle this, that is what we do. As n8n consultants based in Brisbane, we have deployed n8n across Australian healthcare providers, financial services firms, and property tech companies. We can have your instance running in production within a day, with backups configured, monitoring in place, and full documentation for your team.

Book a free n8n consultation if you want to discuss your deployment options, understand the trade-offs between Coolify and raw Docker, or get a time estimate and cost breakdown for your specific use case.

Frequently Asked Questions

Is Coolify actually free for n8n hosting?

Yes, Coolify is completely free open-source software. You pay only for the VPS underneath. Coolify does offer a cloud-hosted version of their platform, but for hosting n8n you want the self-hosted version on your own VPS, which costs nothing beyond the VPS bill itself.

What is the best VPS for Coolify and n8n?

For Australian teams, Vultr Sydney or DigitalOcean Sydney offer the best combination of latency and cost. Both support automated backups and integrate cleanly with Coolify. Hetzner offers better value if cost is the primary concern. Minimum specs: 2 vCPU, 4 GB RAM. We recommend 4 GB RAM even if you think 2 GB might work. The extra cost is minimal and you avoid memory pressure once you run concurrent workflows or store execution history.

Can I run other services alongside n8n on the same Coolify server?

Yes, this is one of Coolify’s strengths. You can deploy multiple services on the same server with isolated networking, separate domains, and separate SSL certificates. Common additions alongside n8n include Uptime Kuma for monitoring, NocoDB for database frontends, and MinIO for S3-compatible file storage. Just monitor resource usage. A 4 GB VPS can comfortably run n8n plus two lightweight services. If you need more capacity, add more RAM or move to a larger instance.

How much does n8n cost on Coolify per month?

Approximately AUD $40-60 per month for a production-ready, fully backed up deployment. This covers the VPS (AUD $36-42), backup storage (negligible), and nothing else. No per-execution fees, no overage charges, no hidden costs. Your bill is predictable and fixed regardless of how many workflows you run or how often they execute.

What happens if my server fails? How do I recover?

Your workflows and execution history are stored in PostgreSQL. If you have configured Coolify’s automated backups (as we recommend), your database is backed up regularly to off-server storage. To recover, spin up a new VPS, install Coolify, restore the PostgreSQL backup, and redeploy n8n with the same encryption key. Your workflows, credentials, and execution history will all be intact. The critical piece is storing your encryption key safely outside the server. Without it, your credentials are unrecoverable even with a database backup.

Do I need DevOps experience to use Coolify?

A basic understanding of Docker and Linux helps, but Coolify abstracts most of the complexity. You do not need to write Dockerfiles or manage containers from the command line. The Docker Compose configuration in this guide is the most Docker-like thing you will interact with, and you can copy it directly. If something breaks at the infrastructure level, familiarity with docker ps, docker logs, and docker exec is useful for debugging. If you prefer to skip the technical work entirely, get in touch and we will handle the entire setup and handoff.

Can Coolify host n8n with Australian data residency?

Completely. Coolify runs on your own VPS in a region you choose. If you deploy on a Vultr or DigitalOcean instance in Sydney, your data stays in Sydney. No cloud provider logs. No data transfer to overseas regions. For Australian organisations in regulated industries (healthcare, finance, government), this data residency control is often the primary reason to self-host in the first place. Managed platforms like n8n Cloud do not offer this guarantee.

This guide is maintained by the n8n consulting team at Osher Digital. We update it as Coolify and n8n release new versions. If you are considering n8n deployment and want to discuss options specific to your organisation, book a free call with our team. We work with businesses across Australia and have deployed n8n in healthcare, finance, property, and professional services.

Jump to a section

Ready to streamline your operations?

Get in touch for a free consultation to see how we can streamline your operations and increase your productivity.

Get in touch
Book a call