Commercial product · Tersane

Bahriya Tersane

Production Helm charts for the platform above your cluster, licensed for your own premises.

Bahriya Tersane is a catalogue of production Helm charts: the charts that run the managed services on bahriya.cloud, licensed for installation on your own premises. It was previously offered as the Mamluk Enterprise Helm Charts, and in October 2026 became a product in its own right, with its own site at tersane.bahriya.cloud.

The catalogue is organised by function: data, messaging, identity, a container registry and continuous integration, workloads and security. These are not upstream charts with a new name. Each chart is opinionated about resource limits, pod disruption budgets, anti-affinity, backups, RBAC and the long list of small decisions that decide whether a workload survives a real outage, and each is documented in full: its values, its upgrade path and the decisions it makes on your behalf.

Tersane is built for the Bahriya Kubernetes Engine and its defaults, and is licensed with it or on its own. BKE decides the network fabric and the Kubernetes version; Tersane supplies what runs above them. The charts ship with BKE's defaults, so on another conformant distribution your team supplies the components the charts expect, or changes the charts' settings to use what the cluster provides. That calls for experience with Kubernetes and those components, or for our engineering services.

Convoys are optional additions installed on top of Tersane, each for one industry or one requirement and licensed separately. The first is the Banking Convoy, an experimental app marketplace for existing digital banking platforms.

  • The charts that run the managed services on bahriya.cloud, packaged for installation on your premises.
  • Opinionated, production-hardened defaults for resource limits, pod disruption budgets, anti-affinity, RBAC and backups.
  • A catalogue organised by function, from databases and message brokers to identity, a container registry and continuous integration.
  • A published chart version is never changed or withdrawn, so a release pinned to a version can always be reinstalled.
  • Public documentation for every published chart at tersane.bahriya.cloud, with no account in front of it.
  • Licensed with the Bahriya Kubernetes Engine, or on its own for any conformant Kubernetes distribution.
  • Convoys for one industry or one requirement, installed on top of Tersane. The first, the Banking Convoy, is experimental.
  • Ticketed support and incident escalation aligned to GCC working hours.

A tersane was a naval arsenal, the yard in which a fleet was built and fitted. The Ottoman word came from the Ligurian tersaná, and before that from the Arabic dār aṣ-ṣināʿa, the house of industry.

Talk to the engineers who built it.