SaaS Tenant Management › Data Residency & Region Placement
Data Residency & Region Placement
BC-4230.40
Level 2
Software & Technology
1 providers
1 API surfaces
1 rated strong or better
Assignment of tenants to regions, enforcement of data-residency commitments, and management of cross-region replication policy.
Data Residency & Region Placement (BC-4230.40) is a level-2 business capability under SaaS Tenant Management in the Software & Technology model. The catalog holds 1 API surface(s) from 1 provider(s) that can perform some part of it, 1 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.
Where this capability definition comes from.
This capability is part of a published business-architecture model that API Evangelist
did not author. It is redistributed here under
CC-BY-4.0.
Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented.
Source repository · NOTICE and third-party framework attributions
Sub-capabilities
Tenant Region Assignment BC-4230.40.10
Assignment of tenants to regions consistent with contract and regulation.
no catalog coverage
Data Residency Enforcement BC-4230.40.20
Enforcement of data-residency boundaries at runtime.
no catalog coverage
Cross-Region Replication Policy BC-4230.40.30
Policy governing cross-region replication for resilience and access.
no catalog coverage
Providers that reach this capability
Ordered by rating band. Reach means a provider publishes an API surface that can perform
some part of this capability — it is not a claim that any particular
organisation has deployed it.
Strong
1
Solid coverage with minor gaps
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature.
This page shows
which providers and tags reach Data Residency & Region Placement. The underlying
tag → capability edges — each with the quoted fragment of the provider's own
OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate
it passed — are available through the API, along with company-level capability maps.
Only edges at confidence ≥ 0.7 with evidence found verbatim in
the source contract are published at all.
See plans →
·
How the edges are graded →