Data residency and sovereign deployments
Choose where the data lives: a dedicated cluster in the region you pick, your own cloud account, or infrastructure you own.
45 minutes with an engineer: we review your workload and sketch the design.
- ✓Operated by AceMQ
- ✓Region you choose
- ✓Your keys and network
- ✓FIPS hosts
Data residency is about where data is stored. Sovereignty also covers who can operate and reach it. For a data sovereignty cloud, OSStend can place a cluster in a region you choose, inside your own cloud account, or on infrastructure you own, with your network, keys and audit trail staying yours.
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Valkey
- OpenSearch
- Kafka
- RabbitMQ
- AWS
- Google Cloud
- Azure
- Kubernetes
- OpenShift
- Prometheus
- Grafana
- Datadog
- Dynatrace
- Splunk
Residency, access and control are separate questions
A sovereignty requirement usually contains three questions: where the data is stored, who can reach it, and who controls the keys. Each deployment option answers them differently.
| Where it runs | Where the data lives | Who holds network, keys and audit trail |
|---|---|---|
| Dedicated in our cloud | Single-tenant clusters in the region you choose. | Set in the design. |
| In your cloud account | In your account and VPC. | You: private networking, your key management, your identity provider and your audit trail. |
| In your data center | On infrastructure you own, on Kubernetes, OpenShift, Windows or FIPS hosts. | You, in the co-managed tier. |
| Air-gapped site | On infrastructure you own, with no route to the internet. | You. See air-gapped. |
Source: OSStend deployment and security descriptions on deployment options and security.
The region of a dedicated cluster, or the account and region in bring your own cloud, is chosen with you and written into the design before anything is built.
Choosing between the options
Pick the option that keeps the data where your rules say it must be. If it has to stay in your own account, use bring your own cloud. If it has to stay on your premises, use the co-managed tier.
- A region, not a cloud account
- dedicated clusters in the region you choose. See deployment options.
- Your cloud account
- bring your own cloud keeps the data, billing and security boundary in your account.
- Your premises
- Kubernetes and OpenShift put the data services on your cluster.
Compliance programmes and attestations
Regimes such as FedRAMP or EU sovereignty frameworks apply to a whole system and its operator. They are decided case by case, and what OSStend holds is stated here only once it is confirmed.
No FedRAMP, SOC 2, ISO or sovereignty-programme status is claimed on this page. For RabbitMQ, AceMQ's FIPSMQ broker uses FIPS 140-2 and 140-3 validated cryptographic modules. For other engines, the FIPS position of each host and engine is settled in the design.
OSStend is operated by AceMQ; see about for the company behind it. This page is not legal advice, and a residency requirement should be checked with your own counsel.
When it fits and when it does not
OSStend suits enterprises with a residency or control requirement that a standard plan cannot meet.
Contact us if
- ✓Policy or contract fixes the region, the account or the premises where data must stay.
- ✓You need to keep your own keys, identity provider and audit trail.
- ✓FIPS-capable hosts are part of the requirement.
Not a fit if
- ✕Your workload fits a standard plan in a single region, where a turnkey service costs less.
- ✕You want a free tier or a card sign-up.
FAQ
What is the difference between data residency and data sovereignty?
Data residency is where data is physically stored. Data sovereignty adds who can access and control it, including who holds the keys and which legal jurisdiction applies.
Can the database run in my own cloud account for residency reasons?
Yes. In the in-your-account option the cluster runs in the customer's account and VPC, so the data stays there, with the customer's keys, identity provider and audit trail.
Can the service run on premises?
Yes, in the co-managed tier, on Kubernetes, OpenShift, Windows or FIPS hosts, including air-gapped sites.
Related pages
- Deployment · Air-gappedAir-gapped cloud and on-prem managed open sourceAir-gapped cloud and on-prem sites: OSStend co-manages PostgreSQL, Kafka and RabbitMQ on infrastructure you own, with hardened FIPS editions on request.
- DeploymentManaged databases: our cloud, yours or on-premManaged databases in OSStend's cloud, your AWS, Azure or Google Cloud account, or your data center. PostgreSQL, Kafka and RabbitMQ, run 24/7 by engineers.
- 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 · Your cloud accountBring your own cloud (BYOC) managed databasesBring your own cloud with OSStend: engineers run PostgreSQL, Kafka and more inside your AWS, Azure or Google Cloud account, so data and billing stay yours.
- Deployment · Your data centerPostgreSQL on Kubernetes, managed by OSStendRun PostgreSQL on Kubernetes and Kafka on your own cluster, co-managed by OSStend through an operator with supported charts and images, 24/7.
- Deployment · OpenShiftKafka on OpenShift and PostgreSQL, run 24/7Kafka on OpenShift and PostgreSQL on OpenShift, co-managed by OSStend through an operator on your cluster, with supported charts and images, 24/7.
Talk to an engineer about residency
Bring the rules that fix where your data must live. 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