Production n8n Infrastructure and Reliability

The shared environment that runs ByteFlow's n8n workflows and web applications. A structured audit mapped the services and their single points of failure.

Several automations and websites depended on one environment with limited monitoring and recovery practices.

Services were added over time, and the overall picture lived in one person's head.

1. Edge

   Traefik reverse proxy with automatic TLS certificates.

2. Runtime

   Docker containers for n8n, web applications and PostgreSQL databases.

3. Audit

   A systems map covering the services and their single points of failure.

1. Document every running service and dependency.
2. Identify single points of failure and risks.
3. Rank remediation by impact.
4. Work through the roadmap and keep the systems map current.

• Docker
• Traefik
• n8n
• PostgreSQL
• Linux VPS

• Documenting what exists comes before changing it.
• Remediation priorities: off-host backups, key management, uptime monitoring, version pinning for n8n, and documentation of undocumented systems.

• Secrets belong in environment variables or credential stores, not in compose files or workflow JSON.

Outcome: Work in progress: the audit and roadmap exist, and remediation is ongoing. No uptime figures are claimed.

Limitations: This is an internal environment, not a managed-hosting service, and no availability guarantees are made.