Managed Dragonfly.
Your cache, managed.

A multi-threaded in-memory store that speaks the Redis protocol. Run your cache in Germany with plans sized by CPU, memory and storage.

Create an account View plans

German data centers
EU hosted

Plans from €8.99/mo.

A familiar protocol. A multi-threaded engine.

Keep the Redis tools you know, and choose the cache engine that fits your application.

Multi-threaded engine
Dragonfly is designed for multi-threaded in-memory workloads. Choose CPU and memory resources for the application you run.
Redis-compatible clients
Connect with familiar Redis libraries. Check your commands and scripts against Dragonfly before changing an existing application.
Familiar data types
Strings, hashes, lists, sets and sorted sets give your application familiar ways to store and retrieve cache data.
Instance monitoring
Track cache memory, connections and activity from the dashboard as your workload changes.

Choose your Dragonfly plan

Compare the CPU, memory and storage available for your cache.

Managed Dragonfly

Choose a resource size for your working dataset and CPU needs. Hourly rates and monthly caps are shown in EUR.

DD Puiu
1 vCPU · 256 MB RAM · 2 GB storage
€8.99/mo
€0.0123/hr
DD Rosu
2 vCPU · 1 GB RAM · 4 GB storage
€18.99/mo
€0.0260/hr
DD Dranov
4 vCPU · 3 GB RAM · 16 GB storage
€37.99/mo
€0.0520/hr
DD Razim
8 vCPU · 6 GB RAM · 32 GB storage
€74.99/mo
€0.1027/hr

Create an account View full pricing

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

Read more customer stories

Dragonfly questions

Compatibility, workload fit and snapshots.

Planning a migration? Talk through your workload with us.

Dragonfly uses a multi-threaded architecture for in-memory workloads. Evaluate it when that architecture fits your cache, and benchmark your own application before choosing an engine or plan.
Link to this answer
Dragonfly speaks the Redis protocol, so you can connect using Redis clients and libraries. Test the commands, Lua scripts and application behavior you rely on before migrating; protocol compatibility does not guarantee every Redis feature behaves identically.
Link to this answer
Consider Dragonfly for application caching and other in-memory workloads that can use its multi-threaded engine. Choose a plan for your working data size and CPU needs, then test it with your application. Existing Redis Cluster deployments need a migration review.
Link to this answer
Dragonfly persists through snapshots rather than AOF. Snapshot schedules and restore behavior depend on your instance configuration. Review those settings and test restores for data you need to retain; writes after the latest completed snapshot can be lost.
Link to this answer

Explore your cache options

Put Dragonfly to work.

Choose your resources, connect your application and test the cache with your own workload.

Create an account View pricing