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.
What you can use it for
- Cache data shared by multiple application instances.
- Support queue-based jobs when your application's queue library uses Redis.
Choose the right configuration
The built-in Redis configuration enables append-only persistence, requires a generated password and mounts /data. Choose it for applications that support Redis for caching or queues. Confirm your application's eviction and durability requirements; enabling persistence does not provide a backup or guarantee that every recent write survives a failure.
What this template creates
redis
redis:7-alpinePrivate 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
- Select Configure deployment and sign in or create an account.
- Choose a new or existing project and select an available region.
- Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
- Inspect deployment logs, complete the application's setup and test its endpoints before production use.
Check your deployment
Connect with REDIS_URL from your application environment, run PING and write then read a disposable key with an expiry. For a queue, submit and consume a test job through the application's queue library. Test persistence during a planned restart before putting important data or jobs in this instance.
Operating this application
- Use the private endpoint and generated credentials to connect your services.
- Check eviction policies and memory use for your workload. Cache data and job queues can require different policies.
- Review persistence and recovery before putting irreplaceable data in Redis.
Hosting costs
Size memory for the working dataset and queue backlog, and storage for persistence. Key expiry and retention affect growth. Adding Redis to an application adds its own resource usage even when it is reachable only over the private network.
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 costsSource and validation
This 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
Choose your next step
Related templates
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.
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.