For n8n
n8n on Edge, with no execution meter
Free to sign up. No egress fees on any product.
Why n8n on Edge
Automation at any volume, without a meter running
Hundreds of integrations
Webhooks, schedules, HTTP requests and AI nodes, plus hundreds of built-in integrations. All on your VM.Queue mode when you need it
Start with one process. Set EXECUTIONS_MODE=queue and Redis hands jobs to as many workers as you run.Credentials stay on your network
Stripe, OpenAI, Salesforce and Slack keys are encrypted with your N8N_ENCRYPTION_KEY and stored in your own Postgres.Webhooks behind the CDN
Inbound webhooks arrive over TLS at the CDN, with DDoS protection included, and pass through uncached to the VM.Private network for workers
Worker VMs reach Redis and Postgres over a free private network in the same region. Nothing internal faces the internet.No per-execution bills
n8n Cloud prices by executions. On Edge, a million runs a month costs the same as a thousand.
Reference architecture
How n8n maps to Edge
Stripe, GitHub, forms
POST /webhook/…
Your team
workflow editor
n8n.acme.com
TLS, /webhook/* bypasses cache
n8n main :5678
editor, triggers, webhooks
redis:7
execution jobs
n8n worker ×2
runs executions, concurrency 10
postgres:16
workflows, credentials, history
n8n-backups
pg_dump and workflow exports
- Compute
Runs the n8n main process, workers, Redis and Postgres. One VM to start, more over a private network later.
- Storage
Nightly pg_dump and workflow exports. Binary data can live here too with n8n's S3 mode (Enterprise licence).
- CDN
TLS and DDoS protection for the editor and inbound webhooks, with caching bypassed on /webhook/*.
- DNS
Anycast DNS for n8n.acme.com.
- Shield
Scores public form submissions before they trigger a workflow.
Deploy
n8n in queue mode, in five steps
- 01
Create a VM and a backup bucket
A Performance VM (4 vCPU, 8 GiB) runs the main process, two workers, Redis and Postgres side by side.
shell$ edge compute create --name n8n --size s-4vcpu-8gb \ --image ubuntu-24 --region london --script docker $ edge storage create n8n-backups - 02
Configure n8n for queue mode
Every n8n process, main and workers, needs the same encryption key. Keep it safe: it decrypts your credentials.
.envN8N_HOST=n8n.acme.com N8N_PROTOCOL=https WEBHOOK_URL=https://n8n.acme.com/ N8N_ENCRYPTION_KEY=<openssl rand -hex 32> GENERIC_TIMEZONE=Europe/London DB_TYPE=postgresdb DB_POSTGRESDB_HOST=postgres DB_POSTGRESDB_DATABASE=n8n DB_POSTGRESDB_USER=n8n DB_POSTGRESDB_PASSWORD=<password> EXECUTIONS_MODE=queue QUEUE_BULL_REDIS_HOST=redis OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true - 03
Write the compose file
Main and workers share one definition. The worker service runs the same image with the worker command.
docker-compose.ymlx-n8n: &n8n image: docker.n8n.io/n8nio/n8n env_file: .env restart: always depends_on: [postgres, redis] services: n8n: <<: *n8n ports: ["127.0.0.1:5678:5678"] volumes: ["n8n-data:/home/node/.n8n"] n8n-worker: <<: *n8n command: worker --concurrency=10 redis: image: redis:7-alpine postgres: image: postgres:16 environment: POSTGRES_USER: n8n POSTGRES_PASSWORD: ${DB_POSTGRESDB_PASSWORD} POSTGRES_DB: n8n volumes: ["pg-data:/var/lib/postgresql/data"] volumes: n8n-data: pg-data: - 04
Start it and put the CDN in front
Add a bypassCache rule for /webhook/* and /rest/* in the deployment's configuration so nothing dynamic is ever cached.
shell$ docker compose up -d --scale n8n-worker=2 $ edge cdn create --name n8n $ edge cdn domains add cdn-a1b2c3 \ --domain n8n.acme.com \ --origin https://<vm-ip> - 05
Scale workers out when you need to
Workers only need Redis and Postgres. Publish both on the private interface only, and point new worker VMs at the main VM's private IP.
shell$ for i in 1 2 3; do edge compute create --name n8n-worker-$i --size s-2vcpu-4gb \ --image ubuntu-24 --region london --script docker done # attach each VM to the private network in the console, then set # QUEUE_BULL_REDIS_HOST=10.185.0.2 # DB_POSTGRESDB_HOST=10.185.0.2 $ docker compose up -d n8n-worker
Prefer to hand it off? Give the job to your AI agent or have our engineers do it.
What it costs
Half a million executions, one VM
- Unlimited executions and active workflows
- Add Standard worker VMs at $19.24/mo each
- Private networking between VMs is free
- Zero egress on API calls, webhooks and exports
Estimated monthly bill on Edge
~500k executions a month · queue mode on one VM
- Compute$38.47Performance VM · 4 vCPU · 8 GiB · 160 GB NVMe
- CDN$0.20~1.3M requests (webhooks + editor), first 500k free, then $0.25/M
- Storage$0.1515 GB of backups and exports, first 5 GB free
- DNS$0.00Zone and records for n8n.acme.com
- Egress$0.00
FAQ
n8n on Edge, answered
How does this compare to n8n Cloud or Zapier?
When should I switch to queue mode?
Can binary data go to Edge Storage?
How do I back up workflows?
Can I use AI nodes with my own models?
Drop-in services
Add these without touching the stack
- Edge ShieldBot protection
POST /siteverify → score: 94Score n8n form-trigger submissions with one HTTP Request node before the rest of the workflow runs.
Free for most sites. No puzzles, no widget to style.Explore - Edge AssistAI answers
<script src="…/assist.js">Add answers to the sites your workflows feed: one script tag, grounded in your own content.
Free tier: 250 answered questions a monthExplore
Run n8n on your terms
Start free and move your Zapier or Make workflows onto VMs you control.
Free tiers hard-cap. Nothing bills until you add a card.