For a lot of software, "where is it hosted" is an afterthought. For the teams running water networks, energy assets, ports and plants, it is often the first question on the procurement form — and the one that quietly disqualifies most vendors. Data-residency rules, sector regulation and plain institutional caution mean that "it's in our multi-tenant cloud, trust us" is a non-starter.
The honest response is not a louder security promise. It is to let the customer decide where the platform runs.
Three deployment models, one platform
Managed EU cloud
The default: hosted on EU infrastructure, fastest to start, nothing to run yourself, with EU-only data residency.
Your private cloud
The same platform deployed into your own cloud tenant on Kubernetes — under your accounts, your network policies, your controls.
Fully on-premises
For the strictest cases, the entire hub runs on your own hardware: a self-contained Kubernetes cluster, local high-availability PostgreSQL, and no dependency on any external key vault. Data never leaves the building.
Portability is the point
The model that actually works is one platform, portable across all three deployments, so moving on-prem costs you some operational overhead, not features. Sovereignty shouldn't cost you the product.