What it does
A per-project policy of allowed regions for six data paths, a decision route that denies an out-of-region placement, a drift check against observations you supply, and a readiness view that states which paths the feature can and cannot enforce.
How it works
PUT /v1/residency/policy declares allowed regions for each dimension: storage, compute, backup, inference, logs and metadata. POST /v1/residency/placement takes a dimension, a resource id, a region and optionally a provider, and returns allowed or denied with a reason code and a decision digest. A dimension with no declared boundary is denied. A denial is written to the audit log with the dimension, region and reason code, never record contents.
Each dimension has a fixed enforcement level that a policy cannot raise. Storage, compute and backup are enforceable at the admission decision. Inference is advisory, because the live model-routing path is not wired to it. Logs and metadata are not enforced, so placements for them are denied and no claim is made. POST /v1/residency/drift compares observations you supply with the policy and lists data found outside its boundary. GET /v1/residency/readiness reports each dimension as unknown, advisory or unenforced, and does not report one as compliant when it cannot know.
Where you reach it
- HTTP
GET|PUT /v1/residency/policy - HTTP
POST /v1/residency/placement - HTTP
POST /v1/residency/drift - HTTP
GET /v1/residency/readiness
Example
# Use the project's service key: residency is per project
curl -s -X PUT "$KYNETRA_URL/v1/residency/policy" \
-H "Authorization: Bearer $SERVICE_KEY" \
-H "Content-Type: application/json" \
-d '{"storage":{"allowed_regions":["in"]},"backup":{"allowed_regions":["in"]}}'
curl -s -X POST "$KYNETRA_URL/v1/residency/placement" \
-H "Authorization: Bearer $SERVICE_KEY" \
-H "Content-Type: application/json" \
-d '{"dimension":"backup","resource_id":"nightly-backup","region":"eu"}'
# {"decision": {"outcome": "denied", "reason": "region_out_of_boundary", ...}}Limits
- The feature answers questions and does not intercept the engine. Storage, backup and deployment code does not consult it, so placement is enforced where a caller, such as your deployment tooling, asks and honours the answer.
- Drift detection works on observations you submit. The server does not discover where data lives.
- The readiness route evaluates the policy without observations, so declared dimensions report unknown until evidence is supplied elsewhere.
- Through the mounted server, tests exercise the policy route inside the forged-policy tests and nowhere else. The placement, drift and readiness routes have no mounted tests of their own, which is why this capability is beta. The decision logic is tested.
- This is not a legal or regulatory certification.
Evidence
- On this siteSecurity overview
- Tests14 residency-domain tests in the compliance crate (allow and deny by region, fail closed without a boundary, unenforced dimensions denied, drift, per-project scoping, persistence across reopen) and 2 tests that refuse forged residency policies through the generic write routes
Test coverage is listed as present in the engine repository at this edition. This page does not report test results.
KynetraDB is in private preview
Request a preview to talk through the limits above against your own workload.