Application hosting

Hosting Valkey

Valkey is an in-memory data store that can be installed from source, containers, or operating-system packages. The project does not give one server size for every dataset and traffic pattern.

Min vCPU
Depends on workload
Min memory
Depends on workload
Min storage
Depends on workload

Must have

Hard prerequisites

No universal server-size prerequisite is published. Check the exact release and configuration before you deploy.

Recommended

Documented guidance

No further general recommendations are published for this version.

Capacity depends on your workload

The project documentation gives no universal server size. Dataset size, maxmemory policy, persistence mode, and traffic affect memory and disk demand.

We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.

Deploy with

Supported paths

  • Build from an official source release
  • Run an official container image
  • Install with a supported distribution package manager

The host must provide

Runtime

Operating system
Linux/BSD package support varies by distribution; consult its current package version
Client
Applications connect using Valkey protocol client libraries
Network protection
Use a firewall and bind only to intended interfaces; enable ACL/password authentication

Storage

Persistent data

Valkey is memory-oriented. Disk use depends on persistence configuration and snapshot/log files. Plan memory around the dataset and configured overhead; preserve and test recovery files if persistence is enabled.

Step by step

Valkey deployment outline

  1. Install a supported release

    Select an official source build, container, or package available for the target operating system.

    Official instructions
  2. Restrict network access

    Bind Valkey only to intended interfaces, firewall its ports, and configure ACL authentication before connecting application services.

    Official instructions
  3. Choose persistence and recovery settings

    Decide whether this instance is a cache or must preserve data. Valkey documents RDB snapshots and AOF logs, with different recovery and write behavior; include the selected data files in a tested backup plan.

    Official instructions

Security

Before you go public

  • Do not expose an unauthenticated Valkey port to the public internet.
  • Restrict listening interfaces and firewall access.
  • Use ACL/password authentication and TLS where required by the network boundary.

Cost

Beyond the server price

  • Memory is often a major infrastructure constraint; include persistence disk, snapshots, backup retention, and network charges.
  • No provider price or universal resource budget is published by Valkey itself.

Matching plans

Plans with published evidence

DigitalOcean

CPU-Optimized Regular Droplet · 2 vCPU / 4 GiB

2vCPU
4 GiBRAM
25 GiBStorage
4 TBTransfer
  • Dedicated CPU
  • SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

DigitalOcean

General Purpose Droplet · 2 Dedicated vCPU / 8 GB

2vCPU
8 GBRAM
25 GBStorage
4 TBTransfer
  • Dedicated vCPU (100% allocatio...
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Google Cloud

Compute Engine e2-medium · 2 vCPU / 4 GB

2vCPU
4 GBRAM
—Storage
—Transfer
  • Shared vCPU (1.00 sustained)
  • Persistent Disk (billed separa...
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Google Cloud

Compute Engine e2-small · 2 vCPU / 2 GB

2vCPU
2 GBRAM
—Storage
—Transfer
  • Shared vCPU (0.50 sustained)
  • Persistent Disk (billed separa...
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX13 (Germany and Finland)

2vCPU
8 GBRAM
80 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX23 (Germany and Finland)

4vCPU
16 GBRAM
160 GBStorage
20 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX33 (Germany and Finland)

8vCPU
32 GBRAM
240 GBStorage
30 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX43 (Germany and Finland)

16vCPU
64 GBRAM
360 GBStorage
40 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX53 (Germany and Finland)

32vCPU
128 GBRAM
600 GBStorage
50 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CCX63 (Germany and Finland)

48vCPU
192 GBRAM
960 GBStorage
60 TBTransfer
  • Dedicated AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CPX11 (US locations)

2vCPU
2 GBRAM
40 GBStorage
1 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Hetzner Cloud

Hetzner Cloud CPX12 (Germany and Finland)

1vCPU
2 GBRAM
40 GBStorage
20 TBTransfer
  • Shared AMD vCPU
  • NVMe SSD
Compatibility unclear from published plan data

Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.

No published runtime facts let us confirm a match.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.