Blog: Running Node-RED in production (follow-up to admin-it.io "Wiring the Modern Stack")

## What

MOFU post for IT/OT digitalization teams already running Node-RED at work. Follow-up to Max Jonas Werner's [Wiring the Modern Stack with Node-RED](https://www.admin-it.io/wiring-the-modern-stack-with-node-red/) (30 Jul 2026) — he walks a genuinely good self-hosted stack (Docker Compose, Caddy, Mosquitto, Postgres, OIDC) and then repeatedly notes that production "requires discipline" without saying where that discipline comes from. This is that post.

Two framings — pick one:

**A — `running-node-red-in-production.md`**
"Running Node-RED in Production: What Comes After the Install Guide"
Problem-led. Better SEO surface: keyword in the title and in the H2s.

**B — `node-red-workshop-era.md`**
"Node-RED in Production: The End of the Workshop Era"
Same material framed as a craft → discipline transition, structured around reviewable / reproducible / inspectable. More distinctive, weaker keyword surface.

## Why

The install is fast because the community made it fast. Production needs a layer Node-RED does not ship: environments, change review, rollback, access control, node governance, fleet, reuse across sites. Werner states the problem well, from outside FlowFuse, with traffic — the answer should exist and be linkable.

## TL;DR

Node-RED stays free either way. The real comparison isn't licence vs. free, it's engineering time vs. a licence.

## Cover

- The gap list: environments, change review, rollback, RBAC, node governance, fleet, cross-site reuse
- Cost each one as the thing you would otherwise build and maintain yourself
- Link back to Werner generously — he did the setup half properly, we're doing the run half
- Node governance cross-links to the Certified Nodes post (#5666)