One release snapshot, two countries, no shared data

You ship the same product to EU and US customers, and the two fleets may never share a byte. They still have to run the same version.

Build the release once, in a template container that holds code and nothing else. Snapshot it. For each regional box, POST /api/v1/containers/{template}/copy with source_snapshot set to that release and target_server_id set to the box. Each region gets containers born from the identical image, on their own machine, on their own disks.

What crosses the border is the snapshot of a codebase with no customer in it. What never crosses is everything created afterward: databases, uploads, logs. The EU containers and the US containers share an ancestor and have no present-tense relationship at all.

Version parity without data parity. The snapshot is the only thing with a passport.