Mamluk console
One place for everything a Mamluk customer holds: BKE and Kipchak Enterprise licences, the documentation for the version you run, your support tickets — and a 14-day BKE trial that no salesperson stands in front of.
An account is free and requires no purchase.
Evaluate BKE
Enterprise Kubernetes is ordinarily evaluated through a sales process: a call, a scoping conversation, an evaluation agreement, and then the software. BKE's trial removes all of it. Create an account, name your organisation, and issue yourself a trial licence — the whole path is a few minutes, asks for no payment details, and ends with a registration command you paste onto your first node.
What you evaluate is the product, not a demonstration of it. BKE has no editions and no feature gates — a trial licence installs exactly the distribution a paid licence installs, on your own machines, against the same published requirements.
A trial runs for 14 days, and one is live per organisation at a time. When it lapses, the licence stops you installing and upgrading; it does not stop the cluster. Nothing of ours sits in the request path of your workloads, so a cluster you built during the trial keeps serving while you decide.
After you sign in
Every BKE and Kipchak Enterprise licence your organisation holds, in one list: which cluster each is bound to, when it expires, and the registration command for a new cluster. A licence covers one cluster and is independent of node count.
The BKE installation and operations documentation, versioned with the product rather than with a website — choose the version your cluster runs and read the pages that describe it, including the release notes.
Raise a ticket and read the replies in the same place. Tickets are answered by the engineers who build the product, in a timezone adjacent to yours — there is no first line to get past.
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.
One more thing it is not
The console manages licences; it does not manage clusters. Your licence is checked when you install, upgrade or change components — never while your cluster runs — and no agent of ours runs inside it. If the console is unreachable, or we are, a running cluster does not notice.