Apivom's application infrastructure runs entirely on Microsoft Azure. By default, that means the West Europe region — one of Azure's many regions, each contained within a single geography that serves as a fixed data residency boundary. Choosing a region means choosing which geography your data is stored in, and Microsoft's regional-service commitment is that data will not be stored outside that geography except for a small, documented set of non-regional or preview services.
Regions that support availability zones — physically separate groups of datacenters with independent power, cooling and networking, close enough for low-latency connections but far enough apart to avoid a shared local outage — give a region additional fault isolation beyond a single datacenter. That's the kind of infrastructure resilience Azure's regions are built to provide.
For customers who need full control over where their data lives — their own data residency policy, their own network boundary, their own compliance scope — Apivom can run in your own Azure tenant rather than ours. The application is the same; the Azure subscription, resource group and network boundary it runs inside are yours.
What this does not mean
Running on Azure is a platform choice, not a certification of our own application. The controls that matter for your data — who can access it, how it's encrypted, how it's backed up, how long we retain it — are decisions we make inside that platform, and we describe the relevant ones elsewhere on this page (the Azure Front Door WAF in front of the live platform) and in our security disclosure policy. A cloud provider's infrastructure guarantees do not, by themselves, describe how an application built on top of it behaves.