The platform step
The distribution becomes a platform. By purchase, not by migration.
BKE is deliberately not a platform — that is the point of it. But the platform step exists, it is one commercial decision rather than an engineering project, and it is the exact pairing that runs our own public cloud.
The pairing
BKE, plus the Mamluk Enterprise Helm Charts.
A BKE cluster with its components enabled can carry production. A platform is the next thing up: the stateful services applications depend on — databases, caches, message brokers — production-ready, with replication, backups and upgrade paths already decided by someone who operates them.
That layer is the Mamluk Enterprise Helm Charts: opinionated, production-hardened and continuously patched charts for MySQL, Valkey, message brokers and more, licensed for on-premise use. Install them on BKE and the ground OpenShift occupies is assembled from parts you can name, version and keep.
BKE
The engine.
Two decisions, pinned to the exact patch: the network fabric and the Kubernetes version.
your components
A production cluster.
Storage, ingress, certificates, mesh and observability — enabled one line each, only the ones you want.
Enterprise Helm Charts
A full platform.
Production-ready MySQL, Valkey and message brokers, with replication, backups and upgrade paths already decided.
The proof
This pairing runs bahriya.cloud.
The managed services on our public cloud — containers, managed data services, all of it — run on BKE with these exact charts, carrying paying customers across multiple regions. The charts are not an integration we tested against the distribution; they are what the distribution was built to carry, patched continuously because our own production depends on them first.
What you license on-premise is the same artefacts, not a derivative: the platform we operate, in your data centre, under your control.
What this replaces
The alternative is a platform vendor's bundle, or building it yourself.
Against the bundled platform.
A platform product decides these layers for you and licenses the whole, usually per core. The pairing reaches the same ground in two named parts — the engine and the charts — each priced flatly, each replaceable, and neither hiding the other's cost inside a bundle.
Against building it yourself.
Production MySQL on Kubernetes is not an install; it is replication topology, backup verification, failover behaviour and an upgrade path, maintained forever. The charts are that work already done — and done by a team that answers for it in its own production, every day.
The charts are licensed through Mamluk.
The full brief — what the charts cover, and how they are licensed for use on BKE or any upstream-compliant distribution — is on mamluk.net.