Data residency shouldn't mean trade-offs. We're rebuilding our control plane and logging on Workers and Durable Objects, so you can choose where WAF rules, Workers, and logs live with a click, and change it with another. Apply for the beta: https://lnkd.in/gmbZd3N3
Rebuilding the control plane and logging on Workers and Durable Objects turns data residency into an architecture decision instead of a product limitation. Will customers be able to place the control plane and their logs in different regions, or do they move together?
For Indian fintech teams this is a very practical problem. RBI rules already require payment data to stay in India, and the logs are where it usually slips: the app runs in Mumbai but the logs quietly get shipped to a US region. Making "where do my logs live" a setting you can see and audit, instead of a surprise found during an audit, is a big deal.
The drive for frictionless data residency is spot on; trade-offs often mean compliance gaps, especially with evolving AI regulations. For sensitive AI workloads, this level of control is critical, as truly eliminating egress risk often requires client-side RAM-only tokenization *before* data ever reaches an LLM, a core tenet Privacy Scrubber focuses on for cross-compliance as discussed at https://privacyscrubber.com/compliance/gdpr/ccpa-ai-cross-compliance/ #GDPR #ZTDS #AIPrivacy