Skip to content
AutoPinFlow AI • Automation • Future Technology

Self-Hosting n8n in Production: The Guide We Wish We Had

Queue mode, Postgres tuning, credential encryption and the observability stack that keeps a self-hosted n8n cluster boring in the best way.

When self-hosting is the right call

Self-hosting wins on cost past roughly one hundred thousand executions per month, and on compliance the moment regulated data enters a workflow. Below that, the managed cloud is almost always cheaper once you price in an on-call rotation.

Queue mode is not optional

Single-process mode is fine for a homelab and dangerous in production. Split the main process, workers and webhook receivers, put Redis in front, and Postgres behind. Every serious incident we investigated started with someone skipping this step.

The observability stack

Structured logs, execution metrics scraped into Prometheus and a dashboard per workflow. Alert on failure rate and queue depth, not CPU. The interesting failures never touch CPU.

LB

Lukas Berg

Senior Automation Writer

Lukas builds and breaks automation stacks for a living — n8n, Make, Zapier and everything in between.

Newsletter

Never Miss an AI Breakthrough

Join thousands of readers receiving weekly AI news, tutorials, and automation insights.

No spam. Unsubscribe anytime. We never share your address.

Comments (0)

Discussion is opening soon. Be the first to comment.

Leave a comment

Your email address will not be published. Required fields are marked *