Managed databases in your own AWS, Azure or Google Cloud account
OSStend engineers design, move and run your databases and messaging inside your own AWS, Azure or Google Cloud account and VPC.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ
- ✓Your account and VPC
- ✓Fully managed
- ✓One partner across clouds
Bring your own cloud means the cluster runs in your cloud account instead of the vendor's. OSStend operates it inside your account and VPC, in AWS, Azure or Google Cloud, fully managed. Your data, your billing and your security boundary stay yours.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
What bring your own cloud means
In a bring-your-own-cloud deployment the infrastructure belongs to you and the operations belong to OSStend. The cluster runs in your account and VPC, and OSStend engineers run it 24/7 as a fully managed service.
| Area | Who holds it | What that means |
|---|---|---|
| Cloud account and infrastructure | You | The cluster runs in your account and VPC, so your data stays in it. |
| Network | You | Private networking in your account. |
| Keys | You | Encryption keys stay in your own key management. |
| Identity | You | Access is tied to your own identity provider. |
| Audit trail | You | Activity is written to your own audit trail. |
| Day-to-day operation | OSStend | Upgrades, backups, scaling and incident response by named engineers, 24/7. |
The controls in the first five rows are described on security. Residency and sovereignty questions are covered on data residency and sovereign deployments.
The infrastructure stays on your own cloud bill. OSStend's fee is quoted separately, per design, and how it is invoiced is set out in the written quote.
AWS, Azure and Google Cloud
The same service can run in AWS, Azure or Google Cloud, on one contract. That matters for estates that span clouds, because the cloud providers' own managed services are tied to their own cloud.
Amazon MQ and Amazon MSK, for example, are AWS services (Amazon MQ docs, Amazon MSK docs, checked 30 Oct 2026). A team with workloads in AWS and another cloud ends up with a different service, and a different set of limits, in each. Running one design in each account gives one set of settings and one on-call team across all of them.
| Cloud | Position in the rollout | Notes |
|---|---|---|
| AWS | First | Dedicated clusters in OSStend's cloud also run here. |
| Azure | After AWS | In your account and VPC. |
| Google Cloud | After AWS | In your account and VPC. Dedicated clusters in OSStend's cloud also run here. |
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). The account and region your cluster uses are fixed in the design you sign off.
How the move into your account works
The three steps are the same as on every OSStend engagement: design, move, run. Two parts of the design are specific to your own cloud: how the account is laid out, and how OSStend engineers reach it.
Design
An engineer reviews the workload and writes the cluster design: size, topology, configs and versions, plus the account, network, key and identity setup it needs. You sign it off before anything is built.
Move
OSStend runs the migration and owns the cutover, with both sides live until you switch. The method depends on the engine: replication for databases, mirroring for Kafka.
Run
Named engineers run it 24/7 with upgrades on your calendar. Metrics and alerts go to your own Datadog, Dynatrace, Splunk or Prometheus.
The full offer is described on how it works, and the uptime terms that go with a fully managed cluster are on service levels.
Engines you can run in your own account
Every engine OSStend runs can be deployed in your account. Kafka and PostgreSQL are the most common starting points.
- Managed Kafka: broker count and partition plan designed for your estate, with Connect and a schema registry.
- Managed PostgreSQL: any size and replica layout, with the extensions you need.
- The other engines are listed on managed database services. The three places a cluster can run are compared on deployment options.
When it fits and when it does not
Bring your own cloud suits teams whose data, billing or security review keeps the cluster inside their own account. It adds little for teams that are happy with a vendor-hosted cluster.
Contact us if
- ✓Your data has to stay in your cloud account and VPC.
- ✓You run in more than one cloud and want one partner and one contract.
- ✓Your security team wants your own keys, identity provider and audit trail.
Not a fit if
- ✕Your workload fits a standard plan in a single cloud, where a turnkey service costs less.
- ✕You want a free tier or a card sign-up.
- ✕The workload must run in your data center or an air-gapped site. See Kubernetes and air-gapped.
FAQ
What is bring your own cloud for managed databases?
Bring your own cloud is a deployment model where the managed service runs in the customer's cloud account instead of the provider's. The provider operates it, and the customer keeps the data, the billing and the security boundary.
Who operates the cluster when it runs in my account?
OSStend engineers operate it 24/7 as a fully managed service. The infrastructure, network, keys and identity provider remain the customer's.
Can one contract cover databases in more than one cloud?
Yes. The same service can run in AWS, Azure and Google Cloud on one contract, with one on-call team across every engine. Availability by cloud and region at launch is confirmed on the engagement.
Related pages
- SecuritySecurity and compliance at OSStendOSStend security: private networking, your identity provider, your key management and audit trail, plus air-gapped delivery and FIPS hosts you control.
- Deployment · Data residencyData sovereignty cloud and residency optionsData sovereignty cloud options: OSStend runs PostgreSQL, Kafka and more in the region you pick, in your own cloud account or in your data center.
- How it worksHow OSStend works: design, move, runOSStend designs your cluster around the workload, moves it in with zero downtime and runs it 24/7. See the three steps and what turnkey services leave out.
- 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.
- 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.
- 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.
Talk to an engineer about your own cloud
Bring the cloud accounts and engines you run. 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