Cloudflare Workers now run global containers (open beta June 2025)

DevOpsEdgeContainersCloudflareWorkers

Key update

Cloudflare announced Containers for Workers (open beta planned for June 2025): you can now declare and deploy container images alongside Workers, start and route to container instances from Worker code (via a Container class or Durable Objects), autoscale or sleep instances, and run stateful or long-running workloads at Cloudflare’s edge with a single wrangler deploy flow. Examples in the announcement show per-session sandboxes (user-generated or LLM-executed code), global FFmpeg jobs, and Workers acting as API gateways, orchestrators or service-mesh frontends to containers. (blog.cloudflare.com)

Why it matters

This is a practical bridge between serverless edge code and full container workloads: teams can port existing Docker-based services to hundreds of edge locations without building out Kubernetes operators or global infra. For developers that need low-latency, regional processing (video/FFmpeg, code sandboxes, CLI tooling, or stateful session workers) it reduces network hops and simplifies routing, scaling, and lifecycle hooks via Workers + Durable Objects. Expect faster iteration for edge-heavy features and simpler migration paths for some backend services, but also new operational considerations: cold-start and warmup patterns, observability and billing for globally distributed instances, and evaluating security/tenant isolation for untrusted code. Treat the beta as a technical evaluation—test realistic workloads, measure startup times and cost, and validate quota/isolation guarantees before production rollout. (blog.cloudflare.com)

Source

Read Next