Valkey is a community-developed key-value store under the BSD 3-Clause license. It continues Redis OSS 7.2 and supports caching, session storage and pub/sub workloads.

Is Valkey compatible with my Redis code?

Valkey uses RESP2 and RESP3 and supports Redis OSS 7.2 and earlier commands. Existing Redis clients can connect. Test your commands, Lua scripts, modules and client version before moving a production workload; features added in later Redis releases need separate checks.

Why choose Valkey over Redis?

Choose Valkey when you want a community-developed cache under the BSD 3-Clause license while keeping the Redis OSS protocol and client ecosystem. Compare the commands and features your application uses before choosing an engine.

How do I migrate to Valkey?

Start with your Redis version and the data you need to keep. Redis OSS 7.2 and earlier have compatible RDB and AOF formats; data files from Redis CE 7.4 and later are not compatible. Test the target instance, agree a supported data-transfer path with us and verify reads and writes before changing the application endpoint.

How do replicas and failover work?

Replica-enabled operator deployments use Sentinel for primary discovery and failover. Use a Sentinel-aware client with the connection details in the console. A standalone instance has no replica to promote, and replicas do not provide a separate reader endpoint.

Does every instance use both RDB and AOF?

No. Persistence depends on the deployment and parameter group. RDB snapshots and AOF are different ways to persist data; check the settings for your instance rather than assuming both are enabled. Plan backups separately from replicas.

Managed Valkey.
A familiar way to cache.

An open-source cache for your application, managed in Germany. Keep the Redis OSS protocol and client ecosystem for caching, sessions and pub/sub.

Deploy Valkey View pricing

European-owned
German data centers
EU hosted

Your Valkey instance

Available versions: 9.1, 9.0, 8.1, 8.0 and 7.2
License: BSD 3-Clause
Protocol: RESP2 and RESP3
Location: Germany

From €6.49/mo

What customers say

“As a developer and cloud enthusiast, I’ve tried a lot of infrastructure platforms — but DanubeData genuinely stands out as one of the most intuitive, modern, and reliable cloud services I’ve used. From signup to deployment, everything feels thoughtfully designed and developer-centric. Deploying a VPS, cache, or database instance takes under a minute — and that’s not an exaggeration! Their intuitive dashboard and instant provisioning make launching new services effortless, even if you’re just getting started with cloud infrastructure”

Keoma WrightCEO/Founder at OpenWeb.co.za

“I’m running my new project’s backend on DanubeData and the experience has been smooth from day one—deployment is fast, the dashboard feels genuinely developer-friendly, and everything has been stable with no issues so far. Any time I had a question or hit a small blocker, the support was excellent: quick to respond, clear in explanations, and focused on getting me unblocked rather than sending me in circles. If you want EU-based infrastructure without the usual DevOps friction, DanubeData delivers.”

Cristian TorzsaCEO at InnovaSoftware SRL

“ruby/Sinatra invoicing application on a Docker container. Danube data was an obvious choice given its incredibly user friendly dashboard and automatic deployment directly from my GitHub repository via webhook. I've used many other platforms (Google, AWS, Azure), but Danube is the clear winner in terms of ease to configure, clear and honest pricing not to mention the excellent response time. Everything works perfectly so I hardly ever have to pull up the dashboard since I moved to Danube Data.”

Bo PereiraParis-Brest srl

Open source, with familiar clients.

Valkey continues the Redis OSS lineage under the BSD 3-Clause license. Keep the protocol your application already speaks.

A community-developed cache

The code is released under a permissive license. Review the Valkey license and the features your workload needs when choosing an engine.

RESP2 and RESP3 let existing Redis client libraries connect. Compatibility starts with Redis OSS 7.2 and earlier; test commands and features from newer Redis releases individually.

Redis clients to check

Node.js: ioredis
PHP: Predis
Java: Jedis and Lettuce
Go: go-redis
Python: redis-py
Ruby: redis-rb

Use your client's supported connection scheme and the endpoint in the console. Check the client version and any Sentinel settings before deploying.

Configure the cache around your workload.

Choose the settings and replica topology your application needs.

