# Workflows, Workers - Restrict Workflows to a jurisdiction

Category: agent-infrastructure
Published: 2026-10-27T00:00:00.000Z
Source: [Cloudflare Workflows changelog](https://developers.cloudflare.com/changelog/post/2026-10-27-workflow-jurisdictions/)
Agent usefulness: 80/100
Confidence: 0.9
Content mode: source-watch
Verified: 2026-10-27T18:17:59.952Z
Tags: cloudflare, workflows, changelog

## Human Summary
Cloudflare Workflows changelog published Workflows, Workers - Restrict Workflows to a jurisdiction. 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…

## Agent Summary
Treat Workflows, Workers - Restrict Workflows to a jurisdiction as an official publication signal. Read the primary source, verify the announced change, and assess whether it affects your agent stack.

## Body
Cloudflare Workflows changelog published Workflows, Workers - Restrict Workflows to a jurisdiction. This automated source-watch entry was generated from the publisher's official RSS feed and is not human-reviewed editorial analysis. Source excerpt: 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 af

## Recommended actions
- Read the original Cloudflare Workflows changelog article before relying on this summary.
- Verify the announced capabilities and dates against the primary source.
- Assess whether the change affects your agent stack or evaluation plan.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, commercial disclosure fields, sourceOfTruthUrl, constraintsLastVerifiedAt, constraintsRefreshCadence, driftHandlingPolicy, and constraintPolicy.