---
title: Cloudflare product compatibility · Data Localization Suite docs
description: The table below provides a summary of the Data Localization Suite product's behavior with Cloudflare products. Refer to the table legend for guidance on interpreting the table.
lastUpdated: 2025-04-14T15:57:09.000Z
source_url:
  html: https://29ff08e0.preview.developers.cloudflare.com/data-localization/compatibility/index.md
  md: https://29ff08e0.preview.developers.cloudflare.com/data-localization/compatibility/
---

The table below provides a summary of the Data Localization Suite product's behavior with Cloudflare products. Refer to the table legend for guidance on interpreting the table.

✅ Product works with no caveats\
🚧 Product can be used with some caveats\
✘ Product cannot be used\
⚫️ Not applicable

## Application Performance

| Product | Geo Key Manager | Regional Services | Customer Metadata Boundary |
| - | - | - | - |
| Caching/CDN | ✅ | ✅ | ✅ |
| Cache Reserve | ⚫️ | 🚧 | ✅ [1](#user-content-fn-29) |
| DNS | ⚫️ | 🚧 [2](#user-content-fn-33) | 🚧 [3](#user-content-fn-32) |
| HTTP/3 (with QUIC) | ⚫️ | ✘ | ⚫️ |
| Image Resizing | ✅ | ✅ [4](#user-content-fn-6) | 🚧 [5](#user-content-fn-1) |
| Load Balancing | ✅ | ✅ | 🚧 [5](#user-content-fn-1) |
| Onion Routing | ✘ | ✘ | ✘ |
| Orange-to-Orange (O2O) | ✘ | ✘ | ✘ |
| Stream Delivery | ✅ | ✅ | ✅ |
| Tiered Caching | ✅ | 🚧 [6](#user-content-fn-2) | 🚧 [7](#user-content-fn-30) |
| Trace | ✘ | ✘ | ✘ |
| Waiting Room | ⚫️ | ✅ | ✅ |
| Web Analytics / Real User Monitoring (RUM) | ⚫️ | ⚫️ | ✘ [8](#user-content-fn-43) |
| Zaraz | ✅ | ✅ | ✅ |

***

## Application Security

| Product | Geo Key Manager | Regional Services | Customer Metadata Boundary |
| - | - | - | - |
| Advanced Certificate Manager | ⚫️ | ⚫️ | ⚫️ |
| Advanced DDoS Protection | ✅ | ✅ | 🚧 [9](#user-content-fn-3) |
| API Shield | ✅ | ✅ | 🚧 [10](#user-content-fn-4) |
| Bot Management | ✅ | ✅ | 🚧 [11](#user-content-fn-5) |
| DNS Firewall | ⚫️ | ⚫️ | 🚧 [12](#user-content-fn-22) |
| Page Shield | ✅ | ✅ | ✅ |
| Rate Limiting | ✅ | ✅ | ✅ [13](#user-content-fn-37) |
| SSL | ✅ | ✅ | ✅ |
| Cloudflare for SaaS | ✘ | ✅ | ✅ |
| Turnstile | ⚫️ | ✘ | ✅ [14](#user-content-fn-38) |
| WAF/L7 Firewall | ✅ | ✅ | ✅ |
| DMARC Management | ⚫️ | ⚫️ | ✅ |

***

## Developer Platform

| Product | Geo Key Manager | Regional Services | Customer Metadata Boundary |
| - | - | - | - |
| Cloudflare Images | ⚫️ | ✅ [15](#user-content-fn-36) | 🚧 [16](#user-content-fn-35) |
| AI Gateway | ✘ | ✘ | 🚧 [17](#user-content-fn-39) |
| Cloudflare Pages | ✅ [18](#user-content-fn-11) | ✅ [18](#user-content-fn-11) | 🚧 [5](#user-content-fn-1) |
| Cloudflare D1 | ⚫️ | ⚫️ | 🚧 [19](#user-content-fn-40) |
| Durable Objects | ⚫️ | ✅ [20](#user-content-fn-7) | 🚧 [5](#user-content-fn-1) |
| Email Routing | ⚫️ | ⚫️ | ✅ |
| R2 | ✅ [21](#user-content-fn-27) | ✅ [22](#user-content-fn-8) | ✅ [23](#user-content-fn-28) |
| Smart Placement | ⚫️ | ✘ | ✘ |
| Stream | ⚫️ | ✘ | 🚧 [5](#user-content-fn-1) |
| Workers (deployed on a Zone) | ✅ | ✅ | 🚧 [24](#user-content-fn-41) |
| Workers AI | ⚫️ | ✘ | ✅ |
| Workers KV | ⚫️ | ✘ | ✅ [25](#user-content-fn-34) |
| Workers.dev | ✘ | ✘ | ✘ |
| Workers Analytics Engine (WAE) | ⚫️ | ⚫️ | 🚧 [5](#user-content-fn-1) |

***

## Network Services

| Product | Geo Key Manager | Regional Services | Customer Metadata Boundary |
| - | - | - | - |
| Argo Smart Routing | ✅ | ✘ [26](#user-content-fn-9) | ✘ [27](#user-content-fn-10) |
| Static IP/BYOIP | ⚫️ | ✅ [28](#user-content-fn-26) | ⚫️ |
| Magic Firewall | ⚫️ | ⚫️ | ✅ |
| Magic Network Monitoring | ⚫️ | ⚫️ | 🚧 [5](#user-content-fn-1) |
| Magic Transit | ⚫️ | ⚫️ | 🚧 [5](#user-content-fn-1) |
| Magic WAN | ⚫️ | ⚫️ | ✅ |
| Spectrum | ✅ | ✅ [29](#user-content-fn-42) | ✅ |

***

## Platform

| Product | Geo Key Manager | Regional Services | Customer Metadata Boundary |
| - | - | - | - |
| Logpull | ⚫️ | ⚫️ | 🚧 [30](#user-content-fn-12) |
| Logpush | ⚫️ | ✅ | 🚧 [31](#user-content-fn-13) |
| Log Explorer | ⚫️ | ⚫️ | ✘ [32](#user-content-fn-23) |

***

## Zero Trust

| Product | Geo Key Manager | Regional Services | Customer Metadata Boundary |
| - | - | - | - |
| Access | 🚧 [33](#user-content-fn-14) | 🚧 [34](#user-content-fn-15) | 🚧 [35](#user-content-fn-16) |
| Browser Isolation | ⚫️ | 🚧 [36](#user-content-fn-17) | ✅ |
| CASB | ⚫️ | ⚫️ | ✘ |
| Cloudflare Tunnel | ⚫️ | 🚧 [37](#user-content-fn-18) | ⚫️ |
| DLP | ⚫️ [38](#user-content-fn-19) | ⚫️ [38](#user-content-fn-19) | 🚧 [39](#user-content-fn-31) |
| Gateway | 🚧 [40](#user-content-fn-20) | 🚧 [41](#user-content-fn-21) | 🚧 [12](#user-content-fn-22) |
| WARP | ⚫️ | ⚫️ | 🚧 [5](#user-content-fn-1) |

## Footnotes

1. You cannot yet specify region location for object storage itself. [↩](#user-content-fnref-29)

2. [Outgoing zone transfers](https://developers.cloudflare.com/dns/zone-setups/zone-transfers/cloudflare-as-primary/) will carry Earth region proxy IPs, thus making regional service dysfunctional when non-Cloudflare nameservers respond to the DNS queries. [↩](#user-content-fnref-33)

3. Dashboard Analytics are empty when using CMB outside the US region. Use Logpush instead. [↩](#user-content-fnref-32)

4. Only when using a Custom Domain set to a region, either through Workers or [Transform Rules](https://developers.cloudflare.com/images/transform-images/serve-images-custom-paths/) within the same zone. [↩](#user-content-fnref-6)

5. Logs / Analytics not available outside US region when using Customer Metadata Boundary. [↩](#user-content-fnref-1) [↩2](#user-content-fnref-1-2) [↩3](#user-content-fnref-1-3) [↩4](#user-content-fnref-1-4) [↩5](#user-content-fnref-1-5) [↩6](#user-content-fnref-1-6) [↩7](#user-content-fnref-1-7) [↩8](#user-content-fnref-1-8) [↩9](#user-content-fnref-1-9)

6. Regular and Custom Tiered Cache works; Smart Tiered Caching not available with Regional Services. [↩](#user-content-fnref-2)

7. Regular/Generic and Custom Tiered Cache works; Smart Tiered Caching does not work with Customer Metadata Boundary (CMB).\
   With CMB set to EU, the Zone Dashboard **Caching** > **Tiered Cache** > **Smart Tiered Caching** option will not populate the Dashboard Analytics. [↩](#user-content-fnref-30)

8. Web Analytics collects the [minimum amount of information](https://developers.cloudflare.com/web-analytics/data-metrics/data-origin-and-collection/). Alternatively, you can [exclude EU Visitors from RUM](https://developers.cloudflare.com/speed/speed-test/rum-beacon/#rum-excluding-eeaeu). [↩](#user-content-fnref-43)

9. Adaptive DDoS Protection is only supported for US CMB. [↩](#user-content-fnref-3)

10. Features such as API Discovery and Volumetric Abuse Detection will not work with CMB set to EU only. [↩](#user-content-fnref-4)

11. Some advanced Enterprise features, including the [Anomaly Detection engine](https://developers.cloudflare.com/bots/concepts/bot-score/#anomaly-detection), are not available. [↩](#user-content-fnref-5)

12. Dashboard Analytics and Logs are empty when using CMB outside the US region. Use Logpush instead. [↩](#user-content-fnref-22) [↩2](#user-content-fnref-22-2)

13. Legacy Zone Analytics & Logs section not available outside US region when using CMB. Use [Security Analytics](https://developers.cloudflare.com/waf/analytics/security-analytics/) instead. [↩](#user-content-fnref-37)

14. [Turnstile Analytics](https://developers.cloudflare.com/turnstile/turnstile-analytics/) are available. However, there are no regionalization guarantees for the Siteverify API yet. [↩](#user-content-fnref-38)

15. Only when using a [Custom Domain](https://developers.cloudflare.com/images/manage-images/serve-images/serve-from-custom-domains/) set to a region. [↩](#user-content-fnref-36)

16. Logs / Analytics not available outside US region when using Customer Metadata Boundary. Jurisdictional Restrictions (storage) options are not supported today. [↩](#user-content-fnref-35)

17. Jurisdictional Restrictions (storage) options for [Logs](https://developers.cloudflare.com/ai-gateway/observability/logging/) are not supported today. [↩](#user-content-fnref-39)

18. Only when using [Custom Domain](https://developers.cloudflare.com/pages/configuration/custom-domains/) set to a region. [↩](#user-content-fnref-11) [↩2](#user-content-fnref-11-2)

19. Jurisdictional Restrictions ([data location](https://developers.cloudflare.com/d1/configuration/data-location/) / storage) options are not supported today. [↩](#user-content-fnref-40)

20. [Jurisdiction restrictions for Durable Objects](https://developers.cloudflare.com/durable-objects/reference/data-location/#restrict-durable-objects-to-a-jurisdiction). [↩](#user-content-fnref-7)

21. Only when using a Custom Domain and a [Custom Certificate](https://developers.cloudflare.com/r2/reference/data-security/#encryption-in-transit) or [Keyless SSL](https://developers.cloudflare.com/ssl/keyless-ssl/). [↩](#user-content-fnref-27)

22. Only when using a [Custom Domain](https://developers.cloudflare.com/r2/buckets/public-buckets/#connect-a-bucket-to-a-custom-domain) set to a region and using [jurisdictions with the S3 API](https://developers.cloudflare.com/r2/reference/data-location/#using-jurisdictions-with-the-s3-api). [↩](#user-content-fnref-8)

23. R2 Dashboard [Metrics and Analytics](https://developers.cloudflare.com/r2/platform/metrics-analytics/) are populated. Additionally, [Jurisdictional Restrictions](https://developers.cloudflare.com/r2/reference/data-location/#jurisdictional-restrictions) guarantee objects in a bucket are stored within a specific jurisdiction. [↩](#user-content-fnref-28)

24. Logs / Analytics not available outside US region when using Customer Metadata Boundary. Use Logpush instead. [↩](#user-content-fnref-41)

25. Jurisdictional Restrictions (storage) for Workers KV pairs is not supported today. [↩](#user-content-fnref-34)

26. Argo cannot be used with Regional Services. [↩](#user-content-fnref-9)

27. Argo cannot be used with Customer Metadata Boundary. [↩](#user-content-fnref-10)

28. Static IP/BYOIP can be used with the legacy Spectrum setup. [↩](#user-content-fnref-26)

29. Only applies to HTTP/S Spectrum applications. [↩](#user-content-fnref-42)

30. Logpull not available when using Customer Metadata Boundary outside US region. Logs may be stored and retrieved with [Logs Engine](https://blog.cloudflare.com/announcing-logs-engine/) which is adding region support in 2025. [↩](#user-content-fnref-12)

31. Logpush available with Customer Metadata Boundary for [these datasets](https://developers.cloudflare.com/data-localization/metadata-boundary/logpush-datasets/). Contact your account team if you need another dataset. [↩](#user-content-fnref-13)

32. Currently, customers do not have the ability to choose the location of the Cloudflare-managed R2 bucket for Log Explorer. [↩](#user-content-fnref-23)

33. Access App SSL keys can use Geo Key Manager. [Access JWT](https://developers.cloudflare.com/cloudflare-one/identity/authorization-cookie/validating-json/) is not yet localized. [↩](#user-content-fnref-14)

34. Can be localized to US FedRAMP Moderate Domestic region only. [↩](#user-content-fnref-15)

35. Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region. [↩](#user-content-fnref-16)

36. Currently may only be used with US FedRAMP region. [↩](#user-content-fnref-17)

37. The only connectivity option is [US FedRAMP Moderate Domestic region](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters/run-parameters/#region). Regional Services only applies when using [Public Hostnames](https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/routing-to-tunnel/) set to a region. [↩](#user-content-fnref-18)

38. Uses Gateway HTTP and CASB. [↩](#user-content-fnref-19) [↩2](#user-content-fnref-19-2)

39. DLP is part of Gateway HTTP, however, [DLP datasets](https://developers.cloudflare.com/cloudflare-one/policies/data-loss-prevention/datasets/#use-dlp-datasets) are not available outside US region when using Customer Metadata Boundary. [↩](#user-content-fnref-31)

40. You can [bring your own certificate](https://blog.cloudflare.com/bring-your-certificates-cloudflare-gateway/) to Gateway but these cannot yet be restricted to a specific region. [↩](#user-content-fnref-20)

41. Gateway HTTP supports Regional Services. Gateway DNS does not yet support regionalization.\
    ICMP proxy and WARP-to-WARP proxy are not available to Regional Services users. [↩](#user-content-fnref-21)
