Databases deployment templates
Store application data, cache responses and support background jobs. Choose the database your application expects, then review storage, credentials and backup requirements.
10 templates · Page 1 / 1
Deno KV
InfluxDB
MySQL
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.
pgAdmin
phpMyAdmin
PostgreSQL
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.
Qdrant
Redis
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.
Redis Insight
How to choose
- Admin UIs are separate templates: pgAdmin for PostgreSQL, phpMyAdmin for MySQL and Redis Insight for Redis. Each adds a service with access to your data, so deploy it only when needed and protect it.
- Redis keeps its working data in memory, so size memory for your dataset and use it beside a primary database for caches, sessions and queues. Deno KV provides a key-value store for Deno apps.
- Choose by data shape: InfluxDB stores time series such as metrics and events, and Qdrant stores vector embeddings for similarity search. Both run as one service, usually beside a relational database.