Layer 3 · self-hosting reality check
What it actually takes to self-host Valkey
The docs say 128 MB. In practice you want Your working set + 30%. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Redis alternatives, where Valkey is one of the picks.
Wondering whether you need to at all? Is Redis free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 128 MB |
|---|---|
| RAM — what it really needs | Your working set + 30% |
| CPU | 2 vCPU — it is single-threaded for commands |
| Disk | Small, unless you enable AOF persistence |
| Monthly cost | $12–30/mo depending on dataset size, against managed Redis pricing that climbs steeply with memory |
| Setup time | 30 minutes |
| How you install it | package or container; it is a drop-in fork of Redis 7.2, so existing clients work unchanged |
| Ongoing maintenance | Low. Watch memory and set an eviction policy. |
| Where it stops scaling | Hundreds of thousands of operations per second on one node. Clustering adds complexity you should defer as long as possible. |
The thing that catches people out
No maxmemory setting means the process grows until the OOM killer takes it — and it takes the whole box's cache with it. Set maxmemory and an eviction policy (allkeys-lru for a cache, noeviction if you are using it as a queue and cannot afford silent data loss) on the very first deploy. This is the single most common self-hosted Redis-family outage.
When not to self-host Valkey
You are using it as a primary datastore rather than a cache and cannot tolerate losing the last few seconds on a crash. Persistence exists but the durability guarantees are weaker than a real database.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 3 self-hosting guides
Common questions
- How much RAM does Valkey actually need?
- Your working set + 30% in practice. The documented minimum is 128 MB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU — it is single-threaded for commands alongside it.
- What does self-hosting Valkey cost per month?
- $12–30/mo depending on dataset size, against managed Redis pricing that climbs steeply with memory This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for low. Watch memory and set an eviction policy.
- How long does it take to set up Valkey?
- 30 minutes, via package or container; it is a drop-in fork of Redis 7.2, so existing clients work unchanged.
- When should I NOT self-host Valkey?
- You are using it as a primary datastore rather than a cache and cannot tolerate losing the last few seconds on a crash. Persistence exists but the durability guarantees are weaker than a real database.
- What is the most common mistake when self-hosting Valkey?
- No maxmemory setting means the process grows until the OOM killer takes it — and it takes the whole box's cache with it. Set maxmemory and an eviction policy (allkeys-lru for a cache, noeviction if you are using it as a queue and cannot afford silent data loss) on the very first deploy. This is the single most common self-hosted Redis-family outage.