Legal
The terms on which Mamluk LLC-FZ licenses the Bahriya Kubernetes Engine, including the warranty, cluster reporting and support levels. Effective 20 September 2026.
These terms govern the licensing of the Bahriya Kubernetes Engine (“BKE”) by Mamluk LLC-FZ, a free zone limited liability company incorporated in the Meydan Free Zone, Dubai, United Arab Emirates, with company registration number 2652439 and registered address at Meydan Grandstand, 6th Floor, Meydan Road, Nad Al Sheba, Dubai, United Arab Emirates (“Mamluk”), to the organisation named in the applicable Order or trial registration (the “Customer”). They apply to every licence Mamluk issues for BKE, including trial licences, together with the Order under which a paid licence is purchased. If an Order conflicts with these terms, the Order prevails for that licence.
1.1 In these terms:
bke- prefix and labelled app.kubernetes.io/managed-by: bke, so that the Customer can enumerate at any time exactly which objects these terms cover, for example with kubectl get clusterrolebindings,clusterroles -l app.kubernetes.io/managed-by=bke./etc/bke/config.yaml on the Customer’s nodes, through which BKE’s behaviour is configured.2.1 Subject to payment of the applicable fees and to these terms, Mamluk grants the Customer a non-exclusive, non-transferable licence, without the right to sublicense, to use BKE to install, upgrade and operate one Cluster per Licence Key for the Customer’s internal business purposes during the licence term stated in the Order.
2.2 One Licence Key licenses one Cluster. A Licence Key becomes bound to a Cluster at registration, when the control-plane endpoint and a machine fingerprint are recorded against the licence. Use of one Licence Key on more than one Cluster is a material breach of these terms.
2.3 Rebinding a Licence Key to replacement hardware is a support action, performed by Mamluk on the Customer’s request at the applicable support level (clause 9).
2.4 A licence is at all times in one of the following states: active, suspended, revoked or expired. The state of a licence governs artifact delivery and support under clauses 5 and 9; it has no effect on software already installed on a running Cluster (clause 5.3).
2.5 The Customer must keep each Licence Key confidential and restrict access to it to personnel who need it to operate the licensed Cluster.
3.1 Mamluk may issue one trial licence per organisation. A trial licence is valid for fourteen days from issue, is provided free of charge, and is subject to these terms in full, save that clause 8 (warranty) does not apply and the trial is provided as is.
3.2 Either party may end a trial at any time without notice or liability. Nothing obliges the Customer to purchase, or Mamluk to offer, a paid licence at the end of a trial.
4.1 Fees are as stated in the Order. Mamluk issues invoices from its accounting system; each invoice is payable within 30 days of its date, without set-off or deduction.
4.2 All fees are stated exclusive of value added tax. Where VAT is chargeable under Federal Decree-Law No. 8 of 2017 (as amended) it is added at the prevailing rate and shown on the invoice.
4.3 A paid licence is activated, and a renewal takes effect, when Mamluk records the corresponding payment. If an invoice remains unpaid 14 days after Mamluk gives notice of non-payment, Mamluk may suspend the licence until payment is received.
5.1 BKE installation artifacts are delivered through an authenticated service operated by Mamluk. The Licence Key is the credential for that service, and installation and upgrade require it.
5.2 The delivery service refuses requests where the licence is not active, where the Licence Key is not bound to the requesting Cluster, or where the requested versions do not correspond to a supported position or adjacent upgrade on the Version Graph.
5.3 Licensing is enforced at provisioning only. Nothing in BKE disables, degrades, expires or interferes with software already installed on a running Cluster, and no state of the licence — including suspension, revocation and expiry — has any effect on a running Cluster. The effect of an inactive licence is confined to artifact delivery under this clause 5 and support under clause 9.
6.1 The Components are third-party open-source software and are licensed to the Customer under their own licence terms, not under these terms. Nothing in these terms limits, conditions or adds to the rights those licences grant the Customer, and those rights survive the expiry or termination of a BKE licence.
6.2 What Mamluk licenses under these terms is the distribution: the selection, version pinning and tested combination of the Components on the Version Graph, the scripts that install and upgrade them, and the delivery and support services. Mamluk serves Component images from its own registry mirror and does not modify upstream software except as stated in the Documentation.
7.1 BKE installs a scheduled reporting job in the bahriya-system namespace on every installation. The Reporting Job sends a report to Mamluk no more than once per day. It is enabled by default, and this clause states plainly what it sends and what it is for.
7.2 The report contains, and is limited to: the licence identifier; the Cluster’s Kubernetes cluster UID; the machine fingerprint stored at installation; the BKE version; the Kubernetes version reported by the API server; the set of installed Components with their versions; the node count; and any drift acceptances recorded under clause 8.6. It contains no workload names, no namespace listings, no personal data, and nothing drawn from the Customer’s data. Mamluk will not expand this list except by an amendment to these terms.
7.3 The report is telemetry for support and licence administration only. It gates nothing: no licence state, no delivery decision and no feature depends on it, and receiving no reports from a Cluster is treated as evidence of nothing.
7.4 The Customer may disable reporting by setting reporting.enabled: false in the Configuration File. Disabling it removes the Reporting Job from the Cluster and carries no consequence of any kind: nothing expires, no feature is withheld, and no request is refused on account of it. The only effect is that Mamluk will not know the Cluster’s component versions when the Customer requests support.
7.5 The report contains no personal data within the meaning of Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data. Organisation and billing contact details provided at registration or in an Order are processed by Mamluk for account administration, invoicing and support.
8.1 Mamluk warrants to the Customer, for the duration of the licence term, that: (a) the BKE scripts, used as described in the Documentation, perform materially as the Documentation describes; (b) each published position on the Version Graph is a combination of Kubernetes and Component versions that Mamluk has tested together and itself operates; and (c) an upgrade between adjacent positions on the Version Graph, performed as described in the Documentation, materially preserves the operation of the installed Components.
8.2 The Customer’s sole and exclusive remedy for breach of clause 8.1 is that Mamluk will correct the non-conformity or re-perform the affected installation or upgrade within a reasonable period, and, if it fails to do so, refund a pro-rata portion of the fees paid for the affected licence corresponding to the unexpired remainder of the then-current licence period, whereupon that licence ends. No refund is payable in respect of the period during which the licence was in use.
8.3 The warranty in clause 8.1 applies to a Cluster only while: (a) every BKE Object on it remains in the state BKE defined (clause 8.4); (b) it runs a published position on the Version Graph reached by supported upgrades between adjacent positions; and (c) changes to BKE’s behaviour are made through the Configuration File and the Customer’s own values and secrets as the Documentation describes.
8.4 The Customer must not modify or delete a BKE Object. Every BKE Object is identifiable and enumerable as described in clause 1.1, so the scope of this obligation is always visible to the Customer on its own Cluster. If a BKE Object is modified or deleted other than by BKE, the affected Cluster is out of warranty from the time of the change until the object is restored to its BKE-defined state. The supported route to different behaviour is the Configuration File, which survives upgrades; direct edits to BKE Objects do not. The Customer remains free to create and manage objects of its own under any name that does not carry the bke- prefix or the app.kubernetes.io/managed-by: bke label, and such objects are outside the scope of this clause.
8.5 The Customer holds full administrative control of its own Cluster, and Mamluk does not and cannot technically prevent modification of BKE Objects. Clause 8.4 is a contractual obligation. BKE detects divergence from the defined state of BKE Objects at upgrade and reports it rather than repairing it; BKE will not silently revert a change the Customer has made.
8.6 Where an upgrade detects that a BKE Object has diverged from its defined state, the upgrade refuses and names each affected object. The Customer may direct the upgrade to proceed by expressly accepting the named objects for that run. Such an acceptance is the Customer’s written instruction to proceed; the accepted objects remain subject to clause 8.4, and the affected Cluster remains out of warranty until they are restored.
8.7 The warranty in clause 8.1 does not extend to: (a) defects in a Component as delivered by its upstream project, as distinct from its selection, combination or installation by BKE; (b) the content of the Customer’s own configuration values and secrets; (c) the Customer’s infrastructure, operating systems, networks or DNS; or (d) use of BKE otherwise than as described in the Documentation.
8.8 Except as expressly stated in this clause 8, and to the fullest extent permitted by UAE law, all other warranties, conditions and representations, express or implied, are excluded.
9.1 Unless the Customer has purchased a support plan under an Order, support is provided at the baseline level described in this clause 9.1 and clause 9.2. The baseline level applies during a trial and to every paid licence for which no support plan has been purchased. At the baseline level, the Customer may raise support tickets through the channel stated in the Documentation, and Mamluk will respond within three working days of receipt, irrespective of the severity of the matter reported. A working day is a business day in the Emirate of Dubai, excluding public holidays observed in the United Arab Emirates.
9.2 At the baseline level, corrections, patches and other changes to BKE are delivered only through the regular releases of BKE. Mamluk publishes releases at its discretion — which may be up to a few times in a month — and determines the content and timing of each release; no patch, hotfix, workaround or other software change is provided outside those releases, and no commitment is made that any particular correction will be included in any particular release.
9.3 Where the Customer purchases a support plan under an Order, support is provided on the response terms of the applicable support schedule, which apply in place of clauses 9.1 and 9.2 to the extent they provide otherwise. Rebinding under clause 2.3 and recovery assistance are support actions at the applicable support level.
10.1 Mamluk may suspend a licence for non-payment under clause 4.3, and may suspend or revoke a licence where the Customer is in material breach of these terms — including use of one Licence Key on more than one Cluster — and, where the breach is capable of remedy, has not remedied it within 30 days of notice. The effect of suspension and revocation is as stated in clause 5.3.
11.1 Each licence runs for the term stated in the Order and ends on expiry, revocation, or termination of these terms. Either party may terminate these terms by notice if the other commits a material breach and, where the breach is capable of remedy, fails to remedy it within thirty days of notice.
11.2 On expiry or termination: artifact delivery and support cease; the Customer’s licence to use the BKE scripts and delivery service ends; and clauses 6.1, 7.5, 8.8, 12, 13 and 15 survive. Software already installed on the Customer’s Clusters continues to run and is unaffected (clause 5.3), and the Customer’s rights in the Components under their own open-source licences continue unaffected (clause 6.1).
12.1 Nothing in these terms excludes or limits any liability that cannot be excluded or limited under UAE law, including liability arising from fraud or wilful misconduct.
12.2 Subject to clause 12.1, neither party is liable to the other for loss of profits, loss of revenue, loss of business, or loss or corruption of data, nor for any indirect or consequential loss. The Customer is responsible for maintaining backups of its own data and Clusters.
12.3 Subject to clause 12.1, each party’s total aggregate liability arising out of or in connection with these terms in any twelve-month period is limited to the fees paid or payable by the Customer to Mamluk in the twelve months preceding the event giving rise to the claim.
13.1 Each party must keep confidential the non-public information of the other received in connection with these terms, use it only for the purposes of these terms, and disclose it only to those of its personnel and advisers who need it and are bound by equivalent obligations, or where disclosure is required by law or a competent authority.
14.1 Neither party is liable for failure or delay in performing its obligations, other than an obligation to pay, to the extent caused by circumstances beyond its reasonable control, provided it notifies the other party and resumes performance as soon as reasonably practicable.
15.1 These terms and the applicable Orders are the entire agreement between the parties concerning BKE and supersede all prior discussions on the subject. Variations must be agreed in writing. Neither party may assign these terms without the other’s prior written consent, not to be unreasonably withheld. A failure to enforce a provision is not a waiver of it. If a provision is held invalid, the remainder continues in force. Notices must be given in writing to the addresses stated in the Order. These terms are executed in English; if a translation is produced, the English text prevails to the extent the applicable law permits.
16.1 These terms are governed by the federal laws of the United Arab Emirates as applied in the Emirate of Dubai. The parties agree, pursuant to Article 5(A)(2) of Dubai Law No. 12 of 2004 (as amended), that the Courts of the Dubai International Financial Centre have exclusive jurisdiction over any dispute arising out of or in connection with these terms, and each party waives any objection to that forum.
Questions about these terms may be sent to Mamluk directly.