No-code automation means building repeatable workflows in a visual editor instead of writing every integration from scratch. A trigger starts the workflow, nodes transform or route data, and action nodes call other services or perform tasks. n8n provides that visual workflow builder, plus AI and business-process features, as either a hosted Cloud service or software you operate yourself. Self-hosting n8n on a virtual private server (VPS) can give you more control over data, networking and costs, but you become responsible for installation, security, updates, backups and reliability.
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
The most repeatable self-hosted route is Docker with Docker Compose on a supported Linux server. The software’s Community edition is free, while the VPS, domain, backups and administration still cost money. Whether you can use n8n for client work depends on how clients access the system and on n8n’s Sustainable Use License.
As an Amazon Associate I earn from qualifying purchases.
What no-code automation actually is
A no-code workflow represents a business process as connected visual steps. You select a trigger, configure the data it receives, then connect nodes that make decisions, transform records or invoke external services.
Triggers start the run
A trigger can be a scheduled time, an incoming webhook, a new record in a connected application or a manual test. It defines when n8n should create a workflow execution.
#1 Best Overall
Nodes process and route data
Processing nodes can clean fields, map columns, filter records, merge results or branch on conditions. You can pass data from one node to the next without writing a custom integration for every step.
Actions produce the outcome
Action nodes send an email, create a ticket, update a database, call an API or post a notification. Credentials are stored in n8n and referenced by nodes rather than pasted into each request.
Free tools Windows power users keep installed
One-click scans. No signup required.
“No-code” describes the primary way you assemble a workflow, not a promise that advanced projects never need code. Expressions, small JavaScript steps, API knowledge, database skills and server administration are useful when a connector does not expose an option you need or when you operate n8n in production.
What n8n is and where it runs
n8n is a fair-code workflow automation platform with AI capabilities and business-process automation features. You can use n8n Cloud, where the service provider runs the application, or download and operate n8n on infrastructure you control. n8n’s current pricing page says its community includes more than 170,000 automation enthusiasts, professionals and community engineers (accessed in 2026).
Cloud and self-hosting run the same kind of visual workflows, but they shift responsibility in different directions. Cloud removes server installation and routine operating-system work. A VPS gives you control over the host, network location and data storage, while leaving you to maintain the complete stack.
Cloud or VPS: which route fits?
| Decision factor | n8n Cloud | n8n on your VPS |
|---|---|---|
| Setup effort | Create an account and configure workflows in the hosted interface. | Install an operating system, Docker, n8n, DNS and HTTPS before production use. |
| Infrastructure responsibility | The service handles the underlying server and routine platform operations. | You maintain the VPS, Docker, n8n, firewall, credentials, backups and monitoring. |
| Data-control requirements | Data is processed on the provider’s service under its hosting arrangements. | You choose the server region and storage controls, subject to your VPS provider and legal obligations. |
| Hosting cost | Recurring n8n subscription pricing applies. | The Community software is free, but you pay the VPS and any related infrastructure or administration costs. |
| Scaling and reliability | Scaling and platform availability are part of the hosted service. | You size resources, add redundancy and plan recovery yourself; no universal minimum CPU or RAM figure is published in the cited official material. |
| Webhooks and networking | Public endpoints are part of the hosted service. | You must provide DNS, a reachable HTTPS endpoint, TLS certificates and firewall rules. |
| Support scope | Support covers the hosted product according to your plan. | You troubleshoot the operating system, Docker, proxy, network and n8n unless you purchase separate help. |
| Licensing needs | Your plan governs use of the hosted service. | Community, Business and Enterprise self-hosted terms differ, especially when other people access the editor or service. |
Choose Cloud when minimizing operations is more important than controlling the server. Choose a VPS when you have a reason to control the deployment, can protect it and are prepared to own the operational work.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Prepare the VPS before installing n8n
A VPS supplies compute, storage, networking and an operating system; it does not administer n8n for you. n8n support guidance names providers such as DigitalOcean, Hetzner, Vultr, Contabo, Linode (Akamai), UpCloud and Scaleway as examples, but the provider name matters less than the capabilities below.
- Region: select a location that meets your latency, residency and contractual requirements.
- CPU, RAM and storage: size the server for your execution volume, concurrency, binary files and database. Treat any size as a starting point and monitor it; the official material does not establish a universal minimum.
- Backups and snapshots: confirm whether backups are automatic, how long they are retained, where they are stored and how restoration is tested.
- Networking: verify IPv4 and IPv6 behavior, bandwidth limits and whether inbound ports can be restricted.
- Firewall controls: allow only required traffic, normally SSH from an administration network and HTTPS from the internet.
- Recovery and support: check snapshot restore tooling, uptime commitments, incident communication and the total renewal price rather than an introductory rate.
Also obtain a domain name you control, decide who may administer n8n, and choose where workflow data and credentials will be backed up. Do not expose the n8n editor directly on an unencrypted IP address.
Self-host n8n with Docker Compose
Docker is not the only self-hosting route: n8n documents npm, Docker and server-based deployments. Docker Compose is the most reproducible starting point because the application definition, environment settings and persistent volume can be kept together.
1. Install a supported server and Docker
Create a current, supported Linux VPS, log in over SSH with a non-root administrative account and apply operating-system security updates. Install Docker Engine and the Docker Compose plugin using the instructions for your distribution. Confirm both commands work:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstalldocker --version
docker compose versionKeep SSH restricted by firewall rules or an allowlist, use key authentication where possible and avoid leaving password login open to the whole internet.
2. Create a project directory and persistent volume
mkdir -p ~/n8n
cd ~/n8n
mkdir -p backupsn8n stores configuration, credentials and execution data in its data directory. A named Docker volume keeps that data when the container is recreated. Treat the volume as sensitive: anyone who can read it may be able to access encrypted application data or configuration.
3. Define the Compose service
Create compose.yaml in the directory. This example binds n8n to localhost so a reverse proxy can provide the public HTTPS endpoint:
services:
n8n:
image: docker.n8n.io/n8nio/n8n:latest
restart: unless-stopped
ports:
- '127.0.0.1:5678:5678'
environment:
- N8N_HOST=n8n.example.com
- N8N_PROTOCOL=https
- WEBHOOK_URL=https://n8n.example.com/
- GENERIC_TIMEZONE=Etc/UTC
- TZ=Etc/UTC
volumes:
- n8n_data:/home/node/.n8n
volumes:
n8n_data:Replace the example hostname and timezone with your own values. Keep the n8n encryption key stable across restarts and migrations; store it outside public source control. If you use an external database or additional environment variables, document them and include them in your backup plan.
Recommended Free Tools
4. Start and verify the container
docker compose up -d
docker compose ps
docker compose logs -f n8nThe container should remain in a running state. Review logs for permission errors, invalid environment values, database failures or repeated restarts before moving on.
5. Put HTTPS in front of n8n
Point a DNS record such as n8n.example.com to the VPS address. Configure a maintained reverse proxy or equivalent managed HTTPS endpoint to forward requests to 127.0.0.1:5678, obtain and renew a TLS certificate, and pass websocket and webhook requests correctly. Set N8N_HOST, N8N_PROTOCOL and WEBHOOK_URL to the public HTTPS address, not the private container address.
Test both the editor and a real webhook from outside the server. If the editor loads but a webhook fails, check DNS, certificate coverage, proxy timeouts, forwarded headers and the webhook URL setting.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors6. Restrict administration
Use n8n’s authentication controls, strong unique credentials and least-privilege accounts. Limit the editor to trusted networks through the proxy, VPN or an IP allowlist when your use case permits. Keep the public surface limited to the endpoints workflows actually need; never publish Docker’s management socket or the VPS SSH service without protection.
Rank #4
- Book - powershell for sysadmins: workflow automation made easy
- Language: english
- Binding: paperback
Operate the deployment safely
Backups and restoration
Back up the n8n data volume and any external database on a schedule that matches the value of your workflows. Keep at least one copy away from the VPS, encrypt backups and record the encryption key separately. A backup is not proven until you restore it on an isolated instance and confirm that workflows, credentials and webhook configuration work.
Updates
Read n8n release notes, back up first, pull the chosen image and recreate the service during a maintenance window. Avoid unreviewed automatic major-version upgrades. Keep Docker, the operating system, the reverse proxy and certificate tooling patched as well.
Monitoring and capacity
Monitor disk usage, memory, CPU, container restarts, failed executions, queue depth if you use workers, certificate expiry and webhook response times. Alerts should reach someone who can act. If workloads outgrow one VPS, design a scaling plan instead of simply increasing concurrency: separate workers, a durable database, external object storage and a load-balanced HTTPS endpoint may be required, depending on the workflow mix.
Secrets and data handling
Use environment management or Docker secrets rather than committing API keys to a Compose file. Rotate credentials when staff or clients leave, limit each credential’s permissions and remove unused integrations. Review execution-data retention because payloads can contain personal, financial or confidential information.
Is self-hosted n8n free?
The self-hosted Community edition is free and includes almost the complete feature set. Registering a Community edition can unlock additional features at no charge. Business and Enterprise self-hosted plans require paid subscriptions and license keys. Features and plan boundaries can change, so verify the current n8n pricing and licensing pages when selecting an edition.
“Free software” does not mean a free deployment. Budget for the VPS, storage, backups, domain registration, email or monitoring services, administration time and possible recovery work. A small server may be inexpensive, but an outage or lost credential can cost more than the monthly infrastructure bill.
Can you use n8n for client work?
n8n’s Help Center license FAQ states: "You build and run workflows for clients on your own instance: allowed under the SUL, as long as clients only receive the outputs and have no access to n8n itself." This is the clearest case for an agency or consultant: you operate one instance, clients receive the resulting reports, records or notifications, and they do not log in to n8n.
Get a different commercial arrangement or legal review before giving clients direct editor access, embedding n8n as a user-facing feature, reselling access to your instance or offering a competing automation service. The Sustainable Use License is not a substitute for checking the exact current terms against your business model.
Quick Recap
Common failures and fixes
| Symptom | Likely cause | What to check |
|---|---|---|
| Browser cannot connect | DNS, firewall or proxy does not reach the container. | Resolve the hostname, verify ports 80/443, inspect proxy logs and confirm n8n is listening on localhost:5678. |
| Editor opens but webhooks return errors | Public URL or forwarded headers are wrong. | Check WEBHOOK_URL, HTTPS termination, proxy path handling and external requests from a different network. |
| Container restarts repeatedly | Invalid environment values, permissions, storage exhaustion or database failure. | Run docker compose logs n8n, inspect disk space and validate the Compose file. |
| Credentials disappear after recreation | The n8n data directory was not persisted. | Confirm the named volume is mounted at /home/node/.n8n and that backups include it. |
| Updates break a workflow | An integration or major version changed. | Restore the pre-update backup, pin a tested image version and schedule a controlled upgrade. |
| VPS becomes slow | Execution volume, binary data or concurrency exceeds available resources. | Inspect CPU, memory, disk and execution history; reduce retention, optimize workflows or resize and redesign the deployment. |
A practical decision checklist
- Use Cloud if you need the fastest start and do not want to run servers.
- Use a VPS if data location, network control or predictable infrastructure ownership justifies the operational burden.
- Choose Docker Compose for a repeatable deployment, but keep a documented rollback path.
- Do not call a production deployment ready until HTTPS, access control, secret protection, backups, restoration tests, updates and monitoring are in place.
- For client projects, keep clients limited to outputs unless your license arrangement explicitly permits another access model.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
