FEATURES / Data Residency
/// Data Residency
Pin your data to a jurisdiction. It stays there.
Create Cloudflare R2 fleets locked to the EU or FedRAMP jurisdiction so data physically stays in-region. Storafleet auto-detects the jurisdiction, sends the cf-r2-jurisdiction header, and keeps R2's fast paths working on jurisdiction-locked buckets.
Start for free/// How it works
Pick a jurisdiction when you create the fleet
Creating a Cloudflare R2 fleet? Choose EU, FedRAMP, or default. R2 provisions the bucket against the jurisdiction-specific endpoint — and that choice is immutable once the bucket exists, so pick it deliberately.
Storafleet detects and reconciles it
Storafleet reads the endpoint, derives the jurisdiction, and pins it to the fleet. Every connection from then on targets that region's R2 endpoint — nothing to configure by hand.
Every request stays in-region
Storafleet sends the cf-r2-jurisdiction header on jurisdiction-aware calls so reads, writes, Super Slurper imports, and Sippy migrations all resolve inside the chosen jurisdiction.
Jurisdiction pinned at creation
When you create an R2 fleet in Storafleet, choose a jurisdiction — EU, FedRAMP, or default. The bucket is provisioned against R2's jurisdiction-specific endpoint so its data is locked to that region from day one.
EU data residency for GDPR
Pin a fleet to the EU jurisdiction and R2 keeps the data physically inside the European Union. This helps you meet GDPR data-residency obligations and contractual EU-only storage clauses.
FedRAMP residency for public sector
Pin a fleet to the FedRAMP jurisdiction for US public-sector and regulated workloads that require data to stay within FedRAMP boundaries. Storafleet routes every request to the matching endpoint.
Automatic jurisdiction detection
Storafleet reads the R2 endpoint — for example <account>.eu.r2.cloudflarestorage.com — detects the jurisdiction, and reconciles it onto the fleet. You don't hand-maintain a separate residency flag that can drift from reality.
cf-r2-jurisdiction sent for you
EU and FedRAMP buckets require the cf-r2-jurisdiction header on jurisdiction-aware operations. Storafleet attaches it automatically, so requests resolve against the correct region instead of failing or hitting the wrong endpoint.
Fast paths keep working in-region
R2's bulk and migration tooling — Super Slurper for bulk import and Sippy for live migration — needs the jurisdiction set correctly. Storafleet wires it through so these fast paths run against EU and FedRAMP buckets the same as default ones.
/// Without Storafleet
R2 jurisdictions live behind region-specific endpoints and a header most tools never send. Get it wrong and requests fail, fast paths break, or — worse — data lands outside the region you promised.
- You have to hand-pick the jurisdiction endpoint like <account>.eu.r2.cloudflarestorage.com per request
- The cf-r2-jurisdiction header is easy to forget — and EU/FedRAMP operations need it
- Super Slurper bulk import and Sippy live migration silently misbehave when the jurisdiction isn't set
- Nothing tells you which jurisdiction a bucket is actually in — and it can't be changed after creation
- A misconfigured endpoint can route data outside the region your compliance terms require
/// With Storafleet
Choose EU or FedRAMP when you create the fleet. Storafleet detects the jurisdiction, sends the right header, and keeps every request and migration inside that region.
- Pick EU, FedRAMP, or default once at fleet creation — Storafleet uses the matching R2 endpoint
- cf-r2-jurisdiction is attached automatically on every jurisdiction-aware request
- Super Slurper and Sippy run correctly against EU and FedRAMP buckets with no extra setup
- Storafleet auto-detects the jurisdiction from the endpoint and reconciles it onto the fleet
- Data physically stays in the chosen jurisdiction, helping you meet GDPR and FedRAMP residency requirements
/// When you'll use this
Keeping customer data inside the European Union
Your contracts say customer data never leaves the EU. You create an R2 fleet in Storafleet and pin it to the EU jurisdiction at creation. R2 stores the data on EU infrastructure, Storafleet routes every request to the EU endpoint, and you have a clean answer for your GDPR data-residency commitments.
Key featureEU jurisdiction pinning with in-region routing
Standing up a FedRAMP-residency workload
A US agency workload requires data to stay within FedRAMP boundaries. You create the fleet with the FedRAMP jurisdiction. Storafleet detects it from the endpoint, sends cf-r2-jurisdiction on every jurisdiction-aware request, and your bulk import via Super Slurper runs against the FedRAMP bucket without manual endpoint wrangling.
Key featureFedRAMP jurisdiction with working Super Slurper import
Honoring a contractual data-locality clause
A customer's contract has a strict data-locality clause. You pin their R2 fleet to the required jurisdiction at creation — it's immutable after that, so there's no risk of someone silently moving the data later. Storafleet reconciles the jurisdiction onto the fleet so your dashboard reflects exactly where the data lives.
Key featureImmutable jurisdiction with auto-reconciled residency
Your storage estate deserves a control plane.
Join the DevOps teams and founders who run every cloud's buckets from one control plane.
Free plan · No credit card · 50+ cloud providers · Cancel any time