The HYEHOST bear in a Halloween cape beside glowing server pumpkinsThe HYEHOST bear enjoying Bonfire Night with fireworks and a glowing server cabinet
A little extra this HalloweenLight up your balance

Your Halloween credit treatYour Bonfire Night boost

+15% extra account credit

Add $5–$100 USD to your HYEHOST account and receive 15% extra credit automatically.Add $5 USD or more and receive 15% extra credit automatically, with no maximum top-up amount.

Add $5
$5.75account credit at 15%25% upgrade · $6.25
Add $25
$28.75account credit at 15%25% upgrade · $31.25
Add $100$1,000
$115$1,150account credit at 15%25% upgrade · $1,250
  1. Log in to your HYEHOST account.
  2. Open Billing and add $5–$100 credit.add at least $5 USD, with no maximum.
  3. Your bonus is added automatically. No code needed.

Valid for qualifying $5–$100 USD top-ups on 31 October 2026, until 23:59 UK time.Updated offer available until midnight UK time at the end of 5 November 2026. Minimum top-up $5 USD, with no maximum amount. The 25% bonus replaces the usual 15% when selected.

Log in and add credit
HYEHOST

Valkey vs Redis on a VPS: Compatibility and Memory

Compare Valkey and Redis for a VPS. Covers Valkey 9.2, client compatibility, cache eviction, persistence, Docker memory limits and migration checks.

Compare Valkey and RedisPlan memory
HYEHOST bear mascot holding a RAM module beside blue Valkey and red Redis database cards above a VPS server

Should you use Valkey or Redis on your VPS?

For a new application using familiar Redis-style caching commands, Valkey is worth evaluating. For an existing application, start with its supported server versions, client library and modules. A successful connection is only the first compatibility check.

Valkey 9.2 was announced on 19 November 2026. Its snapshot, replication and access-control changes make this a useful time to review how an in-memory datastore fits a small VPS. This guide focuses on the decisions that affect a real deployment, including RAM limits, eviction, recovery and migration.

A new cache deployment

Check that your application supports Valkey, then test its normal reads, writes and expiry behaviour. Give the cache an explicit memory budget before sending production traffic.

An existing Redis workload

Record its exact version, modules and persistence format. Rehearse the migration with representative data and keep a tested route back to the original service.

Queues and important state

Check the application's recovery requirements. Decide which data can expire or be evicted, and test how workers respond to memory pressure and restarts.

Valkey vs Redis at a glance

Check the exact release and application requirements before choosing either server.
DecisionValkeyRedis
LicenceBSD 3-ClauseRedis 8 and later offer AGPLv3, RSALv2 or SSPLv1
Application supportRESP protocol with its own evolving featuresCheck the application's supported Redis release and features
Moving existing dataOfficial migration guidance covers Redis OSS 7.2 and earlierCE 7.4 and later data files require a different migration approach

Valkey's licence file and Redis's licensing overview describe the terms. Older Redis versions have different licences. Review the actual version and distribution you intend to use.

What Valkey 9.2 changes for VPS operators

The Valkey 9.2 announcement highlights three practical additions.

  • Opt-in forkless snapshots can avoid the copy-on-write overhead of a fork during supported background saves. Enabling the infrastructure adds four bytes per key, and the preferred mode can fall back to forking.
  • Compressed replication offers LZ4 or Zstandard options. This may help when moving changes between servers, with compression work and build requirements to assess.
  • ACL roles let administrators reuse permission rules across users, making a shared access policy easier to maintain.

These features need deliberate configuration and testing. Forkless snapshots still use memory, compression still consumes resources, and neither establishes how much traffic your VPS can serve. Read the release notes for behaviour changes before an upgrade.

Redis protocol compatibility needs an application test

Valkey supports RESP2 and RESP3, the protocols used by Redis clients. That makes existing libraries a useful starting point. It does not establish that every newer Redis command, module or application integration behaves identically.

Make a short inventory of the commands your app uses, required modules, Lua scripts, transaction behaviour and authentication settings. Include session expiry, reconnects and background workers in your tests. A cache that passes a simple connection test can still fail when a worker uses a missing feature.

Check your library's support matrix and Valkey's client listings. Prefer an explicitly supported combination. If an application requires a particular Redis module, confirm that requirement with its maintainers before replacing the backend.

How much RAM does Valkey need on a VPS?

Plan around the entire server. The operating system, application, database and datastore all need RAM. Our starting suggestion for a lightweight application and modest cache is a 2 GB VPS, subject to measured memory use. This is sizing guidance rather than a capacity benchmark.

