Redis
The in-memory data store - cache, queues, pub/sub, streams - as a single password-protected node.
One-click deploy, from $5/mo on a Miget plan.
Redis is the in-memory data store that powers caching, job queues, pub/sub, rate-limiting, sessions, leaderboards, and streams across a huge share of modern apps. This template is a single node, password-protected, with append-only persistence on a volume.
It runs internal-only on Miget: other services in the same project connect at redis:6379 over the private network. A thin wrapper reads the password from the environment at start, so the secret is never baked into the image.
Miget also offers managed Valkey (a Redis-compatible drop-in) as an addon - reach for that when you just want a cache wired to an app. Run this when you want to own and tune Redis yourself, or step up to the sentinel (failover) and cluster (sharding) templates.
Upstream project: Redis
#what you get
- Cache, queues, pub/sub, streams, and rich data structures
- Password-protected, append-only persistence on a volume
- Internal-only - reached at redis:6379 on the private network
- Single node, ~tiny footprint
- Sentinel and Cluster variants available for HA / scale
- Redis 8 is AGPL-3.0
#topology
| Service | Role | Public |
|---|---|---|
| redis | in-memory data store (:6379) | no (internal) |
#miget sizing
// this stack needs
512 MiB RAM · 5 GB disk · 1 service
Size RAM to your working set (Redis keeps data in memory); the volume only needs to hold the append-only file. A single node is not HA.
Hobby - recommended fit
$5/mo
1 vCPU · 512 MiB · 10 GiB disk
Headroom for your own apps: 1 GiB at $7/mo
Professional - production
$22/mo
1 vCPU · 2 GiB · 10 GiB disk
Dedicated resources, production SLOs - plan details
One Miget plan is a fixed pool of compute - the whole stack (managed databases included) deploys inside it, and anything left over runs your other apps. No per-service or per-seat math.
#vs. the managed service
What the hosted equivalents charge, against the flat Miget plan this stack fits on. Prices as of June 2026, sources linked.
| Service | Plan | Monthly | What you get |
|---|---|---|---|
| Redis on Miget ★ | 512 MiB plan | $5 | this whole stack, flat - no usage meters, and room left for your own apps |
| AWS ElastiCache | cache.t4g.micro | ~$12 | smallest on-demand node/mo; HA doubles it |
| Redis Cloud | Fixed | ~$5 | from $5/mo for a tiny instance, scales with memory |
Managed Redis/Valkey bills per node (and per AZ for HA); this is one flat plan on your own infrastructure.
#vs. other PaaS
Estimated monthly cost of running this exact stack (512 MiB RAM, 5 GB disk, 1 container) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $5 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$25 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| DO App Platform | ~$11 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Render | ~$8 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| Railway | ~$6 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$4 | cheapest sticker price - but burstable shared CPUs (1/16 core; dedicated vCPUs cost ~2-3×), no compose deploys (one app per container, manual wiring), managed DBs billed extra |
Estimates assume RAM fully allocated at published on-demand rates - and sticker price isn't the whole comparison: the cheaper rows buy burstable shared CPUs, per-service wiring instead of a compose deploy, and managed databases billed separately. Heroku and DO App Platform have no persistent volumes at all - stateful stacks like this one need workarounds there.
#deploy it
On Miget
- Create a Compose Stack in app.miget.com pointing at the templates repository
- Set the stack path to
redis -
Set the required variable:
REDIS_PASSWORD, requirepass secret (openssl rand -hex 24)
- Deploy. Miget layers
compose.miget.yaml(RAM, privacy, volumes, managed services) automatically
Locally first?
Every template is portable, vanilla Docker Compose - the Miget overrides are ignored locally:
git clone https://github.com/deployable-sh/stacks
cd miget-compose-templates/redis
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
Should I use this or managed Valkey?
For most apps, managed Valkey (a Redis-compatible addon) is less to operate. Use this Redis template when you specifically want Redis, full control of its configuration, or the Sentinel / Cluster topologies the managed addon does not expose.
What does this save vs ElastiCache?
AWS ElastiCache starts around $12+/node/month for the smallest instance and multiplies for HA, plus data transfer. This is one flat plan on your own infrastructure, with no per-node metering.
Is my data safe across restarts?
Append-only persistence is enabled and written to the volume, so data survives restarts. For real high availability (automatic failover), use the redis-sentinel template; a single node still has a single point of failure.
Ship Redis today
One compose stack, 512 MiB of RAM, from $5/month flat, and it runs on your laptop with the same files.