Commercial product · Sipar

Sipar

The gateway and service mesh for Kubernetes, built on open standards and supported from within the GCC.

Sipar is Mamluk's traffic layer for Kubernetes: the gateway through which every request reaches an organisation's applications, and the mesh that secures the traffic between them. It has two parts. Sipar Gateway receives HTTP, TCP and TLS traffic at the edge of the cluster and applies the organisation's rules before any application sees a request: rate limits, a response cache, access by address to databases and other TCP services, a request identifier on every response, and one structured log line for every request. Sipar Mesh gives every workload a cryptographic identity and encrypts the traffic between services with mutual TLS, without changes to the applications.

Every application an organisation runs depends on this layer. An outage in it stops every application behind it, and a change to its supplier's licensing terms reaches every application at once. Mamluk builds Sipar so that this layer has one accountable supplier and no dependency on any single vendor's free edition. It is built on projects of the Cloud Native Computing Foundation, which are governed by many contributing companies rather than one: Envoy and the Kubernetes Gateway API for the gateway, and Istio's ambient mode for the mesh. These projects are used unmodified. Mamluk's own code runs only at the extension points they publish, so an upstream security fix reaches a Sipar cluster without waiting for a modified copy to be brought up to date.

Sipar is included with every Bahriya Kubernetes Engine licence at no extra price, and is part of the Bahriya Tersane licence on other conformant Kubernetes distributions. Its full documentation is public at tersane.bahriya.cloud.

  • One gateway for the cluster's HTTP, TCP and TLS traffic, configured through the Kubernetes Gateway API, an open standard, rather than a proprietary format.
  • Rate limits, a response cache and access control by address for TCP services, applied before a request reaches the application.
  • A request identifier on every response and one structured log line for every request, with no credentials or query strings recorded, so that an incident can be traced from a customer's report to the service that answered.
  • Mutual TLS and workload identity between services with Sipar Mesh, enabled per cluster and per namespace, with no changes to the applications.
  • Built on Cloud Native Computing Foundation projects, used unmodified, with no dependency on a single vendor's free edition.
  • Runs entirely inside the organisation's own cluster. No traffic, configuration or log leaves it for a supplier's service.
  • Installed and upgraded with the Bahriya Kubernetes Engine, or from the Bahriya Tersane catalogue on another conformant distribution.
  • Included with every BKE licence at no extra price, with ticketed support from within the GCC.

A sipar is a shield. The Persian word, carried into Ottoman Turkish as siper, named the round shield of the horseman, and later any cover that stands between a defender and an attack.

Why Mamluk builds Sipar

The layer every application depends on should not depend on one vendor's goodwill.

The gateway and the mesh carry every request, every credential check and every connection between services. Three considerations led Mamluk to build and support this layer itself.

The traffic layer carries the organisation's risk

Every request, every rate limit and every access decision passes through the gateway. An organisation that cannot influence that component, or obtain support for it on its own terms, carries a risk it does not control. Sipar gives that layer one supplier who is accountable for it, under the same licence as the cluster.

Open-core software is a supply risk

Several widely used gateways and meshes are open-core products, in which one company maintains a free edition and sells a paid one. That company can reduce or withdraw support for the free edition at its own discretion, and its users must then migrate under time pressure. Sipar depends only on projects governed by a foundation, with many contributing companies.

Regulators expect evidence

Supervisors of banks and critical infrastructure across the GCC expect traffic to be encrypted, workloads to be identified and activity to be logged in a form an auditor can read. Sipar provides each of these as configuration that can be inspected on the cluster, rather than as an assurance in a document.

Two parts, one licence

Sipar Gateway and Sipar Mesh.

Both parts are installed, upgraded and supported with the cluster. Each is enabled only when the organisation chooses.

Sipar Gateway

The entry point for the cluster. It routes HTTP, TCP and TLS traffic to applications using the Kubernetes Gateway API, and applies rate limits, a response cache, access control by address for TCP services, request identifiers and structured access logs. It runs as at least two replicas on separate nodes, so that maintenance on one node does not interrupt traffic.

Sipar Mesh

Security between services. Every workload receives a cryptographic identity, and traffic between services in an enrolled namespace is encrypted with mutual TLS. It works without a proxy beside each application, so applications need no change. Rules that depend on which service is calling are enforced in the mesh, and Sipar Gateway acts as its default entry point.

For the organisation

What changes for the business.

One accountable supplier

The cluster, its gateway and its mesh are built, tested together and supported by the same engineers, under one licence and one support contract.

No additional licence

Sipar is part of the Bahriya Kubernetes Engine licence. Adopting it adds no product to procure and no separate renewal to manage.

Open standards, not lock-in

Routes are written in the Kubernetes Gateway API, an open standard that other implementations also read, so an application's routing is described in a portable form.

Data stays in the organisation

Sipar runs inside the organisation's own cluster, in its own data centre or its own cloud accounts. No traffic, configuration or log is sent to Mamluk or to any other supplier.

Talk to the engineers who built it.