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 Bahriya Tersane.
A BKE cluster with its components enabled can carry production. A platform is the next thing up: the services applications depend on — databases, caches, message brokers, identity, a registry and CI — production-ready, with replication, backups and upgrade paths already decided by someone who operates them.
That layer is Bahriya Tersane: a catalogue of production Helm charts and operators, organised by function, licensed for installation on your own premises. Each chart carries the operational decisions as well as the software: resource limits, disruption budgets, anti-affinity, backups and an upgrade path. Where a service is best run by a Kubernetes operator, its chart installs the operator. Install Tersane 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.
Bahriya Tersane
A full platform.
Data stores, messaging, identity, a registry and CI, workloads and security, each as a chart or an operator installed by one, with the operational decisions already made.
The catalogue
Every capability a platform needs, as a chart you can read.
Data and messaging.
MySQL, standalone or as a highly available cluster; Valkey, standalone, with Sentinel or sharded; Memcached; and further data stores and message brokers in the catalogue.
Identity, registry and CI.
Identity and single sign-on, a container registry, source control and continuous integration, so that a cluster can build, store and deploy its own images without a separately licensed suite.
Workloads and security.
Charts for your own web services, workers and scheduled jobs, and for antivirus scanning and secrets management alongside them.
Each chart is documented in full: its values, its upgrade path and the decisions it makes on your behalf. The full catalogue on tersane.bahriya.cloud →
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. Tersane is not an integration we tested against the distribution; it is what the distribution was built to carry, patched continuously because our own production depends on it first.
What you license for your own premises is the same charts, not a derivative: the platform we operate, in your data centre or your own cloud account, under your control.
Convoys
Specialist additions, on top of Tersane.
A convoy is an optional addition that carries what one industry or one requirement needs. It installs on top of Tersane and is licensed separately. The Compliance and Assurance Convoy is available: it maps a regulator's technical controls onto your cluster, enforces and checks them, and keeps dated evidence for each regime. The Banking Convoy, through which Mamluk will install and upgrade digital banking applications from specialist vendors on your own premises, the Identity Verification Convoy and the Zero Trust Convoy Coming soon follow.
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. A Tersane chart is that work already done — and done by a team that answers for it in its own production, every day.
Tersane is licensed per organisation.
One licence per organisation, per year, however many clusters it runs on. Tersane is licensed with BKE, or on its own at a higher price for any conformant Kubernetes distribution. The catalogue, the documentation and the licensing are on its own site, and the licence terms are provided with the quotation.