Residency policy is pool membership

IT rents three boxes in Frankfurt and one in Amsterdam and puts all four in a pool named eu-prod. Developers get the User role: they can deploy containers to pool servers and see what's there. They cannot rent a server and they cannot add one to the pool.

That is the whole residency control. A developer who needs a new environment picks a server from the pool, and every server in the pool is on EU ground because IT put it there. No tag to forget, no policy engine scanning for containers that landed in the wrong place. The wrong place isn't in the list.

When a US footprint is needed, IT opens a second pool. Access to the pool is access to the geography.

Policy enforcement is usually a scanner that catches the mistake afterward. Here the mistake has nowhere to happen.

Here the mistake has nowhere to happen.