n8n
n8n in queue mode - editor plus horizontally scalable workers, with managed Postgres and Valkey auto-wired.
One-click deploy, from $25/mo on a Miget plan.
n8n is the workflow automation tool that took Zapier’s job for technical teams: 400+ integrations, a visual editor, and real code nodes when clicking runs out. Its production architecture is queue mode - the editor/webhook instance enqueues executions into Redis, and dedicated workers burn through them - and that is exactly what this template deploys.
On Miget, db and queue become managed Postgres and Valkey, with connection env auto-wired onto both the main instance and the workers. One required variable (N8N_ENCRYPTION_KEY) and you have the architecture n8n’s own docs recommend for production.
Workers are stateless - binary data lives in the database - so this is the one template in the catalogue where scaling replicas is the right move: bump worker replicas as workflow volume grows. n8n Cloud meters by executions; here, executions are free and the meter is your plan’s RAM.
Upstream project: n8n
#what you get
- Queue mode: the production architecture, not a single-container toy
- Horizontally scalable workers (stateless BullMQ consumers)
- 400+ integrations plus JS/Python code nodes and AI agent nodes
- Managed Postgres + Valkey auto-provisioned and auto-wired
- Unlimited executions - no per-run pricing
- Webhooks served on the public editor instance
#topology
| Service | Role | Public |
|---|---|---|
| n8n | editor + API + webhooks + scheduler (:5000) | yes |
| n8n-worker | workflow execution (scale replicas) | no |
| db / queue | Postgres / Valkey - managed services on Miget | no |
#miget sizing
// this stack needs
3.3 GiB RAM · 6 GB disk · 4 services
1 GiB editor + 1 GiB per worker + managed services. Workers are the scaling dial: heavy workflow volume means more worker replicas, which the 4 GiB plan accommodates one of and the 8 GiB plan several.
Hobby - recommended fit
$25/mo
2 vCPU · 4 GiB · 80 GiB disk
Headroom for your own apps: 8 GiB at $49/mo
Professional - production
$43/mo
2 vCPU · 4 GiB · 25 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| n8n on Miget ★ | 4 GiB plan | $25 | this whole stack, flat - no usage meters, and room left for your own apps |
| n8n Cloud | Starter | ~$24 | 2,500 executions/mo, 5 concurrent - no queue mode |
| n8n Cloud | Pro | ~$60 | 10,000 executions/mo, 20 concurrent |
Self-hosted n8n has no execution metering - the comparison crosses over at a few thousand workflow runs a month.
#vs. other PaaS
Estimated monthly cost of running this exact stack (3.3 GiB RAM, 6 GB disk, 4 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $25 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$163 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$44 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$42 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$33 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$20 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
n8n -
Set the required variable:
N8N_ENCRYPTION_KEY, encrypts stored credentials (openssl rand -hex 24); losing it orphans saved credentials
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/n8n
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
How much does self-hosted n8n cost vs n8n Cloud?
n8n Cloud Starter is ~$24/month for 2,500 executions and Pro ~$60/month for 10,000. This stack runs ~$25/month (4 GiB hobby) with unlimited executions - the crossover happens at trivially low workflow volume, and self-hosted includes queue mode, which Cloud reserves for higher tiers.
What is queue mode and why does it matter?
In default mode one process does everything - a heavy workflow blocks the editor and webhooks. Queue mode separates concerns: the main instance enqueues executions into Valkey and stateless workers execute them. It is n8n’s recommended production setup and what this template ships.
How do I scale n8n workers?
Increase the n8n-worker replica count - workers are stateless (binary data lives in Postgres), so this is the one catalogue template where replicas-based scaling is correct. Each worker wants ~1 GiB.
Are community nodes and AI features available self-hosted?
Yes - community nodes install from the editor, and the AI/LangChain agent nodes work with your own API keys. Self-hosted n8n has no feature meter on executions or workflows.
What happens if I lose N8N_ENCRYPTION_KEY?
Stored credentials become undecryptable - workflows survive but every connection must be re-authenticated. Treat the key like a database backup: store it in a password manager the day you deploy.
Ship n8n today
One compose stack, 3.3 GiB of RAM, from $25/month flat, and it runs on your laptop with the same files.