Cloudflare Containers can now pin where they run, in the EU or North America!

Hey everyone, it's Shiichan! Today I've got a small-but-important update: you can now choose where your servers actually live.

Cloudflare Changelog developers.cloudflare.com

What was announced?

Over on the Cloudflare Changelog, they announced that Containers now support placement constraints. That means you get to decide where in the world your containers run.

There are two kinds you can set: regions for geographic placement, and jurisdiction to pin things to compliance boundaries.

The story so far

Until now, Containers ran automatically close to the incoming request. That's great for speed, but if you have a rule like "this data must never leave the EU," not being able to control where things run was a bit of a headache.

What changes

Now you can say things like "keep this container inside the EU" or "limit it to North American regions." For teams that care about data residency or regulatory compliance, this is a long-awaited feature.

Dive Deep

Here's what you can pick:

• regions: choose from ENAM (eastern North America), WNAM (western North America), EEUR (eastern Europe), and WEUR (western Europe) to narrow the geographic area.
• jurisdiction: set eu or fedramp to bind to a compliance boundary. eu maps to the European regions (EEUR, WEUR), and fedramp maps to the North American regions (ENAM, WNAM).

So with jurisdiction, you don't have to memorize every region name — you can group them as "the EU" or "FedRAMP" and set them all at once. For the setup details, check the Containers placement docs.

Wrap-up

• Cloudflare Containers can now constrain where your containers run
• regions lets you pick geographic regions (ENAM / WNAM / EEUR / WEUR)
• jurisdiction offers eu and fedramp, each mapping to a compliance boundary
• It's an update that really lands for teams with data residency or regulatory requirements