Partners
Mamluk works with managed service providers, software vendors and consulting firms whose customers run Kubernetes. Each of them meets the same problem from a different side: an enterprise platform licensed per core takes budget that would otherwise pay for their own services.
Partners
Run Kubernetes for your customers on a flat licence per cluster, with the production data services already built, and quote more of the customer's budget as your own services.
Read more →Stop the platform your application runs on from taking the budget meant for your licence, your customisation and your consultancy.
Read more →Lower the platform cost and the learning curve of a client's programme, and leave more of its budget for the advice and delivery it engaged you for.
Read more →The arithmetic
A worked example: a regulated bank running production, staging and performance testing in 3 clusters, on 320 worker cores in total.
| Platform | Per year | Over 3 years |
|---|---|---|
| OpenShift, 320 worker cores at an assumed USD 1,850 per core | USD 592,000 | USD 1,776,000 |
| BKE for 3 clusters, the Enterprise Helm Charts, and support with a four-hour response time | USD 156,000 | USD 468,000 |
| Difference | USD 436,000 | USD 1,308,000 |
The OpenShift rate is an assumption: a heavily discounted figure, including Red Hat’s support subscription, used because OpenShift is negotiated per customer and no list price applies to any particular one. Substitute the per-core rate from a real quote and multiply it by 320; the BKE figures do not depend on it. Hardware and staff are excluded from both sides. The full example, with each arrangement and the cost of growth, is on the BKE site.
On the assumed rate, OpenShift costs 3.8 times as much. The difference does not shrink as the estate grows: a further worker core adds to a per-core subscription every year, and adds nothing to a BKE licence, which is USD 12,000 per cluster whatever its size.
Whoever delivers the programme, that difference is budget the customer has already approved for its platform. On a per-core subscription it leaves the programme. On BKE it remains available for the services, software and advice the customer is buying from its partners.
What partners work with
Upstream Kubernetes and upstream components, with no fork and no proprietary resource types. Licensed at a flat USD 12,000 per cluster per year, whatever the number of nodes, cores or memory, with every component included.
Production-ready MySQL, Valkey, message brokers and more, with replication, backups and upgrade paths already decided. They are the charts that run the managed services on bahriya.cloud, licensed per organisation for on-premise use.
BKE and the charts are supported by the engineers who develop them, from within the GCC. Support with a four-hour response time and Kubernetes support contracts are available on top of the standard support included with a licence.
A 14-day trial licence is issued from the Mamluk console and installs the complete distribution. The documentation and the node requirements are published in full.
The commercial terms of each partnership are agreed directly with the partner.
A flat licence, and more of the budget for your work.