As an illustration, treat a 2 GiB guest as a 2,048 MiB budget. Reserving 384 MiB for the OS, 640 MiB for the application and 512 MiB for cache accounting leaves 512 MiB for other overhead and peaks. Your application may require much more, especially if it also runs a relational database.

maxmemory controls eviction accounting. It does not cap the process's complete resident memory. Replication and AOF buffers can sit outside that accounting, while allocator overhead and persistence activity also need room. A container's hard memory limit must allow those needs above the dataset budget. See the memory-limit documentation.

Use your existing authenticated connection to inspect the server. Supply the correct host, user and TLS options for your setup. These are read-only checks, although CONFIG GET needs appropriate administrative permission.

valkey-cli INFO server
valkey-cli INFO memory
valkey-cli CONFIG GET maxmemory
valkey-cli CONFIG GET maxmemory-policy
valkey-cli INFO persistence

For an interactive password prompt, add --askpass to the CLI invocation. Avoid putting passwords directly in command arguments. The official CLI reference explains authentication and TLS options.

In INFO output, compare used_memory with used_memory_rss, watch peaks and inspect persistence status. Identify Valkey using server_name and valkey_version, since a Redis compatibility version may also appear.

Choose an eviction policy for the data

For disposable cached results that your application can rebuild, an initial configuration might contain the following settings.

# Example for a rebuildable cache
maxmemory 512mb
maxmemory-policy allkeys-lru

allkeys-lru can remove less recently used keys as memory fills. Do not copy this policy into a queue or session store without understanding the consequences of losing those entries.

noeviction avoids that automatic removal, but writes that require more memory can fail at the limit. The application must handle failures. Separate disposable cache data from important queued work when their retention policies differ.

Choose recovery behaviour before enabling persistence

RDB snapshots capture a point in time. Writes after the last usable snapshot may be lost after a failure. AOF records write operations, with durability affected by its flush policy. It also adds disk activity and requires space for ongoing files and maintenance. Valkey documents these choices in its persistence guide.

For a rebuildable cache, decide whether recovery is quicker by restoring data or allowing the application to refill it. For queues or important state, define acceptable data loss and recovery time before choosing settings.

Keep independent copies and test them on the intended restore version. A VM backup and an application-consistent datastore archive serve different recovery needs. Neither a replica nor a persistence file on the same disk provides a complete backup plan.

Keep the datastore on a private connection

Valkey's security model assumes trusted clients. Avoid publishing port 6379 to the internet. On one VPS, use an appropriate local connection or private Docker network. Across VMs, restrict access to the application servers over an available private LAN and firewall the service.

Use authentication with narrowly scoped ACL permissions. Add TLS where the connection needs encryption and verify certificates. A private address does not replace authentication or access rules. Keep administrative access separate from the application's routine account.

Place the app and datastore close together. A cache queried repeatedly during a request can become sensitive to network round trips. Cross-region replication needs its own latency, transfer and recovery assessment.

Plan a Redis-to-Valkey migration you can reverse

The official migration guide covers Redis OSS 7.2 and earlier. Redis CE 7.4 and later produce incompatible data files, so copying their snapshot into Valkey is not a supported shortcut. Investigate an appropriate logical migration method for your source version.

  1. Record the source version, data types, modules and application dependencies.
  2. Restore a compatible backup into an isolated test environment.
  3. Exercise application features, expiry and recovery under representative load.
  4. Plan the write cutover and rollback, including any writes made after switching.

Keep the original environment available until you have verified the new service and recovery process. Two running servers do not automatically provide a safe rollback if their data has diverged.

Match the VPS to your application and memory budget

HYEHOST Cloud VPS is available in Wolverhampton, Ashburn and Auckland. Choose the region near your application and compare its transfer allowance. For a larger datastore or application stack, VDS offers dedicated CPU threads and larger RAM allocations. Size for measured peaks and recovery work as well as normal traffic.

Valkey vs Redis VPS FAQ

Can I use Valkey with a Redis client?

Many clients use the same protocol. Verify your application's supported versions, commands and modules before switching.

Is Valkey free to use?

Valkey is available under the BSD 3-Clause licence. Hosting and ongoing administration are separate costs.

Can I copy Redis 7.4 data files into Valkey?

Redis CE 7.4 and later data files are incompatible. Plan a migration method suitable for your source version.

Is maxmemory the same as a Docker memory limit?

No. It governs eviction accounting. Track process memory separately and allow headroom for buffers and persistence.

Does Valkey 9.2 remove persistence memory overhead?

No. Forkless snapshots are opt-in and still need memory. Measure persistence peaks and leave headroom.

Which HYEHOST region should I choose for Valkey?

Keep the datastore near your application. HYEHOST Cloud VPS is available in Wolverhampton, Ashburn and Auckland. Compare the selected region's resources and transfer allowance.