Script
Here is today's Cloudflare Daily for Friday August 14th. Yesterday, Cloudflare Gateway added package registry security, giving organizations more control over a frequently overlooked supply-chain risk: software dependencies downloaded by developers and CI/CD systems. Gateway can now identify package downloads by protocol, extracting details such as ecosystem, package name, version, namespace, and Package URL. Administrators can then write allow or block policies for npm, PyPI, RubyGems, Cargo, Go, Maven, and NuGet packages. Because detection uses the registry protocol rather than a particular hostname, the controls can also work with internal mirrors and proxies such as Artifactory or Nexus. TLS decryption is required. [1]
Also yesterday, Cloudflare Artifacts introduced data-localization support. When creating an Artifacts namespace, teams can now choose the European Union or United States as the sole jurisdiction for repository data storage and processing. Every repository in that namespace inherits the setting. The choice cannot be changed later, so organizations with compliance, sovereignty, or customer-contract requirements should make jurisdiction part of their initial project design rather than treating it as a later migration task. [2]
A third update improves Cloudflare Realtime SFU DataChannels for low-latency applications. Developers can now choose unordered or partially reliable delivery instead of the default reliable, ordered behavior. That is especially useful for game state, sensor readings, chat presence, and control events, where a newer update may be more valuable than a delayed older one. Teams can set no retries, limited retransmissions, or a time limit on delivery, tailoring transport behavior to how quickly information becomes stale. [3]
The broader trend is more precise control at infrastructure boundaries. Cloudflare is giving security teams policy-level visibility into what enters development environments, compliance teams clearer control over where data lives, and application developers more choice over how realtime data behaves. The common lesson is that defaults remain important, but modern systems increasingly need controls that reflect the specific risk, location, and lifetime of each workload. [4]
Thank you for listening to Cloudflare Daily from The Daily FM. See you tomorrow!
- Changelogs | Cloudflare Docs
...to Data localization.Aug 13, 2026Detect and control software package downloads with package registry securityCloudflare Gateway can now detect software package downloads and give you policy control over supply chain traffic. When a developer or CI/CD pipeline downloads a package through Gateway, the proxy identifies the registry protocol from the request URL and extracts the package ecosystem, name, version, and namespace. You can then write HTTP policies using pkg.* selectors to allow or block package downloads. Gateway detects package downloads for the following ecosystems: Ecosystem Namespace npm Scope (for example, @babel) PyPI -- RubyGems -- Cargo -- Go Module path Maven Group ID NuGet -- In the dashboard, select Package Ecosystem to access the package registry selectors. After selecting a single ecosystem, nested fields for package name, version, and n...
- Changelogs | Cloudflare Docs
...dates and improvements at Cloudflare.Aug 13, 2026Data localization support for ArtifactsArtifacts now supports jurisdictions, allowing you to select the European Union or the United States as the only location where repo data is stored and processed. Select a jurisdiction when you create a namespace. Every repo in that namespace automatically uses the selected jurisdiction. curl --request POST \ "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/artifacts/namespaces" \ --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \ --header "Content-Type: application/json" \ --data '{ "namespace": "my-eu-namespace", "jurisdiction": "eu" }' Jurisdictions cannot be changed after namespace creation. If you omit the jurisdiction, Artifacts creates an unrestricted namespace. For supported jurisdictions and usage details, refer to Data localization.Aug 13, 2026Detect and c... - Changelogs | Cloudflare Docs
..., game state, sensor updates, and control events. Realtime SFU DataChannels now support unordered and partially reliable delivery. DataChannels remain reliable and ordered by default, so existing channels keep their current behavior. With ordered delivery, a delayed message can block later messages. For game state or sensor updates, recent data may be more useful than recovering an older message. Unordered delivery lets later messages proceed, while partial reliability limits retransmission attempts or delivery time. Delivery settings answer two questions: whether newer messages can bypass a delayed message, and when the transport should stop retrying delivery. Choose the policy that matches how long your payload remains useful: Goal Settings Use when Reliable, ordered delivery (default) Omit ordered, maxRetransmits, and maxPacketLifeTime Messages remain useful an...
- Changelogs | Cloudflare Docs
...13, 2026Control Realtime SFU DataChannel delivery Cloudflare Realtime SFU is a WebRTC selective forwarding unit that runs on Cloudflare's global network. It forwards audio, video, and application data between WebRTC clients without requiring you to manage SFU infrastructure or regions. DataChannels are WebRTC channels for application messages. A client publishes a named DataChannel to Realtime SFU, and the SFU forwards its messages to every client that subscribes to that channel. Use DataChannels for low-latency payloads such as chat messages, game state, sensor updates, and control events. Realtime SFU DataChannels now support unordered and partially reliable delivery. DataChannels remain reliable and ordered by default, so existing channels keep their current behavior. With ordered delivery, a delayed message can block later messages. For game state or sensor updat...