Key takeaways
- Yes, n8n can be self-hosted with Docker, npm or Kubernetes under its fair-code licence.
- Self-hosting means you run n8n on your own server, controlling data, cost and updates.
- n8n Cloud removes operations work; self-hosting gives control and suits sensitive data and heavy usage.
- A production setup uses Docker Compose, PostgreSQL, HTTPS, a fixed encryption key and backups.
- Self-hosting is worth it when you have the skills and time to secure, monitor and update the server.
Yes, n8n can be self-hosted: you can run it on your own computer, a VPS or Kubernetes using Docker or npm, free for internal use under its fair-code Sustainable Use License, with paid enterprise features available. Self-hosting gives you control over data and costs, in exchange for managing security, backups and updates yourself. Docker and self-hosted services are part of my deployment stack, so this page explains what self-hosting means, how it works, cloud versus self-hosted, installation, setup, updates, versions and whether it is worth it.
Can n8n be self-hosted?
Yes. n8n is designed to be self-hosted as well as offered as a managed cloud. You can deploy it with Docker, Docker Compose, npm, or Kubernetes, on anything from a laptop to a cloud server.
Also asked as: can n8n be self hosted · how to setup n8n self hosted
Its licence, the Sustainable Use License, allows free self-hosting for internal business and personal use, but restricts offering n8n itself as a commercial service to others without an agreement. Some advanced features, such as certain enterprise capabilities, require a paid licence. Read the licence before building a business on top of self-hosted n8n. For students and personal projects, self-hosting on a laptop or a small cloud server is a practical, free way to learn automation and AI agents.
What does n8n self-hosted mean?
It means you run the n8n application on infrastructure you control, rather than using n8n's managed cloud. Your workflows, credentials and execution data live on your server or database, and you are responsible for keeping it running and secure.
Also asked as: what does n8n self hosted mean
This suits organisations with data residency or privacy requirements, teams needing to reach internal systems inside private networks, and heavy users who want predictable infrastructure costs. It also lets you install community nodes and customise the environment more freely. The trade-off is operational responsibility: uptime, security patches and backups are yours.
How does n8n self-hosting work?
You run n8n as a Node.js application, usually in a Docker container, with its data stored in SQLite by default or PostgreSQL for production. It listens on a port, usually behind a reverse proxy that provides HTTPS, and executes workflows when triggers fire.
Also asked as: how does n8n self hosting work
Webhooks need a public URL so external services can reach your instance, configured with environment variables such as the host and webhook URL. An encryption key protects stored credentials. For scale, n8n can run in queue mode, with a main instance and worker processes coordinated through Redis, spreading executions across multiple workers.
Should I use n8n self-hosted or n8n Cloud?
Choose n8n Cloud if you want to start quickly without managing servers, updates or backups. Choose self-hosting if you need data control, access to private systems, custom nodes, or predictable costs at high execution volumes, and can handle operations.
Also asked as: n8n self hosted vs cloud
Comparison:
- Setup: cloud in minutes; self-hosted needs server and configuration.
- Maintenance: cloud handled for you; self-hosted is your job.
- Data location: cloud on n8n's infrastructure; self-hosted on yours.
- Customisation: self-hosted allows more freedom.
- Cost: cloud is subscription-based; self-hosted costs infrastructure and time.
Many teams prototype on cloud and move to self-hosting as needs grow, or the reverse.
How do I install self-hosted n8n?
The simplest install is Docker: create a volume for data and run the official n8n image with port 5678 mapped. Alternatively, install with npm using npx n8n for quick local testing, or use Docker Compose for production with PostgreSQL.
Also asked as: how to install n8n self hosted
Quick start with Docker:
docker volume create n8n_data
docker run -d --name n8n -p 5678:5678 -v n8n_data:/home/node/.n8n docker.n8n.io/n8nio/n8n
Open port 5678 in your browser and create the owner account. Some hosting providers offer one-click n8n installs, which handle much of this setup for you. Whatever method you use, keep the data volume, because deleting it deletes your workflows and credentials.
How do I set up self-hosted n8n for production?
Use Docker Compose with n8n and PostgreSQL, put a reverse proxy such as Caddy or Traefik in front for HTTPS, set environment variables for host, protocol, webhook URL, timezone and a fixed encryption key, and configure backups and monitoring.
Production checklist:
- Store the encryption key and database credentials in an
.envfile excluded from git. - Use named volumes or managed PostgreSQL for persistence.
- Restrict access to the editor, and enable two-factor authentication.
- Back up the database and key regularly, and test restores.
- Monitor disk, memory and failed executions.
- Use queue mode with workers for heavy workloads.
How do I update self-hosted n8n?
Back up your database and encryption key, read the release notes for breaking changes, then pull the new image and recreate the container: docker compose pull followed by docker compose up -d. Data in volumes or PostgreSQL is preserved.
Also asked as: how to update n8n self hosted
Pin specific version tags rather than "latest", so updates happen deliberately. For major versions, upgrade step by step and test critical workflows in a staging copy first. Watch logs during startup while database migrations run. If something breaks, roll back to the previous tag and restore your backup, since migrations may not be reversible.
What is the latest self-hosted n8n version?
n8n releases new versions frequently, often weekly, with stable and beta channels. The latest version is listed on n8n's GitHub releases page and in its documentation's release notes, which also describe new features and breaking changes.
Also asked as: what is the latest n8n self hosted version
Self-hosted users can choose when to upgrade by pinning image tags. Staying reasonably current matters for security fixes and new integrations, but you need not chase every release. A sensible routine is reviewing release notes monthly, upgrading a staging instance first, then production. Subscribe to release notifications on GitHub to stay informed. To check your current version, open the editor's settings or help menu, or run the version command inside the container.
Is self-hosting worth it?
Self-hosting is worth it when you need data control, private network access, customisation or lower costs at scale, and have the skills and time to run servers securely. It is not worth it if operations would distract from your core work or you lack security experience.
Also asked as: is self hosting worth it
Hidden costs include monitoring, backups, security patches, incident response and your time. For students and learners, self-hosting is also an excellent way to learn Docker, Linux, networking and security. For businesses, compare total cost of ownership, including engineering time, against managed services before deciding. A useful test: if your server went down at night, would someone notice and know how to restore it? If not, start with a managed service and self-host later.
What is self-hosting?
Self-hosting means running software on servers you control, your own hardware or rented virtual machines, instead of using a provider's managed service. Common self-hosted tools include automation platforms, databases, websites, password managers and media servers.
Also asked as: what is self hosting
Benefits: control over data and configuration, independence from vendors, and potentially lower costs. Drawbacks: responsibility for security, updates, backups and uptime. Self-hosting usually involves Linux, Docker, reverse proxies, domain and HTTPS configuration and monitoring. Communities share guides and tools that make it accessible, but security deserves careful attention, especially for anything exposed to the internet.






