41–50 of 173 posts
This would only work if they would provision docker image deployment, similar to google cloud run, but the still, everything serveless has its own caveats…
Earlier quoted context omitted.
[flagged]
Cloudflare is in the S&P500. If you have a 401k diversified in broad market indexes then most likely… you are a shareholder.
If eastdakota/jgc are here. - simply expose containers to the world directly - without having to go via workers. - You have other amazing parts of the stack anyway (D1, durable objects, a great object store). These aren't considered "lockin". - workers is "lockin" - not similar enough to lambda/cloud functions and so becomes CF specific. Not having a simple container based compute piece has made me hesitate in taking…
I run workers and containers and am curious what you mean. Do you have specific use cases in mind outside of the worker invocation model? If so, I'm curious what you'd want to run on Cloudflare. Otherwise, workers don't have to be much of a "lockin" if treated as a thin layer, more like configuration.
> You have other amazing parts of the stack anyway (D1, durable objects, a great object store).
Instead, if you mean accessing these resources from containers, it's a bit clunky [0] but it's there - you should be able to access worker bindings from containers through those outbound handlers.
[0] https://developers.cloudflare.com/containers/platform-detail...
Lets keep in mind this is cloudflare workers runtime - it only makes sense to deploy small things there, maybe static sites. Unless the agent creates something for cf workers from scratch, asking it to „now deploy to cloudflare” will fail so bad. This would only work if they would provision docker image deployment, similar to google cloud run, but the still, everything serveless has its own caveats…
What makes you say that?
I want to set a cap of $100/month and know, for sure, that if something untoward happens my apps will all stop serving traffic rather than me getting hit with a bill for $1000s.
The safest way to use Workers is on the free tier, which will shut off after 100,000 requests/day: https://developers.cloudflare.com/workers/platform/pricing/#...
Lets keep in mind this is cloudflare workers runtime - it only makes sense to deploy small things there, maybe static sites. Unless the agent creates something for cf workers from scratch, asking it to „now deploy to cloudflare” will fail so bad. This would only work if they would provision docker image deployment, similar to google cloud run, but the still, everything serveless has its own caveats…
The latest models appear to know CF Workers inside out and are very capable of doing that if you ask them to.
Here's my GPT-5.5 xhigh + Codex Desktop transcript building one just now: https://gist.github.com/simonw/264bd6b8a39fc34c91c9c867454c6... - code here: https://github.com/simonw/cloudflare-redirect-resolver
Earlier quoted context omitted.
Cloudflare is in the S&P500. If you have a 401k diversified in broad market indexes then most likely… you are a shareholder.
About half of US households don’t have any retirement at all. Making their point that “shareholders” are a distinct class separate from the whole of the population.
Would love to know more about how Cloudflare plans to prevent abuse of ephemeral infrastructure to host malicious content. From elsewhere in their documentation, “Cloudflare limits how quickly you can create temporary preview accounts. If the Wrangler CLI cannot create an account because too many temporary preview accounts were requested too quickly, wait before retrying or authenticate the CLI with a permanent Cloud…