VALKEY // DATABASES
Valkey on Your Cluster
Provision Valkey for cache-first or durable key-value workloads on your own cluster. Standalone or primary + replicas, configurable persistence, ACL auth, and exporter-backed insights — running on your infrastructure.
Powered by Valkey
Available versions
FEATURES // VALKEY
Fast Key-Value, Your Way
Edka provisions Valkey on your own cluster and gives you a clean control surface for day-2 operations. The data stays in your cloud account.
Topology & Posture
Tune Valkey for cache or durability.
- Standalone or primary + replicas
- Cache-first or durable usage posture
- Node-pool placement and taint tolerations
Persistence
Choose how much state survives restarts.
- None, RDB, or RDB + AOF persistence
- Sizable storage when persistence is enabled
Replication Safety
Keep replicated topologies healthy.
- Optional read service for replication mode
- Write-safety thresholds for replicated topologies
Access & Security
Authenticate and expose Valkey securely.
- Managed ACL auth for the default user
- LoadBalancer, private MetalLB, or Tailscale exposure
Insights
Watch throughput and runtime health.
- Runtime metrics
- Exporter-backed insights
Other engines
PostgreSQL 
MySQL 
ClickHouse GET STARTED // NOW
Provision Valkey
Spin up a cache-first or durable Valkey runtime — on your own infrastructure.
Which Valkey versions can I deploy with Edka?
Available versions today: 9.0.2. You pick the version when provisioning the runtime.
Is Valkey on Edka a cache or a durable store?
Either. Run standalone or primary plus replicas, and pick the persistence mode: none, RDB, or RDB with AOF. Storage is sizable when persistence is enabled.
How is Valkey access secured?
Edka manages ACL auth for the default user. Expose the runtime through a LoadBalancer, private MetalLB, or Tailscale.
Where does my Valkey data live?
In your own Kubernetes cluster, on your own infrastructure. There is no hosted database service in between. You keep full control of the runtime and its storage.