Polyer

n8n with PostgreSQL

Run n8n with a dedicated PostgreSQL database on Polyer to build and host automated workflows. Alongside n8n and its external task runner, this variant adds a private PostgreSQL 16 service that stores workflows, credentials and execution history instead of SQLite. Review both persistent volumes before deploying.

AutomationCoolify open catalog

What you can use it for

  • Run team or production automations whose execution history belongs in a separate database rather than a local SQLite file.
  • Keep workflow and execution data where you can back it up and query it with standard PostgreSQL tools.

What this template creates

n8nn8nio/n8n:2.10.2
Public endpoint Persistent volume
task-runnersn8nio/runners:2.10.2
Private service
postgresqlpostgres:16-alpine
Private service Persistent volume

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

  1. Select Configure deployment and sign in or create an account.
  2. Choose a new or existing project and select an available region.
  3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
  4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Operating this application

  • Create the n8n owner account as soon as the generated domain responds, and change GENERIC_TIMEZONE and TZ from their UTC default if schedules should follow your local time.
  • Back up PostgreSQL together with the n8n volume at /home/node/.n8n, because n8n encrypts stored credentials with a key it generates on first start and saves there; a database restored without that key leaves credentials unreadable.
  • The n8n and runners images are pinned to 2.10.2, so upgrade both together after a database backup, as n8n migrates its schema on startup; this variant runs a single instance without queue mode.

Hosting costs

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Review prices and estimate resource costs

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-10

Upstream documentation Template source and license

Choose your next step

Related templates

n8n

Run n8n on Polyer to connect services and build automated workflows. The standard catalog template runs n8n with a separate task-runner service and local SQLite storage; use the related PostgreSQL variant if you need a separate database. Review the actual service composition and configuration before deploying.

Automation2 services

Activepieces

Deploy Activepieces on Polyer to build no-code automations between your business apps. The template runs the public Activepieces 0.75.0 service with private PostgreSQL 18 and Redis services; flows, connections and run history are stored in PostgreSQL. Review the default code execution mode before deploying.

Automation3 services