What's the difference between Redis, Valkey, and Dragonfly?

Redis is an in-memory data store with a broad client ecosystem. Valkey is an open-source fork of Redis. Dragonfly uses a multi-threaded architecture. Choose based on the commands, persistence behavior and resource needs of your application, and test compatibility before switching engines.

Do you provide DNS management for cache instances?

Yes. Public cache instances can enable managed DNS hostnames such as redis-{instance}.{tenant}.danubedata.ro or valkey-{instance}.{tenant}.danubedata.ro. Use the connection details shown in the console for your instance.

Do you support Redis clustering?

Replica support depends on the deployment kind. Supported operator-managed instances can add replicas, with engine-specific failover and client configuration. Replicas do not imply Redis Cluster sharding or a separate load-balanced reader endpoint.

How do I migrate from another Redis provider?

Check the destination engine supports your commands and client library. Test your data import and application in a separate instance, then plan the connection change and any required downtime. Contact support if you need help choosing a migration approach.

What's the data persistence like?

Persistence depends on the engine, deployment kind and parameter group. Redis and Valkey can use RDB snapshots or AOF where configured. Dragonfly uses snapshots rather than AOF. Review your settings and recovery points before relying on the cache for durable data.

Can I clone a cache instance from a snapshot?

Yes, where the snapshot and deployment topology support cloning. Use the available recovery actions in the console to create a separate instance from a recovery point, then verify it before changing your application connections.

Do you have data centers outside Europe?

Our infrastructure is in Falkenstein, Germany. Choose a cache close to your application and test the connection with your own workload.

Managed cache,
your choice of engine.

Redis, Valkey and Dragonfly for sessions, cached responses and pub/sub. Choose an engine, configure your working set and keep an eye on it from one console.

European-owned
German data centers

Entry Redis plans from €6.49/month. About €0.22/day over 30 days. Billed hourly.

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

Choose the engine that fits your application

Start with your client library and commands. Each engine has its own plans and persistence behavior.

Redis 8.6

In-memory data structures for cached responses, sessions and pub/sub messaging.

Explore Redis 8.6

Valkey 9.1

An open-source cache engine derived from Redis, with community governance.

Explore Valkey 9.1

Dragonfly 1.39

A multi-threaded in-memory engine for workloads that can use multiple CPU cores.

Explore Dragonfly 1.39

Manage the cache around your workload

Connection details, metrics and supported recovery actions stay with your instance.

Monitor your working set
View memory use, operations and connections in the console to understand how your cache is being used.
Configure your engine
Use parameter groups to manage supported settings such as eviction and persistence. Available settings differ by engine.
Snapshots and cloning
Create snapshots and clone from a recovery point on a supported topology. Check the available recovery actions for your instance.
Replica options
Supported operator-managed deployments can add replicas. Topology and client connection requirements depend on the engine.
Public DNS
Enable a managed DNS hostname for a public cache instance and use it in your application connection settings.
Optional 10GI UpLink
Eligible instances can add a paid upgrade with up to 10 Gbit/s shared across public and private networking, subject to availability.

Size for your working set

Entry Redis plans are shown below with hourly and monthly rates. Compare Valkey and Dragonfly plans on their engine pages.

Redis plans

Memory, compute and storage are shown for each supplied plan. See each engine page for its own plan choices.

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

Get started View all pricing

All prices in EUR. Check the engine plan and your configured options before deploying.

From engine choice to application connection

Choose your engine
Pick Redis, Valkey or Dragonfly. Check the commands your application uses before choosing an alternative engine.
Set up your cache
Choose a plan, networking and parameter group in the console. Configure replicas where your deployment supports them.
Connect and observe
Use the connection details from your instance, then watch memory use and connections as your application runs.

Cache the data you read often

Use expirations for sessions and cached responses. Other common patterns include rate limiting, background job queues and sorted-set leaderboards, where supported by your engine.

A session with a 24-hour expiry. Set CACHE_URL from your instance connection details and keep it out of source control.

Node.js sessions

import { createClient } from 'redis';
const client = createClient({ url: process.env.CACHE_URL });
await client.connect();

await client.set('session:123', JSON.stringify(userData), {
  EX: 86400
});

Cache a response for one hour. Check your chosen engine supports the commands and client behavior your application needs.

Python API responses

import json
import os
import redis

client = redis.Redis.from_url(os.environ['CACHE_URL'])
client.setex('api:/users', 3600, json.dumps(users))

Cache questions, answered

Engine choices, persistence and recovery.

Read the documentation or ask us about your workload.

Redis is an in-memory data store with a broad client ecosystem. Valkey is an open-source fork of Redis. Dragonfly uses a multi-threaded architecture. Choose based on the commands, persistence behavior and resource needs of your application, and test compatibility before switching engines.
Link to this answer
Yes. Public cache instances can enable managed DNS hostnames such as redis-{instance}.{tenant}.danubedata.ro or valkey-{instance}.{tenant}.danubedata.ro. Use the connection details shown in the console for your instance.
Link to this answer
Replica support depends on the deployment kind. Supported operator-managed instances can add replicas, with engine-specific failover and client configuration. Replicas do not imply Redis Cluster sharding or a separate load-balanced reader endpoint.
Link to this answer
Check the destination engine supports your commands and client library. Test your data import and application in a separate instance, then plan the connection change and any required downtime. Contact support if you need help choosing a migration approach.
Link to this answer
Persistence depends on the engine, deployment kind and parameter group. Redis and Valkey can use RDB snapshots or AOF where configured. Dragonfly uses snapshots rather than AOF. Review your settings and recovery points before relying on the cache for durable data.
Link to this answer
Yes, where the snapshot and deployment topology support cloning. Use the available recovery actions in the console to create a separate instance from a recovery point, then verify it before changing your application connections.
Link to this answer
Our infrastructure is in Falkenstein, Germany. Choose a cache close to your application and test the connection with your own workload.
Link to this answer

Build the rest of your application

Put your cache to work

Choose your engine and plan, connect your application and follow its memory use as it grows.

Create an account View pricing

Start free

Compute

Storage

Managed apps

Caching

Databases

Messaging

Monitoring

DanubeData CLI

Automation & Agents

Tools

Developer docs

Learn

Support

Managed cache,
your choice of engine.

What customers say

Choose the engine that fits your application

Redis 8.6

Valkey 9.1

Dragonfly 1.39

Manage the cache around your workload

Monitor your working set

Configure your engine

Snapshots and cloning

Replica options

Public DNS

Optional 10GI UpLink

Size for your working set

Redis plans

From engine choice to application connection

Choose your engine

Set up your cache

Connect and observe

Cache the data you read often

Cache questions, answered

Build the rest of your application

Put your cache to work

Start free

Compute

Storage

Managed apps

Caching

Databases

Messaging

Monitoring

DanubeData CLI

Automation & Agents

Tools

Developer docs

Learn

Support

Managed cache,your choice of engine.

Redis 8.6

Valkey 9.1

Dragonfly 1.39

Monitor your working set

Configure your engine

Snapshots and cloning

Replica options

Public DNS

Optional 10GI UpLink

Redis plans

Choose your engine

Set up your cache

Connect and observe

Put your cache to work

Managed cache,
your choice of engine.