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.
- 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.
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.
In your cloud account
OSStend operates inside your account and VPC, in AWS, Azure or Google Cloud. Your data, your billing, your security boundary.
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 cloud | In your cloud account | In your data center | |
|---|---|---|---|
| Service tier | Fully managed | Fully managed | Co-managed |
| Who owns the infrastructure | OSStend | You, in your account | You |
| Network and access controls | Set in the design | Yours | Yours |
| Platforms | Google Cloud, AWS | AWS, Azure, Google Cloud | Kubernetes, OpenShift, Windows and FIPS hosts, air-gapped sites |
| Kind of SLA | Uptime SLA | Uptime SLA | Response-time SLA |
| Best when | You want the whole service run for you | Data and billing must stay in your cloud account | The 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.
- Managed PostgreSQL: any size and replica layout, with the extensions you need.
- Managed Kafka: broker count and partition plan for your estate, in your own cloud account if you want it.
- RabbitMQ hosting: federation and shovel to your data center, with Windows and FIPS hosts.
- Managed Redis or Valkey, managed MySQL, managed MongoDB and managed OpenSearch.
- Managed Debezium: change data capture from your databases, run 24/7, and managed Cassandra: Apache Cassandra in our cloud, yours or your data center.
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.
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.
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.
Not a fit if
- ✕Your workload fits a standard plan in a single cloud.
- ✕You want a free tier or a card sign-up.
Related pages
- Service levelsService levels: two tiers, a written SLAOSStend service levels: fully managed and co-managed tiers, what each one covers, who is on call and how incidents are handled, with a written SLA for each.
- PostgreSQLManaged PostgreSQL service and Postgres hostingManaged PostgreSQL service, compared: how to choose between RDS, Aiven, Crunchy Bridge, Neon and a tailored cluster run 24/7 in your cloud or ours.
- KafkaManaged Kafka in your cloud or data centerManaged Kafka with the broker count, partition plan, KRaft, Connect and schema registry designed for your estate, run 24/7 in your cloud or your data center.
- RabbitMQRabbitMQ hosting in your cloud or on premiseRabbitMQ hosting for clusters a plan cannot hold: federation and shovel, the plugins you need and upgrades on your change calendar, run 24/7 by engineers.
- Redis or ValkeyManaged Redis or Valkey, your choice of engineManaged Redis or Valkey: you choose the engine, with persistence, eviction and configuration set for your workload, run 24/7 in your cloud or data center.
- MySQL and MariaDBMySQL hosting: managed MySQL and MariaDB, 24/7MySQL hosting for enterprise workloads: managed MySQL and MariaDB with replicas, point-in-time recovery and failover, run 24/7 in your cloud or data center.
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