Valkey
The BSD-licensed, Redis-compatible in-memory store - cache, queues, streams - as a single node.
One-click deploy, from $5/mo on a Miget plan.
Valkey is the BSD-licensed, Redis-compatible in-memory data store, forked and stewarded by the Linux Foundation after Redis changed its license. It is a drop-in for Redis clients and protocols: caching, queues, pub/sub, streams, and data structures all work unchanged.
This template is a single node, password-protected, with append-only persistence on a volume, running internal-only on Miget (apps connect at valkey:6379). A thin wrapper reads the password from the environment at start.
Miget offers managed Valkey as an addon for hands-off use. Run this template when you want to operate Valkey yourself, pin a version, or move up to the sentinel (failover) and cluster (sharding) topologies.
Upstream project: Valkey
#what you get
- Fully Redis-protocol compatible - clients work unchanged
- Cache, queues, pub/sub, streams, data structures
- Password-protected, append-only persistence on a volume
- Internal-only - reached at valkey:6379
- Sentinel and Cluster variants available for HA / scale
- BSD-3-Clause licensed
#topology
| Service | Role | Public |
|---|---|---|
| valkey | 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; the volume holds the append-only file. A single node is not HA - see valkey-sentinel for failover.
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 |
|---|---|---|---|
| Valkey on Miget ★ | 512 MiB plan | $5 | this whole stack, flat - no usage meters, and room left for your own apps |
| AWS ElastiCache | Valkey, cache.t4g.micro | ~$12 | smallest on-demand node/mo (ElastiCache now defaults to Valkey) |
| Aiven | Caching Startup | ~$31 | smallest managed Valkey plan/mo |
Managed caches bill per node; self-hosted Valkey is one flat plan, BSD-licensed.
#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
valkey -
Set the required variable:
VALKEY_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/valkey
docker compose up -dSame files, same behavior. The template README covers connection strings and scaling notes.
#faq
How is Valkey different from Redis?
Valkey is the community fork created after Redis moved to a more restrictive license. It stays under the permissive BSD-3-Clause license and remains protocol-compatible, so existing Redis clients, libraries, and tooling work without changes.
Why run this if Miget has managed Valkey?
The managed addon is simpler for wiring a cache to an app. This template is for running Valkey yourself with full control, or for the Sentinel and Cluster topologies, which the managed addon does not provide.
Can I point Redis clients at it?
Yes. Valkey speaks the Redis protocol, so any Redis client or library connects to valkey:6379 the same way it would to Redis.
Ship Valkey today
One compose stack, 512 MiB of RAM, from $5/month flat, and it runs on your laptop with the same files.