Announcement
BKE has its own home: bke.bahriya.cloud
The Bahriya Kubernetes Engine now has a dedicated website: bke.bahriya.cloud. It carries the product argument in full — the two decisions BKE makes and the many it deliberately does not, named comparisons with OpenShift, Rancher, Tanzu and Talos, and pricing worked into the per-core unit those products are quoted in.
The documentation is now public
The larger change is the documentation. The complete installation and operation documentation — seventeen pages, from what a node needs through installing, upgrading, storage, ingress and cluster login — is now public at bke.bahriya.cloud/docs, with no account in front of it. They are the same pages our customers operate from, not a summary written for marketing.
We did this for a plain reason: BKE is evaluated the way open-source software is evaluated, through a self-service trial rather than a sales process, and an evaluation is only as good as what you can read before it. It also means the engineer on shift at a customer no longer needs a console login to read an upgrade procedure.
One thing stays with the licence: each release’s notes, which state the exact versions it pins, remain in the console. Which versions a cluster runs is its operator’s business and nobody else’s.
Where things live now
- bke.bahriya.cloud — the product, the documentation, and a guided evaluation path from three Debian servers to a working cluster in an afternoon.
- The console — licences, release notes, support, and the self-service 14-day trial.
- mamluk.net — the brief, the requirements and the pricing, as before.
BKE remains the engine our own public cloud runs on. That has not changed; it is now simply easier to read about.