The EU team analyzes a copy that lives in the EU

The Frankfurt analysts need the warehouse. Legal says the warehouse stays in Frankfurt. The warehouse is currently in Virginia.

POST /api/v1/containers/{id}/copy with target_server_id pointing at your rented EU box. The container: SQLite files, the notebooks, the pinned environment: lands on German metal and starts on its own. From then on, a cron entry in Virginia POSTs /containers/{copy-id}/sync at 02:00 nightly. Sync is incremental; only the blocks that changed cross the Atlantic.

The Frankfurt team's queries, kernels, and exports all run on the Frankfurt server. Nothing they touch round-trips to Virginia, because the data they touch isn't in Virginia.

No cross-region replica to configure, no IAM boundary, no second managed-database bill. A copy and a nightly sync, both HTTP.

Data residency stops being a clause in the contract and becomes a server ID in a POST.