# Workflows, Workers - Restrict Workflows to a jurisdiction

Publisher-attributed story with a reviewed brief or permitted publisher paragraph. The original publisher is responsible for the linked reporting.

- Publisher: Cloudflare Developers
- Category: Cloud
- Original publication time: 2026-10-27T00:00:00Z
- First observed by NexusTechWire: 2026-10-27T17:50:39Z
- Original source: https://developers.cloudflare.com/changelog/post/2026-10-27-workflow-jurisdictions/
- NexusTechWire record: https://nexustechwire.com/news/news-2c3ad3cac7e3fe5ebca5

## From the publisher

You can now restrict a Workflow to a jurisdiction. Its instances only run and store data within that jurisdiction, which helps you comply with data localization regulations such as GDPR ↗︎ or FedRAMP ↗︎. Set jurisdiction on a workflows binding, or on a Workflow declared in exports: \{ "workflows": \[ \{ "name": "my-workflow", "binding": "MY\_WORKFLOW", "class\_name": "MyWorkflow", "jurisdiction": "eu", \}, \], \} \[\[workflows\]\] name = "my-workflow" binding = "MY\_WORKFLOW" class\_name = "MyWorkflow" jurisdiction = "eu" The supported jurisdictions are eu (the European Union), us (the United States), and fedramp (FedRAMP-Moderate data centers). A Workflow's jurisdiction is set when the Workflow is created, and cannot be changed afterwards. If an existing Workflow has a different jurisdiction, wrangler deploy and wrangler versions upload stop before uploading your Worker.

Source license: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Publisher excerpt shortened and converted to plain text. Original source license applies.

Read the full original: [Cloudflare Developers](https://developers.cloudflare.com/changelog/post/2026-10-27-workflow-jurisdictions/)

This record does not reproduce the complete article or represent independent confirmation of every source claim.
