Where Planverity runs
The control plane and its database run in the EU. Provider calls go wherever your policy permits: allowed regions filter the candidate set before any ranking, so nothing downstream can reintroduce an endpoint outside them.
Residency is a hard constraint in the policy engine, not a scoring preference — a cheaper model in the wrong jurisdiction is not a candidate.
The control plane and its database run in the EU. Provider calls go wherever your policy permits: allowed regions filter the candidate set before any ranking, so nothing downstream can reintroduce an endpoint outside them.
A classification can require endpoints to carry specific tags — EU processing, no-training — with all listed tags mandatory. An endpoint missing one is infeasible rather than deprioritised. For data that must not leave your estate at all, a self-hosted endpoint speaking the same shape drops in with no code change.
Planverity enforces the residency metadata recorded in your registry. It does not independently audit where a provider actually processes data — that assurance comes from your contract with them. We hold no certification and make no certification claim.