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.
Use PostgreSQL when your application expects a PostgreSQL connection. Check the selected region before choosing a version: managed PostgreSQL and the self-run container follow different deployment paths. Use the private connection details shown after deployment; external access and recovery capabilities need a separate review for that region.
Regions with managed PostgreSQL use PostgreSQL 18: ghcr.io/cloudnative-pg/postgresql:18.6-standard-trixie
Other regions use the self-run image: postgres:16-alpine
This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.
Connect from the application environment with the displayed credentials and run SELECT 1. Then test an application migration and a write/read cycle in a disposable database. A successful connection does not verify recovery: restore a backup into a separate test target and check the records before relying on it.
Estimate database resources separately from your application. Query load, connection count, indexes and retained data affect memory, CPU and storage needs. Check the selected region's prices and backup options instead of assuming every PostgreSQL deployment has the same cost or recovery policy.
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 costsThis is a Polyer built-in database template.
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-15
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.
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.
