Valkey Sentinel
Highly-available Valkey with automatic failover - one master, two replicas, three sentinels. BSD.
One-click deploy, from $13/mo on a Miget plan.
Valkey Sentinel brings high availability to Valkey using the same battle-tested design as Redis Sentinel: sentinels watch the master and promote a replica automatically if it fails. This template runs one master, two replicas, and three sentinels (quorum 2). BSD-licensed and Redis-protocol compatible.
One image plays all three roles, selected by an environment variable; the entrypoint generates each command and the sentinel config from env, with hostname resolution so failover reports a DNS-resolvable address on a multi-pod network.
Clients connect through Sentinel - existing Redis Sentinel client libraries work unchanged, asking a sentinel for the current master and following failovers transparently.
Upstream project: Valkey
#what you get
- Automatic failover with replica promotion
- One master, two replicas, three sentinels (quorum 2)
- Hostname-based discovery for multi-pod networks
- Existing Redis Sentinel clients work unchanged
- All internal-only, password-protected
- BSD-3-Clause licensed
#topology
| Service | Role | Public |
|---|---|---|
| valkey-master | primary (:6379) | no (internal) |
| valkey-replica-1/2 | replicas (failover targets) | no |
| valkey-sentinel-1/2/3 | monitors + electors (:26379) | no |
#miget sizing
// this stack needs
1.9 GiB RAM · 15 GB disk · 6 services
Master and replicas hold the dataset in memory; sentinels are tiny. Six services, all internal. For sharding instead of failover, see valkey-cluster.
Hobby - recommended fit
$13/mo
1 vCPU · 2 GiB · 50 GiB disk
Headroom for your own apps: 2 GiB at $19/mo
Professional - production
$43/mo
2 vCPU · 4 GiB · 25 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 |
|---|---|---|---|
| Valkey Sentinel on Miget ★ | 2 GiB plan | $13 | this whole stack, flat - no usage meters, and room left for your own apps |
| AWS ElastiCache | Multi-AZ (2 nodes) | ~$24 | primary + replica on-demand/mo for the smallest size |
| Aiven | Caching Business | ~$80 | smallest HA managed Valkey plan/mo |
Managed HA caches bill per node; the whole Sentinel topology here is one flat plan, BSD-licensed.
#vs. other PaaS
Estimated monthly cost of running this exact stack (1.9 GiB RAM, 15 GB disk, 6 containers) elsewhere, from published June 2026 rates.
| Platform | Est. monthly | Notes |
|---|---|---|
| Miget ★ | $13 flat | compose stacks first-class: one deploy, dedicated vCPU, managed Postgres/Valkey, volumes and TLS all included in the plan |
| Heroku | ~$94 | no volumes; nothing between 1 GB ($50) and 2.5 GB ($250) dynos - 2 GB containers cost far more than shown |
| Render | ~$46 | per-service instances (0.5 GB $7, 2 GB $25) - every container is its own paid service |
| DO App Platform | ~$35 | no persistent volumes - stateful containers need managed DBs/Spaces (base $5 Spaces included here) |
| Railway | ~$21 | usage-based ($10/GB RAM-mo); vCPU billed separately at $20/vCPU-mo on top |
| Fly.io | ~$14 | 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
valkey-sentinel -
Set the required variable:
VALKEY_PASSWORD, shared by master, replicas, and sentinel auth
- 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/valkey-sentinel
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
Sentinel or Cluster?
Sentinel gives failover HA for a dataset that fits on one node. valkey-cluster shards across multiple masters when one node is not enough. Many teams only need Sentinel.
Is it compatible with Redis Sentinel clients?
Yes. Valkey implements the same Sentinel protocol, so libraries written for Redis Sentinel connect to the valkey-sentinel-* nodes with master name "mymaster" unchanged.
What does this save vs managed HA caches?
Managed HA Redis/Valkey (ElastiCache Multi-AZ, Redis Cloud, Aiven) bills per node per month plus transfer. This is one flat plan on your own infrastructure for the whole topology.
Ship Valkey Sentinel today
One compose stack, 1.9 GiB of RAM, from $13/month flat, and it runs on your laptop with the same files.