Sessions, queues, counters, pub/sub and caching on the datastore your Redis clients already speak — from a single node to a sharded cluster, managed through the same console, CLI and Terraform provider as the rest of your platform.
Valkey is the Linux Foundation's community fork of Redis 7.2, created when Redis moved away from its open-source licence, and backed by the industry's largest cloud providers. It stays under the permissive BSD 3-Clause licence — the commands, data structures and wire protocol your applications already use, with open governance and no licensing uncertainty underneath them.
Existing Redis client libraries connect unchanged — same protocol, same commands, same semantics, including Sentinel discovery and cluster redirects. Point your connection string at the instance handle on port 6379 and keep the code you have. Migrating off a hosted Redis is a connection-string change, not a rewrite.
Create an instance as a cache (in-memory only, least-recently-used eviction) or a store(disk persistence, storage sizing, eviction off by default, free scheduled backups). The purpose sets honest defaults for what happens when memory fills and what survives a restart — so a full cache drops cold entries while a full store refuses to lose data.
A single node for rebuildable data. A highly available tier with automatic failover in seconds. A sharded cluster that grows capacity with your keyspace. Standard and hardened sizes trade nodes for tighter failure tolerance — and the console shows the derived node count and a live cost estimate before you create anything.
Platform features
Everything an in-memory datastore needs in production — provisioning, security, backups and visibility — without operating any of it.
Topologies
One node, a Sentinel-coordinated highly available tier (3 or 5 nodes), or a sharded cluster (from 6 nodes, growing with shards). The tier decides failover behaviour and which client driver your application needs — and nothing else about your code.
Durability
Store instances persist to disk and recover their data across restarts. Scheduled backups are free — a cron schedule you control, with the last seven days of snapshots retained as your recovery path.
Security
Instances are project-private by default. External exposure requires TLS, authentication and an IP allowlist — all three, enforced by the platform. There is no way to put an open datastore on the internet.
TLS
With managed TLS, the platform issues a certificate covering every name the instance answers to — per-region hostnames, per-node names, and your custom domains — and keeps it current as the instance changes. Or bring your own bundle from the vault.
Multi-region
Each region runs an independent copy with its own data — the right shape for active-active deployments. Your containers always talk to the copy in their own region using the same handle, with no per-region configuration.
Automation
Create and manage instances from the console with a live cost estimate, from the Reis CLI in flag or YAML mode, or declaratively through the Terraform provider — the same resource model as every other Bahriya resource.
Use cases
Valkey's data structures carry real application state — pick the purpose and tier that match what the data means to you.
Session stores, query caches and computed results on a cache instance — least-recently-used eviction keeps the hot set in memory, and eight eviction policies let you tune exactly what gives way when memory fills.
Lists and streams back job queues that must survive a restart — a store instance persists to disk, refuses to evict, and backs itself up on your schedule. Pair it with worker containers in the same project.
Atomic increments, sorted sets and expiring keys make Valkey the natural home for rate limiting, usage counters and ranking — with the highly available tier keeping them online through node failures.
Publish/subscribe channels and streams power presence, notifications and live updates between your services — project-private by default, or exposed externally over TLS to services hosted elsewhere.
Purpose, tier, memory and regions with sensible defaults, a derived node count, and a live cost estimate before you create.
Memory is billed per node, storage per region — the estimate on the form is the same arithmetic as the invoice.
Status, node counts, connection endpoints and credential reveals in the console, with every change in the activity log.
Topologies, eviction, persistence, backups and external access — covered in the knowledgebase with CLI and Terraform examples.
Coming Soon
Planned for later in 2026/2027, timeline subject to change.
Managed relational database with automated backups, point-in-time recovery, and regional deployment. A production-ready RDBMS for structured data and transactional workloads.
Managed PostgreSQL with automated backups, point-in-time recovery, and regional deployment. Advanced SQL features, JSONB support, and extensions for modern application workloads.
A globally distributed, multi-region document database with built-in replication. Conflict-free sync across regions for offline-first applications and geo-distributed NoSQL workloads.
S3-compatible object storage for files, media, backups, and static assets. Accessible from your containers or directly via standard S3 APIs and client libraries.
Global content delivery network for static assets, media, and API acceleration. Edge caching across multiple PoPs with automatic origin pull from your containers or object storage.
Your own dedicated API gateway in front of your services. JWT/OAuth2/OIDC and key auth, fine-grained rate limiting and quotas, request/response transformations, circuit breakers, canary releases and traffic splitting, gRPC and WebSocket proxying, and rich per-route analytics — all configured declaratively via Reis or the Console.
Managed RabbitMQ for asynchronous messaging between containers. Multi-region clusters, project-private networking, and per-node billing — same operational model as Memcached.
Create an instance next to your containers, point your existing Redis client at it, and keep your data on an open-source datastore.
