Residency is more than a map
A marketing map can show where infrastructure might exist, but it does not explain what happens when an organisation’s content has a strict placement rule. The operational question is whether the product has an organisation-level property that influences where governed data is written.
Casewelt’s regional-control model starts there: a home region belongs to the organisation context rather than being inferred from the user’s current location.
Conflicts should be visible
If a write requests placement that conflicts with the organisation rule, silently choosing another region makes the policy hard to reason about. A visible conflict is easier to operate: automation can stop, surface the reason and require an authorised migration or configuration change.
That same principle should apply to supporting context such as key wrapping and authoritative audit, according to the actual deployment design.
Migration is a deliberate event
Moving an organisation between regions can affect storage, keys, availability, contracts and operational sequencing. Treating it as a migration programme is more credible than describing it as an invisible routing change.
The exact regions and migration options should therefore be confirmed for the environment being evaluated, not assumed from a generic public page.
Inspect a conflict
The important test is a conflict. Ask the product to place data somewhere policy does not permit and inspect whether the write stops clearly and leaves useful evidence.