Cloudflare expands agent infrastructure with quantum-safe TLS plans and faster containers
Cloudflare said on Wednesday it plans to issue quantum-proof TLS certificates, among the first certificate authorities to do so. It also rebuilt its Containers platform, which now starts sandboxes more than six times faster.
Cloudflare said on Wednesday it plans to issue quantum-proof TLS certificates. That would make it one of the first certificate authorities to offer them. The company also pushed out a rebuilt Containers platform, an error-monitoring tool for Workers, a public beta of its Auto Router and a closed beta of a payment gateway for AI agents. All five announcements landed on the same day, according to the company's own blog posts and a report by Ars Technica.
The certificates are the headline. Cloudflare will run an open source platform that issues both classic TLS certificates and a post-quantum equivalent called Merkle Tree Certificates, Ars Technica reported on 30 September. The hybrid certificates will be free to paying and non-paying users alike. To get there, Cloudflare is acquiring an already trusted certificate root from CA GlobalSign. The company says the move will let millions of websites switch to post-quantum certificates without added performance overhead.
None of this is live yet. "We are not issuing certificates yet, and it will be a little while before we do," Cloudflare's Steve Goldsmith wrote, in a quote carried by Ars Technica. "What we are doing is committing to the work in public, sharing the milestones as they land, and telling you exactly what we are building while working with the root programs and other members of the WebPKI community to achieve this."
Why the handshake has to change
The problem is size. Quantum-proof versions of today's classical X.509 certificates would add roughly 40 times the data required for a TLS handshake, according to Ars Technica. That handshake is the exchange that happens every time a browser opens a session with a server. The added computation and bandwidth would break the web as it currently runs. Google proposed Merkle Trees in February as a way out: hierarchical data structures that verify large amounts of information using a small fraction of it. The design, tested in limited pilots by Google and Cloudflare, drops handshake data to about 40 kilobytes, roughly what is processed today.
Instead of a multi-link chain of signatures, a certificate authority signs a single "tree head" representing millions of certificates. Browsers usually handle a "landmark", a lightweight proof that a certificate sits somewhere in the tree. Industry rules still require certificates to be published in append-only public transparency logs. Ars Technica notes that is one of the harder parts to fit into the new design.
The rebuild will take years. It touches operating systems, browsers, certificate authorities and internet infrastructure. No single vendor controls the schedule.
Containers get a scheduling rewrite
The Containers changes are shipping now, at least in part. Cloudflare said it rearchitected the platform so application code can pick each sandbox's image and instance type at runtime. Filesystem snapshots are available in public beta. In ComputeSDK's independent benchmark, median startup fell from just over four seconds to 648 milliseconds, the company's blog post says. Cloudflare's own preliminary burst tests created hundreds of thousands of containers in seconds. The company describes the new policy as durable_object scheduling, and says Sandbox SDK 1.0 carries the same model forward.
The pitch is that agents do not deploy sandboxes ahead of time. They create one per task, expect it instantly, and want to pause and resume it later. Cloudflare names Base44, Kilo Code, Cursor Cloud Agents, Devin Outposts, the OpenAI Agents API and Claude Managed Agents as workloads already running this way. Every Container still gets its own Durable Object as a controller sitting next to it.
Separately, Cloudflare put its Issues error monitoring into open beta for Workers. The feature groups repeated exceptions, 5xx responses and error logs into one issue. It can then hand the error, stack trace, logs, traces and Worker version to a configured coding agent. It needs one line of configuration and no SDK, because it is built into the Workers runtime. Developers can attach user, account and session identifiers through the runtime's built-in OpenTelemetry API. They can then route issues to Claude Code or Cursor once they cross an occurrence threshold.
Routing models, charging agents
On the AI side, Cloudflare released Auto Router in public beta through AI Gateway. Setting a model to cloudflare/auto routes each request to a model the company judges capable enough for the task. Cloudflare says early internal results through its OpenCode harness showed cost savings of up to 30% against using only frontier models such as OpenAI Sol and Anthropic Claude Opus. It evaluated the router against OpenAI's GPT-6 Sol and Anthropic's Claude Opus 5.5 on an internal benchmark of 97 tasks with three samples per model per task. The tasks covered email, calendars, Slack, files, travel and finance.
The Monetization Gateway is narrower: a closed beta that lets domain owners charge agents for access to sites, APIs, MCP tools or datasets, priced per request. It uses the HTTP 402 Payment Required status code so payment travels inline with the request rather than through a checkout redirect. Cloudflare says stablecoin transactions currently meet the latency and cost profile agents need, and that other payment networks may follow.
Not every item in the day's news cycle was a Cloudflare post. A GitHub project called LocalThings showed up in the same window, connecting Samsung SmartThings appliances to Home Assistant over the local network with no cloud account. It talks to appliances over CoAP and DTLS and checks non-push devices every 30 seconds. Most Samsung appliances from about 2022 onward work, the README says, plus some earlier washers, air conditioners and wall ovens on an older local interface.
There was also a startup launch page. InstaCloud describes itself as an agent-native serverless cloud backed by Combinator, with auto-scaling to zero and environment cloning for parallel agent work. The page carries no pricing, no customer names and no independent benchmarks. Treat the claims as marketing until someone tests them.
The money outside the cloud
Investment news in the same 24-hour window leaned toward energy and manufacturing rather than data centres. Bloomberg reported, and Seeking Alpha relayed on 30 September, that President Donald Trump is expected to unveil roughly $200 billion in South Korean investments in the United States on Wednesday. About $54 billion of that is tied to the long-delayed Alaska LNG project. Shipbuilding, LNG and power plants, and nuclear energy are the targeted areas, according to Seeking Alpha's summary. Those figures come from people familiar with the discussions, not from a signed document.
For cloud watchers, the relevance is indirect. Large gas and nuclear commitments shape where power-hungry capacity can eventually sit. But nothing in the public record ties the South Korean package to a specific cloud region or operator. Cloudflare's own announcements say nothing about new regions either.
What the day does show is where Cloudflare is placing its bets: identity and encryption on one side, agent runtime and agent payments on the other. The certificate work is the slowest of the five and the most consequential. Everything else is available to try now, in beta form, with the usual caveats about benchmarks run by the vendor or its partners. ComputeSDK's startup number is the exception, and even that measures one workload pattern.
Sources
8- 01Cloudflare plans to issue quantum-safe TLS certificatesEN
- 02Cloudflare Containers, rebuilt to scale agent sandboxesEN
- 03Detect and send production issues straight to your agentEN
- 04Cut your AI spend with AI Gateway's Auto RouterEN
- 05Monetization Gateway beta: charge AI agents for consumption with HTTP 402EN
- 06Trump set to unveil $200B South Korean U.S. investment planEN
- 07LocalThings: SmartThings devices in Home Assistant without a cloud connectionEN
- 08InstaCloud: Agent-Native Serverless CloudEN
All figures and quotations in this text come from the sources listed below.
Content prepared by the editorial team with AI assistance.
Comments
0- No comments yet — be the first.