Engineering Insights

4M Models Scanned: Protect AI + Hugging Face 6 Months In

Hugging Face to sell open-source robots thanks to Pollen Robotics acquisition 🤖

Visual Salamandra: Pushing the Boundaries of Multimodal Understanding

Gateway - HTTP redirect and custom block page redirect

You can now use more flexible redirect capabilities in Cloudflare One with Gateway. A new Redirect action is available in the HTTP policy builder, allowing admins to redirect users to any URL when their request matches a policy. You can choose to preserve the original URL and query string, and optionally include policy context via query parameters. For Block actions, admins can now configure a custom URL to display when access is denied. This block page redirect is set at the account level and c

Stream - Signed URLs and Infrastructure Improvements on Stream Live WebRTC Beta

Cloudflare Stream has completed an infrastructure upgrade for our Live WebRTC beta support which brings increased scalability and improved playback performance to all customers. WebRTC allows broadcasting directly from a browser (or supported WHIP client) with ultra-low latency to tens of thousands of concurrent viewers across the globe. Additionally, as part of this upgrade, the WebRTC beta now supports Signed URLs to protect playback, just like our standard live stream options (HLS/DASH). For

Workers AI - Workers AI for Developer Week - faster inference, new models, async batch API, expanded LoRA support

Happy Developer Week 2025! Workers AI is excited to announce a couple of new features and improvements available today. Check out our blog for all the announcement details. Faster inference + New models We’re rolling out some in-place improvements to our models that can help speed up inference by 2-4x! Users of the models below will enjoy an automatic speed boost starting today: @cf/meta/llama-3.3-70b-instruct-fp8-fast gets a speed boost of 2-4x, leveraging techniques like speculative decoding,

Legacy build image is being deprecated on September 1, 2025

Node.js 18 (LTS support ends April 30, 2025) and the Vercel legacy build image will be deprecated on September 1, 2025. If you are still using the legacy build image on this date, new builds will display an error. What changes between the legacy build image and latest build image? How do I know if I am still using the legacy build image? Will my existing deployments be affected? Existing deployments However, the Node.js version will need to be updated on your next deployment.will not be affected

BrowseComp: a benchmark for browsing agents

BrowseComp: a benchmark for browsing agents.