Containers

Containers fills an obvious gap in the Workers platform. Sometimes you need a real Linux process for an existing binary, an unsupported runtime, or CPU-heavy work. You can now run one on Cloudflare’s network and address it from a Worker.

That Worker dependency is also the biggest structural drawback. Every container is reached through a Worker and managed by a Durable Object, so you cannot deploy one without buying into the rest of the platform. This is an add-on for Workers architectures, not a standalone container service, and it inherits the operational concerns of Durable Objects. Instance choices are limited, cold starts take seconds, and sustained workloads can cost more than simply renting a VM. That leaves it squarely in the middle.

For heavy, stateful compute, owned hardware still wins comfortably. As burst capacity for a Workers-first architecture, though, Containers is already handy for the odd FFmpeg job, legacy binary, or build step. It is also clearly early in its life.