Self-Hosted n8n Service Baseline
Stand up n8n as an operational service rather than a one-off container, with persistence, boot recovery and a narrow public ingress boundary.
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
A recoverable n8n stack that survives host reboot and separates webhook ingress from admin access.
Docker/Compose available on the host.
A domain/reverse proxy plan.
A backup location outside the live container volume.
Persist application state
Declare the n8n data volume explicitly and remember persistence is not backup.
Add application health
Expose readiness separately from container started state.
Make boot lifecycle explicit
Use host service management so the stack returns after reboot.
Separate webhook ingress from admin
Public callbacks do not require a publicly open editor.
Prove restore readiness
Back up and restore the state before treating the service as durable.
Turn the Recipe into checkable work.
Progress, notes and history stay in this browser.