Cloudflare Containers, rebuilt to scale agent sandboxes

Cloudflare has introduced a new durable_object scheduling policy for Containers, aimed at agent workloads that require on-demand, configurable, persistent Linux sandboxes. The update lets application code running in Durable Objects select a Container’s image and compute instance type at runtime, rather than requiring separate preconfigured deployments, while also enabling code-managed rollout strategies. Cloudflare reports that a redesigned scheduling path and runtime reduce median Container startup time from 4.049 seconds to 648 milliseconds in an independent benchmark, with preliminary internal tests creating 100,000 Containers in 5.387 seconds across six locations. A new prepared Debian Trixie system image is intended to reduce setup overhead, and public-beta filesystem snapshots allow workspaces to be saved, restored, and reused as consistent baselines for tasks such as coding sessions, evaluations, and reinforcement learning. The company positions Durable Objects as persistent controllers for Container identity, state, lifecycle, networking, credentials, and supervision, with new native ctx.container APIs replacing much of the prior wrapper-based model. New functionality is available only through the native Durable Object approach, while the existing Container and legacy Sandbox classes will be maintained without updates through December 31, 2026, and Sandbox SDK 1.0 is being refocused as a collection of utilities for developers’ own Durable Object classes.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.