Bahriya Tersane · ter-SAH-neh
Production Helm charts and operators for the platform above your cluster.
Databases, caches, identity, a container registry and continuous integration, packaged as the charts that run bahriya.cloud and licensed for installation on your own premises, including your own cloud accounts. Where a service is best run by a Kubernetes operator, its chart installs the operator. They are built for the Bahriya Kubernetes Engine and its defaults, and install on any conformant Kubernetes distribution.
On your premises
The charts install inside your perimeter. No data leaves it.
The charts we run
The same charts operate the managed services on bahriya.cloud.
One licence per organisation
Not per cluster, node or core. Supported from within the GCC.
The catalogue
Every capability a platform needs, as a chart you can read.
Data
- mysql · MySQL, standalone or as a highly available cluster
- postgresql · PostgreSQL
- cloudnative-pg · CloudNativePG, the operator that runs the PostgreSQL clusters, installed once per cluster
- valkey · Valkey, standalone, with Sentinel, or sharded
- memcached · Memcached
- couchdb · Apache CouchDB, a document database
- opensearch · OpenSearch, for search and log analytics
- velero · Velero, for backing up and restoring cluster resources and volumesUnder consideration
Messaging
- rabbitmq · RabbitMQ, a message broker
- kafka · Apache Kafka, for event streaming
Identity
- keycloak · Keycloak, for identity and single sign-on
Registry and CI
- harbor · Harbor, a container image and chart registry
- onedev · OneDev, for Git repositories with code review, issues, and container, npm and Maven registries
- concourse · Concourse, for continuous integration and delivery
Workloads
- safeena (ship) · Web services, with ingress, TLS and autoscaling
- khadim (servant) · Workers and daemons
- saat (hour) · Scheduled jobs
- sipar-gateway (shield) · The gateway for a cluster, installed once per cluster, with address-based access control for TCP clients and a response cache, each behind a switch
- sipar-route (shield) · A library chart, used inside an application's own chart and never installed on its own, that renders the application's entry on the cluster's Sipar gateway, with its access, rate-limit and cache policies; it needs sipar-gateway
Security
- clamav · ClamAV, as a shared malware scanner in the cluster
- openbao · OpenBao, for secrets management
- secrets-store-csi-driver · The Secrets Store CSI driver, which mounts secrets into Pods as files through a provider
- kyverno · Kyverno, for admission policy
- policy-reporter · Policy Reporter, a view in the cluster of Kyverno's policy reports
- trivy-operator · Trivy Operator, for scanning the images running in the cluster
- logging · Cluster logs in OpenSearch, with the Kubernetes audit log, dashboards and alerts
Each chart is documented in full: its values, its upgrade path and the decisions it makes on your behalf. Browse the chart documentation
Convoys
Specialist additions to Tersane.
A convoy is an optional addition that carries what one industry or one requirement needs. It installs on top of Tersane and is licensed separately.
The on-premises installation, and the upgrades, of digital banking applications from specialist vendors, provided by Mamluk. Together with BKE and Tersane, your bank can run its digital banking ecosystem in its own data centre.
Read about the Banking ConvoyThe Bahriya Kubernetes Engine decides the network fabric and the Kubernetes version. Tersane supplies what runs above them.
Together they are the combination that runs bahriya.cloud: a platform assembled from parts you can name, version and keep.
Tersane may also be licensed on its own, for any conformant Kubernetes distribution. The charts ship with the Bahriya Kubernetes Engine's defaults, so running them elsewhere calls for experience with Kubernetes and the components the charts expect, or for Mamluk's engineering services.
About the Bahriya Kubernetes Engine Running Tersane without BKE
From the Journal
Announcements, press releases and articles.
The latest about Tersane, published on the Mamluk Journal.
Press release · 19 November 2026
The Compliance and Assurance Convoy adds the Central Bank of Iraq's Cyber Resilience Controls
The Compliance and Assurance Convoy for Bahriya Tersane now evidences the Central Bank of Iraq's Cyber Resilience Controls and Banking Reform Standards B2, B3, B7 and B9: 524 requirements under the CBI's own numbering, each shown as Controls or Standards.
Read on mamluk.net →Press release · 18 November 2026
The Compliance and Assurance Convoy adds MAS Technology Risk Management
The Compliance and Assurance Convoy for Bahriya Tersane now evidences the Monetary Authority of Singapore's Technology Risk Management Notices and Guidelines: 259 requirements under MAS's own numbering, each shown as binding or guidance.
Read on mamluk.net →The name
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. English took arsenal from the same root.
Licensing
Tersane is licensed per organisation, per year, with the Bahriya Kubernetes Engine or on its own. With BKE it costs USD 60,000 a year; on its own, the price is on request.
Enquire about a licence