Deployment · Your data center

Managed PostgreSQL and Kafka on your Kubernetes or OpenShift

OSStend co-manages PostgreSQL, Kafka and other engines on the Kubernetes or OpenShift cluster you own, through an operator with supported charts and images.

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

  • Operated by AceMQ
  • Co-managed
  • Kubernetes and OpenShift
  • Operator, charts and images

PostgreSQL on Kubernetes, with Kafka and other engines, is a co-managed OSStend service on your Kubernetes or OpenShift cluster. It is delivered through an operator on your cluster, with supported charts and images. You keep the infrastructure, the network and the access controls.

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

What co-managed means on your cluster

Co-managed is the tier for clusters you own. The infrastructure and the network stay yours, and OSStend engineers design, move and run the data services on top, under a response-time SLA.

Dedicated or your cloud account
Service tierCo-managedFully managed
Who owns the infrastructureYouOSStend, or you in your account
Network and access controlsYoursSet in the design, or yours
Kind of SLAResponse-time SLAUptime SLA
How it is deliveredAn operator on your cluster, with supported charts and imagesOSStend runs the cluster

Terms for each tier are on service levels. The three options side by side are on deployment options.

Operators, charts and images

On Kubernetes a database or broker is usually run by an operator: a controller that watches a custom resource and keeps the cluster in the state it describes. OSStend delivers its service through an operator on your cluster, with supported charts and images.

The pattern is documented by Kubernetes as the operator pattern, and stateful engines run as StatefulSets with persistent volumes. Community operators exist for the main engines, for example CloudNativePG for PostgreSQL, Strimzi for Kafka and the RabbitMQ Cluster Operator. They show what an operator manages. For PostgreSQL, OSStend runs CloudNativePG; see managed CloudNativePG (project links checked 30 Oct 2026).

The Kubernetes version and distribution, the operator and chart version for each engine, and the images it runs are named in the design you sign off, so the supported set is the one written down for your cluster.

What the design step settles

Running a stateful engine on Kubernetes comes down to a few platform choices. They are set in the cluster design you sign off, before anything is built.

QuestionWhy it matters
StorageDatabases and brokers need volumes that outlive a pod and perform predictably.Persistent volumes
Spread across zones and nodesReplicas on one node or one zone fail together.Topology spread constraints
Planned disruptionNode upgrades drain pods, and a quorum-based engine must not lose too many at once.Pod disruption budgets
Network isolationWhich workloads and operators may reach the data services.Network policies
Upgrade calendarOperator, engine and node upgrades follow your change windows, not a fixed schedule.Set in the design; see how it works

Kubernetes documentation links checked 30 Oct 2026.

Engines on your cluster

PostgreSQL and Kafka are the usual starting points, and the other engines follow the same delivery model.

Enterprise only

When it fits and when it does not

Co-managed on Kubernetes fits teams that have a platform they trust and want the data services run by engineers who do it all day.

Contact us if

  • You run Kubernetes or OpenShift in your data center and want to keep it there, for example under a residency or sovereignty rule.
  • Cloud repatriation is on the roadmap and the data services have to move with it.
  • Your platform team owns the cluster but does not want to be on call for databases and brokers.
Talk to an engineer

Not a fit if

  • You want the whole stack, including the infrastructure, run for you. See bring your own cloud or the fully managed tiers.
  • 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 PostgreSQL run on Kubernetes in production?

Yes, with an operator that manages replicas, failover and backups, and with storage, zone spread and upgrade windows planned up front. OSStend delivers PostgreSQL on a customer's Kubernetes through the CloudNativePG operator, with supported charts and images. See managed CloudNativePG.

Who is on call when the cluster is mine?

In the co-managed tier OSStend engineers run the data services 24/7 under a response-time SLA. The customer's team stays responsible for the underlying infrastructure and network.

Does it work on OpenShift?

Yes. OpenShift is a supported platform for the co-managed tier. The OpenShift-specific points are on the OpenShift page.

Talk to an engineer

Talk to an engineer about your cluster

Bring the platform you run and the engines you want on it. 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.