Containers are available in public beta for simple, and programmable compute
blog.cloudflare.com
Containers are available in public beta for simple, and programmable compute
1–10 of 23 posts
Re: Containers are available in public beta for simple, and programmable compute
#2Would UDP services and anycast DNS be supported in the future e.g. to be able to run dnsdist or similar services.
Re: Containers are available in public beta for simple, and programmable compute
#3If my math is not wrong, running a single “standard” container during 1 month (non-stop) would cost ~55$.
This looks extremely expensive for anything other than a simple demo/toy project. I can’t think of a reason I’d use this for heavy services instead of using [anything else]. Maybe I’m not seeing the use-case?
Re: Containers are available in public beta for simple, and programmable compute
#4If my math is not wrong, running a single “standard” container during 1 month (non-stop) would cost ~55$. This looks extremely expensive for anything other than a simple demo/toy project. I can’t think of a reason I’d use this for heavy services instead of using [anything else]. Maybe I’m not seeing the use-case?
I don't think you can calculate the cost of serverless compute this way. What containers do you have that run "non-stop"?
If the container doesn't run any workloads, it doesn't cost you anything. Most of the compute i pay for sit idle most of the time.
This is amazing pricing.
Re: Containers are available in public beta for simple, and programmable compute
#5If my math is not wrong, running a single “standard” container during 1 month (non-stop) would cost ~55$. This looks extremely expensive for anything other than a simple demo/toy project. I can’t think of a reason I’d use this for heavy services instead of using [anything else]. Maybe I’m not seeing the use-case?
Math is not wrong for the standard instance.
This is about using and abusing the _on-demand_ part.
The first example in the Getting started goes with sleepAfter = '10s'.
Re: Containers are available in public beta for simple, and programmable compute
#6If my math is not wrong, running a single “standard” container during 1 month (non-stop) would cost ~55$. This looks extremely expensive for anything other than a simple demo/toy project. I can’t think of a reason I’d use this for heavy services instead of using [anything else]. Maybe I’m not seeing the use-case?
I don't think you can calculate the cost of serverless compute this way. What containers do you have that run "non-stop"? If the container doesn't run any workloads, it doesn't cost you anything. Most of the compute i pay for sit idle most of the time. This is amazing pricing.
Say I want to deploy a service that is currently receiving 1rps at a constant rate, no upticks, no gaps. Wouldn’t that be the cost? If the answer is “yes”, then no, that is a terrible pricing.
Re: Containers are available in public beta for simple, and programmable compute
#7(I work at Cloudflare) We shipped a Containers 101 video today showing how to get up and running. YT: https://www.youtube.com/watch?v=oyOaxMY4eNo
Re: Containers are available in public beta for simple, and programmable compute
#8We published an in-depth comparison between Cloudflare Containers, Fly Machines, and Rivet Containers: https://rivet.gg/blog/2025-06-24-cloudflare-containers-vs-ri...
(I work at Rivet)
Re: Containers are available in public beta for simple, and programmable compute
#9Would UDP services and anycast DNS be supported in the future e.g. to be able to run dnsdist or similar services.
They stated on the livestream they're considering TCP, but I suspect UDP is not coming soon since Workers themselves don't support UDP. All traffic going to Cloudflare Containers must be "proxied" through the Workers platform.
Re: Containers are available in public beta for simple, and programmable compute
#10If my math is not wrong, running a single “standard” container during 1 month (non-stop) would cost ~55$. This looks extremely expensive for anything other than a simple demo/toy project. I can’t think of a reason I’d use this for heavy services instead of using [anything else]. Maybe I’m not seeing the use-case?
A 1 CPU + 2 GB of RAM + 50 GB ephemeral storage on Cloudflare Containers is $74.90.
The same on Fly Machines is $31.00 (performance-1x, varies by region). Fly Machines has the same sleeping functionality as Cloudflare.
Rivet Containers also has a similar price point of $29.40, but takes a different approach to sleeping (opts for optimizing coldstarts + autoscaling over snapshotting). (I work at Rivet)