Bahriya Cloud reaches general availability with containers, Valkey and Memcached

DUBAI, UNITED ARAB EMIRATES — 31 August 2026 — Bahriya, the first public cloud provider built in the United Arab Emirates, today announced that Bahriya Cloud has reached general availability. The platform leaves early access with container deployment, Managed Valkey and Managed Memcached generally available across four regions, and with sign-up open to all customers without invitation.

Bahriya opened to a small group of early access users in May 2026. In the period since, the platform has added persistent volume storage, network policies, cryptographic and configuration management, per-path traffic rules, worker and cron workloads, a Terraform provider and its first persistent managed data service. General availability marks the point at which the company considers the management surfaces — not just the runtime — stable enough to commit to.

What general availability changes

Early access on Bahriya was always a statement about the interfaces rather than the infrastructure: the runtime executing customer containers has been in production and serving live traffic throughout, while the API, the console and the tooling were explicitly permitted to change shape. That permission now ends.

The v1 API contract is locked. Breaking changes to the published API will require a versioned endpoint and a coordinated migration path, on the terms customers expect from any established provider. The full API reference is published, and every action available in the console remains available programmatically.
Sign-up is self-service. Organisations can register, create a project and deploy without an onboarding call or an invitation code.
The uptime target is published. Bahriya targets 99.95% monthly uptime for the core infrastructure on which customer services run, with service credits payable against the affected resources where the target is missed in a calendar month. The terms are set out in full on the Bahriya terms of service.
Console layout churn ends. The rate of structural change to the console drops sharply now that the platform is out of early access.

Generally available today

The following services are generally available at launch, in every active region, and are manageable from the console, the Reis CLI, the Terraform provider and the API from day one:

HTTP containers — any OCI-compliant image deployed as a global web service, with TLS, GeoDNS, health-check failover and per-region autoscaling.
Worker containers — long-running background workloads with no public ingress, for queue consumers and schedulers.
Cron jobs — any image on a schedule, with per-execution history, exit codes and per-minute billing.
Managed Valkey — the Redis-compatible, BSD-licensed in-memory datastore, as a volatile cache or a persistent store with scheduled backups and self-service restoration.
Managed Memcached — project-private in-memory caching with stable node identities for consistent hashing.
Volume storage — ephemeral scratch space plus replicated SSD volumes that survive restarts.
Network policies — private-by-default project networking with additive ingress peers and egress allow-lists.
Vault and Configs — encrypted keys, TLS bundles, certificates and versioned configuration files, mounted into containers at runtime.

“Early access was never about whether the platform could run production workloads — it has been doing that from the first day,” said Meezaan-ud-Din, Founder of Mamluk, which operates Bahriya. “It was about earning the right to freeze the contract. We told our early customers that we would break the API while it was cheap to break, and that we would stop when it was right. Today we stop. What a customer integrates against now is what they will still be integrating against in three years.”

Regions

Bahriya is generally available in four regions today — Falkenstein and Helsinki in Europe, Ashburn in the United States, and Singapore — with containers deployable to several regions in a single operation and datastores running an independent region-local copy in each. London, Jeddah, Fujairah, Doha, Istanbul, Sydney, Hillsboro, São Paulo and Lagos are on the published roadmap; the current map is maintained at bahriya.cloud/locations. Guidance on region selection and data residency is available in the regions knowledgebase.

Documentation

The Bahriya knowledgebase covers the platform in nineteen sections, from what Bahriya is and deploying a first container through to container configuration, Valkey topologies and backups, Memcached sizing, the security model and how billing is measured. Pricing is published per resource, per region and per minute at bahriya.cloud/pricing, with a 60-second minimum and no committed-spend requirement.

What follows

General availability opens a roadmap of managed services intended to remove the remaining reasons a container-based application has to reach outside the platform. Managed MySQL and PostgreSQL will bring relational workloads to Bahriya, followed by CouchDB for globally distributed document storage, S3-compatible object storage for files, media and backups, and a content delivery network built on the platform’s existing edge. Further regions, including the company’s first in the GCC, are being brought online in parallel.

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.