n8n Hosting on High-Performance VPS
Workflow automation with unlimited executions and your credentials on your own server.
Size a server for n8n
Every stop is a real configuration you can deploy. Priced per 30 days, billed by the hour, exclusive of 18% GST.
What n8n is
n8n is a workflow automation tool: you connect services together on a canvas, and each workflow runs when a trigger fires - a webhook, a schedule, a database row, a message. It occupies the same ground as Zapier or Make, with the difference that the whole thing runs on infrastructure you control.
That difference is the reason most people self-host it. Hosted automation is billed per task or per execution, so the cost of a workflow scales with how often it runs, and a chatty polling workflow can cost more than the server it would need. On your own VPS the execution count stops being a billing dimension entirely.
The other reason is credentials. n8n stores API keys and OAuth tokens for every service a workflow touches - your CRM, your payment processor, your mail provider - encrypted with a key you set. Self-hosting means that encrypted store sits on a disk you control rather than a vendor's.
Why run n8n on a VPS
Executions are not metered. The limit is what the server can process, not a plan tier.
The credential store and its encryption key stay on your disk.
Workflows can reach services on the same private network - a database or an internal API that is not exposed to the internet.
You choose the n8n version and when it changes. An upgrade that breaks a node happens when you decide it does.
n8n features
Visual workflow editor with 400+ integration nodes
Webhook triggers with your own domain and TLS
Scheduled and event-driven executions
A Code node for JavaScript or Python when no node fits
Encrypted credential storage
Execution history you can inspect and replay
Queue mode with separate workers for heavier loads
Recommended server
A starting point for n8n, not a hard floor — size it on the sliders.
| Memory | 4 GB for light use; 8 GB once workflows run concurrently |
|---|---|
| CPU | 2 vCPU is enough for most; queue mode benefits from 4 |
| Storage | 40 GB, more if you retain long execution histories |
| Operating system | Ubuntu 22.04 or 24.04 LTS |
How deployment works
n8n is installed on the server itself with Node.js and a PostgreSQL backing store rather than SQLite, which is what makes execution history survive restarts and keeps concurrent writes safe. A reverse proxy terminates TLS for your domain. You have root throughout and can change any of it afterwards.
What people run it for
Internal integrations
Move data between systems that have no native integration - a CRM into a warehouse, form submissions into a ticketing tool.
Scheduled reporting
Pull metrics on a cron, assemble a digest, deliver it to email or chat without a person in the loop.
Webhook processing
Receive callbacks from payment providers or SaaS tools, transform the payload and route it onward.
AI pipelines
Chain model calls with retrieval and post-processing, keeping prompts and keys on your own machine.
n8n hosting questions
Related applications
Windmill Hosting Scripts become APIs, workflows and internal UIs — with executions bounded by your server, not a plan. 
Node-RED Hosting Event-driven flows for IoT, MQTT and API glue, on a server with a fixed address. 
OpenClaw Hosting A private AI agent instance with its own sandbox and persistent memory, on hardware you control. 
Apache Airflow Hosting Data pipeline orchestration with DAGs and retries, without per-task pricing. 
Portainer Hosting A web interface for Docker — containers, images, volumes and networks, without living in the CLI. Deploy n8n on your own server
Root access, your choice of size, and no container between you and the application.