Discover what you can run. Read the configuration, understand the dependencies and choose the template that fits your project.
Selected configurations to explore. Selection is not a live-deployment certification.
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.
Deploy WordPress with a separate MariaDB service for a website or blog. This template includes both the application and its database. Uploaded files and database records need separate persistence and recovery checks.
Deploy PostgreSQL for applications that need relational data, transactions and SQL. Polyer's built-in template creates a private database service with persistent storage. Managed PostgreSQL behavior depends on the selected region's capabilities.
Deploy Redis for caching, queues and shared application state. The built-in template creates a private service with a storage volume. A volume alone does not determine Redis durability: check the persistence settings required by your application.
Deploy Uptime Kuma on Polyer to monitor websites, APIs and network services and get alerts when they go down. This template runs one louislam/uptime-kuma:2 service on a public domain and keeps monitors, settings and history on a volume at /app/data. Review the floating 2.x image tag before deploying.
Deploy MySQL on Polyer for applications that need relational data, transactions and SQL. The built-in template creates a private mysql:8.4 service with persistent storage at /var/lib/mysql, a generated root password and a database named app. Review the connection URL and whether you need the optional TCP proxy.
Compare n8n service, database and worker configurations.
Choose your application and database combination.
Create versioned templates from a project in your workspace.
Catalog templates include configurations from Coolify's Apache-2.0 licensed open template collection. Compatibility status describes Polyer's importer analysis, not a guarantee that every application has been tested live.