Deployment · OpenShift

Managed Kafka and PostgreSQL on OpenShift

OSStend co-manages Kafka and PostgreSQL on the OpenShift cluster you own, in your data center.

45 minutes with an engineer: we review your workload and sketch the design.

  • Operated by AceMQ
  • Co-managed
  • OpenShift
  • Kafka and PostgreSQL

Kafka on OpenShift, with PostgreSQL and other engines, is a co-managed OSStend service delivered through an operator on your cluster, with supported charts and images. You keep the platform, the network and the access controls, and OSStend engineers run the data services 24/7.

160+AceMQ customers
10+Years running these systems
24/7Engineers on call
3Places it runs: our cloud, yours, your data center
Engines we run, on the platforms you already use
  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis
  • Valkey
  • OpenSearch
  • Kafka
  • RabbitMQ
  • AWS
  • Google Cloud
  • Azure
  • Kubernetes
  • OpenShift
  • Prometheus
  • Grafana
  • Datadog
  • Dynatrace
  • Splunk

Data services on the OpenShift you already run

OpenShift is Kubernetes with extra controls, and the co-managed model is the same as on any Kubernetes cluster. The cluster stays yours, and OSStend designs, moves and runs the data services on it.

The delivery model, the service tier and the SLA type are described on the Kubernetes page. This page covers what is specific to OpenShift.

AceMQ engineers already support customer systems on OpenShift (acemq.com/support, checked 31 Oct 2026). The OpenShift version, the operator and chart version for each engine, and the images are named in the design you sign off.

What is specific to OpenShift

OpenShift applies stricter defaults than plain Kubernetes. The points below are the ones the design step checks first for a database or broker.

TopicDocumentation
Security context constraintsOpenShift controls what a pod may run as and which volume types it may use through security context constraints. An image or chart written for plain Kubernetes may need to fit those rules.OpenShift security context constraints
Rack and zone awarenessKafka can place replicas by rack, which maps to zones on a multi-zone cluster. Replica placement is part of the broker and partition plan.Kafka broker.rack
StorageBoth engines depend on persistent volumes that perform predictably.Persistent volumes
Disconnected clustersSome OpenShift clusters have no internet route. The delivery then follows the air-gapped model.See air-gapped

Documentation links checked 30 Oct 2026.

Kafka and PostgreSQL on OpenShift

Kafka and PostgreSQL are the engines most teams put on OpenShift first. Each page covers the sizing and the tailoring for that engine.

Enterprise only

When it fits and when it does not

This option suits teams that have standardised on OpenShift and want the data services run by specialists.

Contact us if

  • OpenShift is your platform standard, in your data center, and a residency rule keeps the data there. See data residency and sovereign deployments.
  • You want Kafka or PostgreSQL on it without adding an on-call burden for your platform team.
Talk to an engineer

Not a fit if

  • You do not run OpenShift and want the cluster hosted for you. See bring your own cloud.
  • Your workload fits a standard plan, where a turnkey service costs less.
Operated by AceMQCompany figures, as published on acemq.com
160+AceMQ customers
10+Years running these systems
24/7Engineers on call

Can Kafka run on OpenShift?

Yes. Kafka runs on OpenShift with persistent volumes, rack-aware replica placement and a broker and partition plan sized to the workload. OSStend runs it there as a co-managed service.

Is the service fully managed on OpenShift?

No. On a customer-owned OpenShift cluster the service is co-managed: the customer keeps the platform, and OSStend runs the data services under a response-time SLA.

Does OpenShift change how PostgreSQL is delivered?

The delivery is the same operator, charts and images as on Kubernetes, and the PostgreSQL operator is CloudNativePG (details). OpenShift adds security context constraints, which the design step checks before anything is built.

Talk to an engineer

Talk to an engineer about OpenShift

Bring your OpenShift version, the engines you want and where it runs. An engineer will review them with you and sketch the design in 45 minutes.

  • A design sketch for your workload, not a plan menu
  • A zero-downtime cutover path for what you run today
  • A price for that design, after the review
See pricing →

Your request goes to the OSStend team. No newsletter sign-up.

Get a quoteTalk to an engineer
2Engines
3Where should it run?
4What do you need?

Your request goes to the OSStend team. No newsletter sign-up.