Announcement
The Mamluk Console is open, and BKE can now be trialled self-service
The Mamluk Console is open. It is the one place a Mamluk customer signs in: the licences an organisation holds, the documentation for the product version it runs, and its support tickets all live there. An account is free, requires no purchase, and takes a minute to create.
The part worth announcing: a BKE trial with nobody in front of it
Enterprise Kubernetes is ordinarily evaluated through a sales process — a call, a scoping conversation, an evaluation agreement, and then the software. As of today, Bahriya Kubernetes Engine is evaluated the way an engineer evaluates an open-source tool.
Create an account, name your organisation, and issue yourself a trial licence. The console hands back a registration command; paste it onto your first node and install. The whole path is a few minutes long, asks for no payment details, and involves no conversation with us unless you want one.
Three properties of the trial are worth stating plainly:
- The trial is the product. BKE has no editions and no feature gates — the licence gates BKE, not parts of it — so a trial licence installs exactly the distribution a paid licence installs, against the same published requirements.
- It runs for 14 days, one live trial per organisation at a time.
- Lapsing is graceful by design. A licence is checked when you install, upgrade or change components — never while your cluster runs — so when a trial ends, what stops is changing the cluster, not the cluster. Whatever you built keeps serving while you decide.
What else the console holds
Licences. Every BKE and Kipchak Enterprise licence your organisation holds, with its binding, its expiry and the registration command for a new cluster.
Documentation. The BKE installation and operations documentation is versioned with the product rather than with a website. Choose the version your cluster runs and read the pages that describe it, release notes included.
Support. Tickets are raised and answered in the console, by the engineers who build the product — there is no first line to get past. Kipchak Enterprise support has run through the console since its announcement; BKE support now lives in the same place.
Your team. Invite colleagues into your organisation by email and decide what each may do: administrators manage licences, billing and membership; support members work with tickets and documentation.
What the console is not
The console manages licences; it does not manage clusters. No agent of ours runs inside your cluster and nothing of ours sits in the request path of your workloads. If the console is unreachable — or we are — a running cluster does not notice.
Start at mamluk.net/console, or go straight to console.maml.uk.