Data residency

Data residency is a claim about geography: where data physically sits and where it is processed, not just who owns it. It usually exists to satisfy a specific legal requirement, a banking secrecy law, a data localization statute, a public sector rule that citizen data must stay within national borders, regardless of which region would otherwise be cheapest or fastest to run in.

For a regulated enterprise, data residency is often a precondition for using a system at all, not a preference. A vendor that only offers one fixed region cannot serve a customer whose law requires a different one.

A government agency required to keep resident records inside its own country's borders, no matter which cloud region a vendor's default deployment would otherwise use.

In Dynamiq, self-hosting the platform inside your own AWS, Azure, GCP, IBM Cloud, Red Hat OpenShift, or any Kubernetes 1.32+ cluster, or on-prem, keeps your data and the models you host inside the location you choose, and any outside service, such as a hosted model, is one you choose to use. Fully isolated or air-gapped environments, where even that is not enough, are delivered with Dynamiq's engineers.