Deploy Redis by Bitnami
Secure, persistent Redis powered by Bitnami. Deploy in 1-click 🚀
redis
Just deployed
/bitnami/redis/data
Deploy and Host Redis by Bitnami on Railway
Redis by Bitnami provides a secure and persistent Redis deployment for Railway. It includes password authentication, AOF persistence, private networking, and persistent storage for caching, sessions, queues, rate limiting, Pub/Sub, and other low-latency workloads.
About Hosting Redis by Bitnami
Hosting Redis by Bitnami on Railway gives you a persistent Redis instance that can be accessed securely by other services through Railway's private network.
The template uses the latest Bitnami Redis container, enables password authentication, stores Redis data on a Railway volume, and exposes standard connection variables such as REDIS_URL, REDISHOST, REDISPORT, and REDISUSER.
Redis remains private by default and does not require a public HTTP domain.
Common Use Cases
- Application caching
- Session storage
- Rate limiting
- Background job and queue backends
- Pub/Sub messaging
- Temporary application state
- Distributed locks
- API response caching
Dependencies for Redis by Bitnami Hosting
- Bitnami Redis container image
- Railway persistent volume mounted at
/bitnami/redis/data - Railway private networking for service-to-service communication
Implementation Details
Redis listens on the standard Redis port:
6379
The Railway persistent volume is mounted to:
/bitnami/redis/data
Redis uses Append Only File (AOF) persistence so writes can survive container restarts and redeployments.
The template uses the following authentication and connection variables:
REDIS_PASSWORD="${{secret(32)}}" # Password required to authenticate to Redis
REDISHOST="${{RAILWAY_PRIVATE_DOMAIN}}" # Private Redis hostname within the Railway project
REDISPORT="6379" # Redis TCP port
REDISUSER="default" # Default Redis ACL username
REDIS_URL="redis://default:${{REDIS_PASSWORD}}@${{RAILWAY_PRIVATE_DOMAIN}}:6379" # Internal Redis connection URL
The template runs Redis directly using a custom start command:
/bin/bash -c 'mkdir -p /bitnami/redis/data && exec /opt/bitnami/redis/bin/redis-server --port 6379 --bind 0.0.0.0 --protected-mode yes --dir /bitnami/redis/data --appendonly yes --requirepass "$REDIS_PASSWORD"'
This keeps the deployment compatible with the latest Bitnami Redis image while explicitly configuring the Redis port, authentication, persistent data directory, and AOF persistence.
Redis should normally remain accessible only through Railway's private network. A public domain is not required.
Connecting from Another Railway Service
Applications in the same Railway project can use the provided REDIS_URL directly.
Connection format:
redis://default:<password>@<private-host>:6379
Many frameworks and Redis client libraries support REDIS_URL directly.
Redis by Bitnami vs Other Redis Deployments
| Feature | Redis by Bitnami | Basic Redis Container | Managed Redis |
|---|---|---|---|
| Redis-compatible | ✅ | ✅ | ✅ |
| Password authentication | ✅ | ⚠️ Manual | ✅ |
| Persistent Railway volume | ✅ | ⚠️ Manual | ✅ |
| AOF persistence | ✅ | ⚠️ Manual | ✅ |
| Private Railway networking | ✅ | ✅ | Depends |
| Ready-to-use connection URL | ✅ | ⚠️ Manual | ✅ |
| Self-hosted | ✅ | ✅ | ❌ |
| Infrastructure control | ✅ | ✅ | Limited |
Why Deploy Redis by Bitnami on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Redis by Bitnami on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
redis
bitnami/redis:latest