One-click template
Trigger- n8n 2.10.2, one click
- Hundreds of integrations
- Custom domain + SSL, automatic
- A European 4 GB server at $0.02/hr
Run n8n 2.10.2 in one click on a dedicated server we provision, secure and run. The webhook URL and the encryption key are set before first boot, so webhooks answer from the first run and credentials survive every redeploy. No execution meter.
Automate everything, except the server upkeep.
+$5.00 added at signup · deployment choice preserved · no card
One-click template
TriggerThe whole of n8n.
On a server in full view.
What it is. n8n is an open-source workflow automation tool for APIs, databases, webhooks and AI models. Here it deploys as a one-click template onto a dedicated server we run, on SQLite or its own Postgres.
Who it is for. Teams who want unlimited executions and their API keys on a server they control, without building Docker, a reverse proxy and TLS themselves.
When to use it. When hosted automation pricing scales with your execution count or when your workflows touch data that cannot sit on a shared cloud.
Where to start. Open the console with n8n selected
What n8n needs and what we already provide.
Self hosted n8n needs a 4 GB server, a database, a reverse proxy and a TLS certificate. The template ships all four, so the only n8n hosting requirement you choose is the server size.
| n8n version | 2.10.2 |
|---|---|
| Task runner | n8nio/runners:2.10.2, separate container |
| Code execution | JavaScript and native Python, max 5 concurrent |
| Database | SQLite (default) or a dedicated PostgreSQL instance |
| Minimum server | 4 GB RAM |
| Per-execution fee | None |
| HTTPS | Automatic, wildcard subdomain or your own domain |
| Webhooks | Pre-wired, no manual URL configuration |
| Regions | Six locations across Europe, North America and Asia. Which are open depends on the machine you pick |
| Backups | Optional. Daily, whole-VM, last 7 kept, +20% of the server price. One image is every container, database and volume together |
| MCP tools | 216 |
Specifications current as of September 2026.
Two containers. One click.
n8n and its task runner run as two containers on your own project server, with SQLite in a volume, HTTPS in front and the encryption key pinned.
| Component | Version | What it does |
|---|---|---|
| n8n | 2.10.2 | Editor, workflow engine, webhook endpoints |
| Task runner | n8nio/runners:2.10.2 | Isolated code execution, JS and native Python, max 5 concurrent |
| Database | SQLite or a dedicated PostgreSQL instance | Workflows, credentials, execution history |
| TLS and routing | Managed by Selfhost.dev | Public HTTPS URL, auto-renewed certificates |
| Encryption key | Persisted platform secret | Credentials stay readable across every redeploy |
n8n encrypts every saved credential with one key. Upstream leaves that key inside the data volume, so losing the volume makes every credential unreadable. We pin it as a platform secret and inject the same key on every redeploy.
Self hosted n8n needs N8N_EDITOR_BASE_URL and WEBHOOK_URL pointed at your public HTTPS address. Otherwise webhooks resolve to localhost. We wire both at deploy time.
Nodes cannot read server environment variables, bare Git repositories are disabled, settings-file permissions are enforced and proxy hops are configured.
From zero to live.
No server to set up.
Four steps. No Docker file, no reverse proxy, no certificate to renew.
Name it and pick a server. 4 GB is enough for n8n. We provision it, no cloud account to connect. Six regions across Europe, North America and Asia.
Add service → Template → n8n. Take SQLite or the Postgres variant for heavy execution volume. Six provisioning stages, about four minutes, then we email the URL and credentials.
No admin password is set at deploy. n8n's first-run screen creates the owner, and the first visitor claims it. Open it before you share the link.
Keep the wildcard subdomain or add your own: set DNS, verify a TXT record and HTTPS provisions and renews automatically. Then build.
The honest split.
We manage the infrastructure. You own what happens inside n8n. This is managed hosting, not managed automation.
| We run | You run |
|---|---|
| Server provisioning and capacity | Your workflows |
| Reverse proxy, TLS, renewals | Your credentials and API keys |
| Firewall and network rules | Your n8n users and roles |
| Editor and webhook URL config | Data retention inside n8n |
| The encryption key | Your n8n version and when to move to a newer one |
| Optional daily backups | |
| Metrics, logs and a health check every 60 seconds |
We pin the template to a tested n8n version, currently 2.10.2.
Your version. Your timing.
Your version is your decision. We pin n8n to an exact image, currently n8n 2.10.2, so a restart or a redeploy always brings back the same software. A newer template build applies to new deployments; yours stays put until you move it.
To move to a newer n8n:
Export your workflows, and your credentials in decrypted form, with n8n's own CLI over SSH.
Deploy the n8n template again. New deployments get our newest tested build.
Import both into the new instance, check a workflow runs, then move your domain across.
Server rates only. No execution meter.
You pay for the server and nothing else. A European 4 GB server is $0.02/hr, about $15 a month if you leave it running, billed hourly against prepaid credits. No per-execution, per-workflow, per-user or per-gigabyte fee.
$15.18 /mo at 730 hours European 4 GB server, $0.02/hr
Deploy n8n| What you pay for | Cost |
|---|---|
| European 4 GB project server | $0.02/hr, $15.18/mo at 730 hours |
| n8n template, task runner, SQLite | $0 |
| Dedicated Postgres variant | No separate fee, shares the server, budget more RAM |
| HTTPS and custom domain | $0 |
| Bandwidth | $0. Traffic is included |
| Daily server backups | Optional, +20% of server price |
Monthly figures assume 730 hours at our lowest rate, which is in our European regions. Other regions run different machine types at their own rates, priced live in the calculator.
n8n Cloud bills per execution. A project server bills per hour, whatever your workflows do.
Tell us your execution volume and we will send back the server size, the monthly cost and the two settings that change it most. One email, no newsletter.
Pick the variant at deploy time.
SQLite is the default and suits most teams. Take the Postgres variant for heavy execution volume or a large execution history. Pick when you add the template.
| SQLite (default) | Postgres variant | |
|---|---|---|
| Best for | Scheduled jobs, moderate webhook traffic | Heavy execution volume, large history |
| How to get it | Default | Select when adding the template |
| Concurrent writes | Fine at typical loads | Better |
| Server impact | Minimal | Same server, budget more RAM |
| Extra cost | None | None |
Postgres alone does not protect your credentials. Stock n8n keeps its encryption key in the data volume whichever database you choose, which is why we pin the key as a secret on both variants.
What this does not do.
Real constraints, easier to plan around than to discover.
Selfhost.dev is a managed self hosting platform for developers and small teams. Open-source apps and databases on dedicated servers you control, billed by the hour with no subscription tiers.
Best for: n8n, Twenty CRM, Supabase and managed PostgreSQL, MySQL, Redis, ClickHouse, OpenSearch and Kafka.