Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- The idea of giving a non deterministic automated process direct deployment control is fucking madness to me. That’s why I don’t get the obsession with MCP. Deployment can be scripted. It doesn’t need an LLM, it is a completely deterministic process and you want it to run identically every single time.
The right model for agentic API usage is having LLMs write scripts that use APIs. Connecting agents to MCPs and telling them to go and do stuff over and over not only wastes money but invites catastrophe.
by dools - I am a bit worried about being misused by black and gray industries, which could then lead to Cloudflare or the US Congress imposing various restrictions, resulting in the functionality of my ordinary Cloudflare account being limited.by taosu_la
- posted yesterday as well: https://news.ycombinator.com/item?id=48598906by variety8675
- Correct me if I'm wrong, but does Cloudflare still not have a "Create Account" button on the account listing page? I think you still have to sign up from scratch doing plus-code email tricks, then invite your original email address as an admin, juggling multiple accounts. They should consider fixing that first.by 827a
- Oh actually it's worse now, they blocked email addresses with + in them!
- Cloudflare makes it really hard to spend money. I constantly have to talk to someone in sales to enable some feature after rounds of negotiating on price. I think they would have way more customers, spending much more money, if they just offered transparent pricing, and fully on-demand services.by frogperson
- If I want to onboard a client to Cloudflare, I have to ask them to create an account and then invite me, which is a lot of friction for non-technical people.
A “create account” button accessible to me would be so much better. Then, I create the account and invite the client to join as owner.
by quinncom - Excuse me for asking, doesnt this make it easier to run a malware bot farm and disappear without a trace?by jackbucks
- > Make snail-game in Cloudflare Worker in TypeScript and deploy it using wrangler, don't ask me questions, do the best you can
https://snail-game.solstice-barometer.workers.dev/
pretty cool.
by jsyang00 - 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 up CF. (Fly or firebase won out)
by anilgulecha - I think you have it the other way around? D1, DO, KV are lockin. The worker is not lockin as it's just JavaScript/WASM and can run in a regular browser.by csomar
- >Not having a simple container based compute piece made me hesitate in taking up CF
Agreed. I wish CF had something like Azure's new fast-starting Express containers.
by yodon - > simply expose containers to the world directly - without having to go via workers.
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...
by unix1 - I am here but I retired from being CTO of Cloudflare in March 2025 [1] and the current CTO is Dane Knecht (dknecht here). What advantage does decoupling Cloudflare Containers from Cloudflare Workers have?
[1] https://blog.cloudflare.com/three-chapters-at-cloudflare-pro...
by jgrahamc - I know no one is writing copy anymore but i wish they tried to edit it a bit so it wasn’t so glaringly obvious. It just sours the product when it seems like so little effort was put into the message. And it’s not even hard - just change the prompt used!by conception
- 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 Cloudflare account,” and “Cloudflare applies additional abuse prevention checks to temporary preview accounts.”[1] This is a bit vague though. Creating a new account has never been a huge hurdle to overcome but this seems to reduce the barrier to entry even more.
[1] https://developers.cloudflare.com/workers/platform/claim-dep...
by derektank - > Would love to know more about how Cloudflare plans to prevent abuse of ephemeral infrastructure to host malicious content
If it helps laugh DDoS attacks they would be incentivized to do the exact opposite. They can charge more for “protection” then.
by rdtsc - Given how little they do now to stop malicious content hosted behind/by Cloudflare, the bare minimum if anything.by gwittel
- Hot damn...
> Any agent can now run wrangler deploy --temporary and deploy a Worker to Cloudflare. This temporary deployment stays live for 60 minutes, during which time you can claim the temporary account, making it permanently your own. If you don't, it expires on its own.
Forget about agents, Cloudflare just provided free scratch deployments - ephemeral for 60 minutes - for anyone.
This is going to be amazing for things like PR previews and code review. Being able to deploy a preview to a working URL for free is a huge reduction in friction.
I hope it doesn't get abused so much that they turn it off again.
by simonw - > This is going to be amazing for things like PR previews and code review. Being able to deploy a preview to a working URL for free is a huge reduction in friction.
Uh that's already true?
by dbbk - Obnoxious reply but I did this myself so I'm compelled to post it: review apps aren't that hard to implement yourself. You just need a VPS, domain name, and Caddy. Then tell any agent to connect the dots.by resonious
- Cloudflare Workers already support preview urls, and if you set up Github integration they are done automatically
- This is gonna be amazing for phishing, like most of the features Cloudflare offers (free Turnstile for fresh accounts, CF tunnels, pages.dev, r2.dev).by heipei
- Wasn’t this case pretty much before?
The limits are 100 workers on free and 500 on paid.
And if need more then you can always go their platform which supports tenancy.
As long as you have a cronjob or similar to clean up the cost of having per PR preview is pretty much zero.
by aleksiy123 - I just tried this out:
I'm amused that it made me accept the terms and conditions without any indication of who I am, but it did work - https://cloudflare-redirect-resolver.educated-celery.workers... will be live for the next 59 minutes.% npx wrangler deploy --temporary wrangler 4.103.0 ──────────────────── You must accept Cloudflare's Terms of Service (https://www.cloudflare.com/terms/) and Privacy Policy (https://www.cloudflare.com/privacypolicy/) in order to continue. By typing "yes", you agree to these terms. Type "yes" to continue. … yes Solving proof-of-work challenge… Temporary account ready: Account: Educated Celery (created) Claim within: 60 minutes Claim URL: https://dash.cloudflare.com/claim-preview?claimToken=CAVe7LzWiGad-redacted Total Upload: 13.79 KiB / gzip: 4.12 KiB Uploaded cloudflare-redirect-resolver (2.27 sec) Deployed cloudflare-redirect-resolver triggers (0.50 sec) https://cloudflare-redirect-resolver.educated-celery.workers.dev Current Version ID: 5c12da7f-2749-4ccc-a8f6-79b85da98d10by simonw - Looks like Cloudflare still haven't shipped the most valuable possible feature for Cloudflare Workers though: hard billing caps.
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/#...
by simonw - This smells like a cottage industry similar to detecting soon to be expired ssl certs.
"Oh that thing that was an experiment and had billing caps turned on but we rushed in to production and now the whole business relies on that thing is in an outage and destroying customer trust we've barely earned yet"
I get the flip side but... 2nd order effects oof.
by yanslookup - To be honest their service is so cheap, that it's extremely unlikely to get such an attack without costing the attacker an equally equivalent amount.
Also, if it's really a problem or you are estimating it'll certainly be a problem, do email alerts or a strict shutdown if xx requests are hitting your account. You can have a simple counter in a KV.
by csomar - If it weren't implemented by cloudflare natively, would you be ok using a library or something that wraps or hooks onto your IaC to wrap entry points with a worker (proxy or circuit-breaker, conceptually) with various types of limits (real-time estimated spend, or just counts of operations, or just a on/off switch wired to an email alert). I'm pulling a few of these threads at the moment since I've been ramping up my cloudflare usage.by devdoshi
- tbh this is my biggest anxiety with cloudflare and this seems intentional
also its funny that i have a backup to cloudflare in case it goes down—that seems to be a regular event now as of lately with CF
by zuzululu