n8n runs on PicoPaaS, our first PostgreSQL-backed recipe

n8n is our first PostgreSQL-backed recipe: what it took to run it, and the limits to know about (database quota, execution pruning, an ephemeral user folder).

Share

To prove managed Postgres end to end we put n8n on it. It runs live at ai.picopaas.xyz on the stock public image, no Dockerfile. A workflow and the owner account both survived a pod restart.

What to know before you copy it

  • The 50 MB database quota is tight. n8n's schema alone takes about 16 MB. Prune executions (save only failures, keep 72 hours, cap the count) or a busy schedule will push the database read-only.
  • Memory. It OOMs at the 384 MiB default and needs an admin override to 512 MiB.
  • The user folder is ephemeral. Set N8N_USER_FOLDER=/tmp. Workflows, credentials and users live in Postgres, but binary data, community nodes and the crash-recovery log vanish on restart. It suits webhooks, API calls and notifications, not file pipelines.
  • Proxy hops. Set N8N_PROXY_HOPS=1 behind Traefik or the login rate limiter sees every visitor as one IP.
  • Pin N8N_ENCRYPTION_KEY as a secret, and update the host and webhook URLs if the app's address changes.

The full env list is in the n8n section of docs/RECIPES.md and in examples/n8n.