Press Release
Bahriya launches Managed Valkey, its first managed persistent service
DUBAI, UNITED ARAB EMIRATES — 20 August 2026 — Bahriya, the first public cloud provider built in the United Arab Emirates, today announced the general availability of Managed Valkey — a fully managed, Redis-compatible in-memory data store engineered and operated by its team in Dubai.
Managed Valkey is the first persistent managed service on the Bahriya platform. Every instance is created with a declared purpose: a cache, which holds data in memory only and evicts under pressure, or a store, which persists to disk, survives restarts and backs itself up on a schedule. The platform’s existing Managed Memcached service remains a volatile cache; Valkey is the first offering on which customers can keep data they would mind losing.
Built for enterprise requirements
The service ships with the controls enterprise and regulated customers ask for first:
- Bring your own key for TLS — the platform issues and maintains a certificate bundle covering every name an instance answers to, including custom hostnames. Customers who prefer to control their own chain of trust can supply their own certificate and key bundle instead.
- Automated backups and self-service restoration — store instances snapshot on a cron the customer controls, with the last seven days retained at no additional charge. Restores are performed from the console or the Reis CLI without raising a ticket.
- Exposure that cannot be misconfigured — instances are project-private by default, and external access is TLS-only, authenticated and IP-allowlisted, always. The platform rejects any configuration missing one of the three.
- Choice of failure tolerance — single-node, highly available with automatic primary promotion, or sharded cluster, each with a live cost estimate before creation.
“Persistence changes what customers are willing to put on a platform,” said Meezaan-ud-Din, Founder of Mamluk, which operates Bahriya. “A cache you can lose is an easy first step. A data store you back up, restore, and terminate TLS on with your own key is a different level of commitment — and it is one we can make because the people who built it are here in Dubai, in the same time zone and under the same jurisdiction as the customers relying on it.”
Designed to sit alongside containers
Valkey is intended to be deployed next to workloads already running on Bahriya Containers, reachable at its handle on the standard port from any container in the same project. Its publish/subscribe channels and streams make it a natural backbone for presence, notifications, job queues and live updates between services — the pub/sub patterns container-based applications typically reach outside the platform to satisfy. Combined with Managed Memcached for volatile caching, customers can now run the application tier, the cache and the message fabric inside a single project-private network.
Instances are region-local by design — each region runs an independent copy with its own data, rather than one cluster stretched across regions — and are manageable from the console, the Reis CLI and the Terraform provider from day one. Documentation covering topologies, connecting, eviction policies, persistence, backups and external access is available in the Valkey knowledgebase.
What follows
Managed Valkey is the first of a series of persistent data services planned for the platform. Managed MySQL, bringing relational SQL workloads to Bahriya, and managed CouchDB, a globally distributed multi-region document database, are both scheduled to follow.
About Bahriya
Bahriya is a public cloud built in the United Arab Emirates, offering container deployment, managed caching and managed data services across multiple regions. It is operated by Mamluk LLC-FZ and runs on the Bahriya Kubernetes Engine — the only enterprise Kubernetes distribution developed and supported from within the GCC.
For media enquiries, contact uae@mamluk.net.