Familiar Redis clients
Use the RESP protocol with existing Redis client libraries. Check any later Redis-specific features before migration.
Configuration for your workload
Parameter groups let you choose supported memory, eviction and persistence settings. The active configuration determines what is written to disk.
Optional replicas
Add replicas for availability. Operator deployments use Sentinel, with connection details for a Sentinel-aware client.
Password authentication
Use the instance credentials and connection details in the console to connect your application.

Move with a tested migration path.

Start with your source version and the data you need to retain.

Check your source
Redis OSS 7.2 and earlier use compatible persistence formats. Redis CE 7.4 and later require a different data-transfer method.
Test your application
Connect a test workload to Valkey. Check the commands, scripts and client settings your application relies on.
Plan the cutover
Confirm the data-transfer path, verify the target data and switch the application endpoint with a recovery plan in place.

Read the official Valkey migration guide for the engine's migration options. Contact us to confirm the supported path for your managed instance.

Valkey pricing

Live plans for memory and persistent storage. Choose your size, then connect your application.

Managed Valkey

Choose the memory and persistent storage your workload needs. Billed hourly, with the monthly rate shown alongside each plan.

DD Puiu
256 MB memory · 2 GB storage
€6.49/mo
€0.0089/hr
DD Rosu
1 GB memory · 4 GB storage
€12.99/mo
€0.0178/hr
DD Dranov
3 GB memory · 16 GB storage
€24.99/mo
€0.0342/hr
DD Razim
6 GB memory · 32 GB storage
€49.99/mo
€0.0685/hr

Deploy Valkey All pricing

Valkey questions

Compatibility, persistence and migration.

Valkey is a community-developed key-value store under the BSD 3-Clause license. It continues Redis OSS 7.2 and supports caching, session storage and pub/sub workloads.
Link to this answer
Valkey uses RESP2 and RESP3 and supports Redis OSS 7.2 and earlier commands. Existing Redis clients can connect. Test your commands, Lua scripts, modules and client version before moving a production workload; features added in later Redis releases need separate checks.
Link to this answer
Choose Valkey when you want a community-developed cache under the BSD 3-Clause license while keeping the Redis OSS protocol and client ecosystem. Compare the commands and features your application uses before choosing an engine.
Link to this answer
Start with your Redis version and the data you need to keep. Redis OSS 7.2 and earlier have compatible RDB and AOF formats; data files from Redis CE 7.4 and later are not compatible. Test the target instance, agree a supported data-transfer path with us and verify reads and writes before changing the application endpoint.
Link to this answer
Replica-enabled operator deployments use Sentinel for primary discovery and failover. Use a Sentinel-aware client with the connection details in the console. A standalone instance has no replica to promote, and replicas do not provide a separate reader endpoint.
Link to this answer
No. Persistence depends on the deployment and parameter group. RDB snapshots and AOF are different ways to persist data; check the settings for your instance rather than assuming both are enabled. Plan backups separately from replicas.
Link to this answer

Explore more solutions

Make Valkey part of your stack.

Choose a plan and connect your application to a managed open-source cache.

Deploy Valkey Compare plans

Start free

Compute

Storage

Managed apps

Caching

Databases

Messaging

Monitoring

DanubeData CLI

Automation & Agents

Tools

Developer docs

Learn

Support

Managed Valkey.
A familiar way to cache.

Your Valkey instance

What customers say

Open source, with familiar clients.

A community-developed cache

Configure the cache around your workload.

Familiar Redis clients

Configuration for your workload

Optional replicas

Password authentication

Move with a tested migration path.

Check your source

Test your application

Plan the cutover

Valkey pricing

Managed Valkey

Valkey questions

Explore more solutions

Make Valkey part of your stack.

Start free

Compute

Storage

Managed apps

Caching

Databases

Messaging

Monitoring

DanubeData CLI

Automation & Agents

Tools

Developer docs

Learn

Support

Managed Valkey.A familiar way to cache.

Your Valkey instance

A community-developed cache

Familiar Redis clients

Configuration for your workload

Optional replicas

Password authentication

Check your source

Test your application

Plan the cutover

Managed Valkey

Make Valkey part of your stack.

Managed Valkey.
A familiar way to cache.