The engine behind Bahriya now has its own home
BKE — the Kubernetes engine every Bahriya region runs on — now has its own home at bke.bahriya.cloud, and its complete installation and operation documentation is public.
Bahriya runs on the Bahriya Kubernetes Engine — BKE, the Kubernetes distribution we build and operate ourselves. Every region, every managed service, every container you run with us is carried by it. Until now, reading about it meant a product page; operating it meant being a customer.
Both halves changed today. BKE has a dedicated site at bke.bahriya.cloud, and its complete installation and operation documentation is public there — the same seventeen pages BKE customers operate from, with no account in front of them.
Why this matters if you run on Bahriya
Transparency about the platform under your workloads. The documentation states precisely what a BKE cluster reports and what it cannot see, how upgrades are classified by what they actually do to a running cluster, and what happens when the licence server is unreachable — nothing, because nothing sits in the data path. Those properties are Bahriya's properties too, because Bahriya is the largest BKE installation there is. You don't have to take them on trust anymore; you can read them.
A few pages worth starting with:
- Cluster reporting — every field a cluster sends, what the reporting job's own permissions can and cannot read, and how to verify both yourself.
- Upgrading — what each digit of a version number promises about a running cluster, before you read a changelog.
- How a cluster fits together — the primer, if Kubernetes itself is the new part.
If you want the same stack in your own data centre
BKE is licensed for on-premise installation, flat per cluster, and evaluated through a self-service 14-day trial — no sales call in front of it. The platform layer above it is available the same way: the Mamluk Enterprise Helm Charts — the production-hardened MySQL, Valkey and message-broker charts that run Bahriya's own managed services — are licensed for on-premise use. BKE plus those charts is, quite literally, this cloud in your data centre. Here's how the platform step works.
Start with the documentation, or go straight to a trial.