Deployment

Run it where your data has to live: our cloud, your cloud or your data center

Three places to run it: dedicated in OSStend's cloud, inside your own cloud account, or in your data center on Kubernetes, OpenShift or air-gapped hosts.

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

  • Operated by AceMQ
  • Our cloud, yours or on-prem
  • Air-gapped and FIPS

Managed database deployment with OSStend happens in three places: dedicated clusters in its own cloud, inside your AWS, Azure or Google Cloud account (bring your own cloud), or co-managed in your data center, Kubernetes, OpenShift or air-gapped site. The first two are fully managed. The third is co-managed.

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

Three ways to deploy

Pick the option that matches where the data has to live. The engines, the engineers and the design process are the same in all three.

Fully managed

Dedicated in our cloud

Single-tenant clusters in the region you choose, on Google Cloud or AWS. Multi-zone by default, with cross-zone traffic planned up front.

Fully managed

In your cloud account

OSStend operates inside your account and VPC, in AWS, Azure or Google Cloud. Your data, your billing, your security boundary.

Co-managed

In your data center

Cloud repatriation, on-prem and air-gapped sites, on Kubernetes, OpenShift, Windows or FIPS hosts. Delivered through an operator on your cluster, with supported charts and images.

AceMQ's RabbitMQ support already covers customer systems on AWS, Azure and Google Cloud, on Kubernetes including EKS, AKS, GKE and OpenShift, on bare metal and at air-gapped sites (acemq.com/support, checked 31 Oct 2026). For OSStend, the cloud, account and region a cluster uses are fixed in the design you sign off.

How the three options compare

The main differences are who owns the infrastructure and the network, and which kind of SLA follows. The table sets the three side by side.

Dedicated in our cloudIn your cloud accountIn your data center
Service tierFully managedFully managedCo-managed
Who owns the infrastructureOSStendYou, in your accountYou
Network and access controlsSet in the designYoursYours
PlatformsGoogle Cloud, AWSAWS, Azure, Google CloudKubernetes, OpenShift, Windows and FIPS hosts, air-gapped sites
Kind of SLAUptime SLAUptime SLAResponse-time SLA
Best whenYou want the whole service run for youData and billing must stay in your cloud accountThe workload must stay on-prem, is leaving the cloud, or is air-gapped

Each tier's figures are set per plan and written into the contract. How the tiers differ is on service levels.

Engines on every option

Each engine page says what is tailored and where it runs for that engine. Start from the engine you run today.

The security controls that apply to each option are on security, and residency and sovereignty requirements are covered on data residency and sovereign deployments. See all engines on managed database services, and the workloads OSStend suits on customers.

Enterprise only

Proof from AceMQ

OSStend is operated by AceMQ, which has run these systems for enterprises on-prem, in their own clouds and in air-gapped sites.

Operated by AceMQCompany figures, as published on acemq.com
160+AceMQ customers
10+Years running these systems
24/7Engineers on call

Contact us if

  • Your data has to stay in your cloud account, your data center or an air-gapped site.
  • You run across more than one cloud and want one partner.
  • You need FIPS or Windows hosts.
Talk to an engineer

Not a fit if

  • Your workload fits a standard plan in a single cloud.
  • You want a free tier or a card sign-up.
Talk to an engineer

Talk to an engineer, not a ticket queue

45 minutes with someone who runs these systems. We map your databases and brokers, the zero-downtime cutover path and which tier fits.

  • 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.