Every place the data comes to rest has to be inside the jurisdiction. Residency covers the agent's memory, the event journal behind it, and the interaction record kept for compliance. The replicas that hold those copies and the control plane that operates the installation are inside the boundary as well.
Akka runs sovereign deployments where traffic and data stay in-region, with data isolation, networking isolation, and local SREs. HA and DR run at full parity with every other Akka region.
An agentic system records the same fact in several places. Agent memory holds what the agent learned. The event journal holds the events that produced that memory. The interaction log holds what was asked, what the model returned, and which policy verdict applied. A replica in a second region holds each of those records again.
Each of those copies carries the residency obligation attached to the data in it. A deployment that keeps the primary in-country and replicates its backups to a cheaper region has moved the data out of the jurisdiction.
People reach the data as well. An SRE reading a log and a support engineer opening a trace both touch data that has a location and an operator.
Akka supports country-isolated deployment in China, Hong Kong, Singapore, the EU, the UK, Japan, Australia, Canada, and North America. Akka also runs on sovereign clouds including T-Systems and AllyCloud, so public, private, and country-isolated deployments come from one platform.
GDPR Chapter V governs transfers of personal data out of the EU. China's Generative AI Interim Measures apply to systems serving users in China. A system operating in several countries carries the residency rules of each.
Akka Verify derives which controls apply from what a system does, what data it touches, and where it runs, against a corpus of 190 AI regulations and 1,230 controls. Each residency row in that obligation set carries its citation, the runtime binding that enforces it, and the evidence event that proves the binding ran.
Active-active HA and DR run at full parity inside a sovereign configuration. Recovery takes under a minute and no committed write is lost, matching any other multi-region Akka deployment.
A sovereign configuration runs a private federation plane inside the boundary, so deployment and operational metadata stay in the same jurisdiction as the workload.
A hosted model provider serving from outside the region makes every inference call a cross-border transfer. Akka Optimize tunes specialized models from an open-weight base inside your own environment and serves them there, which keeps the call inside the boundary.
Local SREs staff a sovereign region, and the interaction record shows which identity read what. Support access is answerable to the same authority as the workload.
Where residency obligations come from and how the runtime enforces them.
What the second region has to hold before the first one fails.
How the obligation set looks in banking, insurance and capital markets.
