Cloudflare
Cloudflare at Beyond Market Intelligence is a file of 32 stories. The newest of them: “Vite+ 1.0 Brings Unified JavaScript Tooling to GitLab and Docker Workflows”, “Cloudflare's new gateway keeps decryption separate from its own traffic”, and “Cloudflare expands its platform by welcoming Deno's expertise”. If you're managing Node.js, packages, and frontend builds across GitLab and Docker, Vite+ 1.0 treats them as one workflow instead of three. Cloudflare's OHTTP Gateway is drawing attention for what it refuses to do: decrypt traffic arriving from its own Workers or proxied hosts. Acme AI is the next-generation, AI-powered spreadsheet platform built to replace Excel and redefine how analysts, data scientists, and enterprise teams work… The list below is every Cloudflare story on Beyond Market Intelligence, newest first.
Vite+ 1.0 Brings Unified JavaScript Tooling to GitLab and Docker Workflows
If you're managing Node.js, packages, and frontend builds across GitLab and Docker, Vite+ 1.0 treats them as one workflow instead of three. VoidZero's stable toolchain unifies these tasks under a single configuration file, then extends that control into CI with native GitLab and Docker support. It's a practical step toward simpler, more automated JavaScript development. For teams exploring similar platform efficiency, our coverage of GitLab 19.4 and its goal-driven AI mode offers useful context.
Cloudflare's new gateway keeps decryption separate from its own traffic
Cloudflare's OHTTP Gateway is drawing attention for what it refuses to do: decrypt traffic arriving from its own Workers or proxied hosts. That separation matters, because it keeps client identifiers and request contents out of the same hands. It's a thoughtful constraint in a privacy landscape where trust is often the first casualty. For deeper platform context, our coverage of Cloudflare welcoming Deno's expertise offers useful background on how the company is evolving its developer stack.
Cloudflare expands its platform by welcoming Deno's expertise
Cloudflare is welcoming Deno's team and its expertise to strengthen the Workers programming model. This move signals a thoughtful investment in the developer experience, making the platform more capable without adding unnecessary complexity. For anyone who has felt the limits of traditional serverless setups, this is a step toward a more accessible and empowering environment. If you are exploring how Cloudflare is evolving its data and event tooling, our coverage of the K2 beta offers a useful look at that momentum.
Cloudflare's K2 Beta Turns Object Storage Into a One-Second Event Stream
Cloudflare's K2 beta turns R2 object storage into a serverless event stream with roughly one-second produce latency at p99. That's a compelling shift for teams already invested in Cloudflare's ecosystem, though the 7.5-second end-to-end p99 reported by one tester suggests the full path still has room to tighten. Consume charges matching produce charges keeps pricing predictable. For deeper context on Cloudflare's AI ambitions, Clef offers a sharper decision-making model worth exploring.
Cloudflare Clef gives AI agents a sharper decision-making model
Cloudflare's Clef takes a different path for AI agents: instead of generating open-ended text, it picks between predefined options. That's a sharper fit for decision-making tasks where precision matters more than prose. The 9B and 27B open-weight models, along with a platform for task-specific tuning, give developers room to adapt. It's a practical step forward, not a flashy one. For more on how AI models are being tested in the wild, our piece on Cloudflare's firewall stress-tests pairs nicely with this.
How AI Models Stress-Test Cloudflare's Firewall to Find Its Weaknesses
Cloudflare placed frontier AI models inside a controlled harness to probe its own Web Application Firewall, using blocked attacks as starting points for the models to generate and refine new variations. It is a clever form of stress-testing that turns AI into an adversary you actually want. The approach feels honest about where security is headed. For more on Cloudflare's AI-forward strategy, see our coverage of its new agent-focused CLI.
Cloudflare's new CLI opens the door for AI agents to command its services
Cloudflare's new open-beta CLI, called cf, is built for a future where AI agents work alongside developers. Written in TypeScript, it offers structured output and command discovery that make Cloudflare's APIs more accessible. This is a practical step toward letting autonomous systems manage infrastructure directly. It also complements our coverage of an autonomous AI fleet probing Alibaba's map service, showing how agent-driven tools are reshaping what's possible in cloud operations.
Cloudflare resolves data leak risk across container boundaries
Recovering complete SQLite databases from a neighbor's container isn't a theoretical risk, it was a real vulnerability in Cloudflare's infrastructure. The company disclosed a cross-tenant data exposure flaw in Containers and Sandboxes, where thin-provisioned storage pools failed to zero reused blocks. Researchers pulled directory structures and database pages across four continents. Cloudflare fixed the issue and found no signs of exploitation. For more on how Cloudflare thinks about future-proofing security, explore their work on a quantum-safe path for internet security.
Cloudflare Builds a Quantum-Safe Path for the Future of Internet Security
Quantum-safe security isn't a future problem, it's a present concern that demands real action today. Cloudflare's new path toward post-quantum cryptography signals a mature, necessary shift in how we protect data against tomorrow's threats. This isn't about hype; it's about building trust into the internet's infrastructure from the ground up. For readers exploring how attackers can trick AI spreadsheets into ignoring instructions, the same principle applies: proactive defense matters more than reaction.
Cloudflare's new Vary controls put cache efficiency back in your hands
Cloudflare has put cache efficiency back where it belongs: in your hands. With native support for the HTTP Vary header across its edge network, the company is giving operators finer control over how content representations are negotiated, without the usual fragmentation headaches. It is a practical step toward reducing server load and keeping things fast. For those exploring how far Cloudflare is pushing its platform, their recent work on Python Workers shows the same pattern of thoughtful, developer-focused progress.
Python Workers Go Live as Questions on Speed and Upstream Support Emerge
Cloudflare's Python Workers have gone GA, but the launch feels more like an opening act than a headliner. Built on PEP 783 and socket syscalls over the Workers connect API, the announcement conspicuously omits performance figures. That silence is loud. A urllib3 maintainer is already asking who supports the upstream work afterward, and Wasmer's founder wants cold-start numbers, citing about 1.027 seconds from Cloudflare's own blog. These are fair, pointed questions. If you're evaluating this for production, you'll want answers before committing.
Cloudflare's Blog Finds Performance Gains with EmDash, Its New CMS
When Cloudflare moved its blog off WordPress, it didn't just switch platforms; it built its own CMS, EmDash, and open-sourced it. The payoff is clear: the system handles up to 7,000 requests per second while improving caching and performance. That's a practical win for a team managing heavy traffic. It's a reminder that sometimes the best tool is the one you create yourself. For more on how organizations are building internal infrastructure, check out our piece on Perplexity's CobbleDB migration.
Cloudflare's Data Innovation Frees 100 TB, Boosts DNS Performance
Cloudflare's Big Pineapple DNS cache just got a serious upgrade. By redesigning the in-memory representation of its entries, the team cut the per-entry footprint by 56%. That freed roughly 100 TB of working-set memory across the fleet, which is a massive win for efficiency. The Rust-based changes didn't stop there. Cache insertion throughput climbed 43%, and lookup latency dropped 19%. This means faster, more responsive DNS without needing extra hardware. It's a smart, practical step forward.
Cloudflare's smarter TLS handshake cuts latency by over 150 milliseconds
Cloudflare's decision to replace static origin TLS guesses with per-origin measurement is a smart, practical win. By measuring instead of assuming, they cut HelloRetryRequests from 52% to 3.7% and shaved over 150 ms off p90 latency. That's meaningful progress. Post-quantum connections now complete in one round trip 99.2% of the time, even if only 12.8% of origins support it yet. It's a measured step forward, not hype. For more on how Cloudflare refines performance behind the scenes, their EmDash migration offers another useful look.
Transforming Cache Storage with Smarter Compression for Greater Capacity
Cloudflare's prototype Cache Transcoding takes a straightforward, promising step: compress uncompressed text like HTML and JSON with Zstandard before it hits disk. The potential is real, with petabytes of extra effective capacity on the table, though broader testing remains the next hurdle. It's a pragmatic move that quietly rethinks storage efficiency, and that kind of focus matters. For more on how Cloudflare pushes performance through data innovation, our piece on its Big Pineapple DNS cache redesign offers a useful parallel.
Explore how Cloudflare AI Search makes custom data instantly accessible for agents
Cloudflare's new AI Search gives agents and developers a built-in way to search custom data without building retrieval from scratch. It supports agent integration, multimodal queries, and works alongside other Cloudflare tools. That's practical, not flashy. For teams tired of bolting search onto every project, this feels like a step toward simpler workflows. If you're exploring how AI fits into your stack, you might also check out "Verify Your AI's Understanding: A Simple Check for Tax Season" for a grounded take on validation.
How a blocked attack turned a security agent into a DNS hijacker
A security agent read a Cloudflare log, found an attacker's prompt-injection payload sitting inside it, and rewrote the company's DNS. The firewall had already blocked that payload, and blocking it is what wrote it into the log. That chain is GhostJacking, and it makes one thing clear: a high block rate is not a security boundary. The fix is an authorization gate outside the model, one that lets an agent propose a change but never approve it.
Kitesurf lets agents run browser tasks with less overhead, more control.
Cloudflare's Kitesurf takes a leaner path for automated browsing, running browser components in isolated WebAssembly and Rust environments on Workers. It speaks Chrome DevTools Protocol, so Playwright and Puppeteer can drive it without the resource weight of a full Chromium build. That's a practical step for teams juggling heavy workloads. We've seen similar infrastructure bets pay off elsewhere, like Perplexity's CobbleDB migration, and Kitesurf feels like another thoughtful push toward efficiency. It's worth exploring if your automation stack needs a lighter touch.
How AI agents triaged 85% of Astro's GitHub issues for Cloudflare
Astro's maintainers were drowning in GitHub issues, so they let AI agents take over triage. The result: an 85% cut in that workload, giving developers time back to focus on the work that matters. This isn't about removing humans; it's about making their role more meaningful. Cloudflare's approach, built on Workers with a human-in-the-loop, shows how agentic workflows can handle the noise. It's a practical win for open source, and it pairs well with our guide on distributed training algorithms.
How Cloudflare uses AI to enforce engineering standards automatically
Cloudflare's latest move turns engineering standards from static documents into a live, AI-enforced control system across the software development lifecycle. That's a smart shift. Too often, best practices sit unread in a wiki, waiting for someone to stumble upon them. By embedding enforcement directly into the workflow, Cloudflare is making standards matter where the work actually happens. It's a practical, forward-looking approach that prioritizes consistency without slowing teams down.
Empower AI agents with precise controls for safer data actions.
Cloudflare's WriteGuard, now in private beta, takes a meaningful step toward safer AI agents by giving MCP servers fine-grained control over which tools can modify data or trigger actions. That shift from broad access to precise permissions feels like the right kind of guardrail for a rapidly evolving space. It's a practical move, not a flashy one, and that's what makes it worth your attention. For a broader look at how MCP is shaping workflows, our visual guide offers a solid starting point.
Explore how durable steps transform CI pipelines into resilient workflows
Cloudflare's new CI SDK, cloudflare/ci, reimagines how pipelines are built by defining them as TypeScript workflows. Each step inherits durable retries and replay, while concurrency and snapshot caching come standard. It's a thoughtful model, though it's not a drop-in replacement yet, since Artifacts remains in private beta. The real lesson here is the durable-step approach, a shift worth exploring. For more on Cloudflare's internal builds, our piece on EmDash offers a useful parallel.
Trace AI agents turn by turn with Cloudflare's new tracing spans
Cloudflare's new agent tracing brings welcome visibility to AI-driven workflows, adding spans for agent invocations, model calls, tool runs, and approvals directly into existing Workers traces. Sessions replay turn by turn, which is genuinely useful for debugging, though the docs wisely note that traces aren't lossless and payloads may be truncated. Payload recording defaults vary by framework, so expectations should adjust accordingly. Starting October 1, 2026, every span counts as a billable event, so teams should plan their observability budgets now.
Cloudflare adds response-phase rules for smarter cache control
Cloudflare's new Cache Response Rules add a crucial second phase to its rules engine, evaluating origin responses before they're cached. Previously, Cache Rules only looked at request attributes, leaving response-level control out of reach. This update matters because it gives developers more precise, flexible cache management where it counts. It's a practical step forward, not a flashy overhaul. For deeper performance insights, Cloudflare's own work with EmDash shows the company isn't shy about applying its own innovations to real-world problems.