Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Temporary Cloudflare accounts for AI agents

blog.cloudflare.com

Post reply on HN
Print view View original

51–60 of 173 posts

Re: Temporary Cloudflare accounts for AI agents

#51

Post by tough »

aleksiy123 wrote: post #33
simonw wrote: post #24

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…

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.

unless you have 500 PR's a day =)

On the other hand, we already use regular CF builds for frontend previews, but that doesnt solve a fullstack PR preview much

Re: Temporary Cloudflare accounts for AI agents

#52

Post by tough »

tailscaler2026 wrote: post #38
htrp wrote: post #26

Earlier quoted context omitted.

quick piece of feedback, the workers architecture is a little bit annoying when converting from Lambda but hooking up to cloudflare MCP solves 90% of the issues

there's absolutely nothing positive we want to encourage copying from AWS's architectural approach to anything.

chuckles

Re: Temporary Cloudflare accounts for AI agents

#53

Post by mahirsaid »

This falls Within my predictions of how the AI playing field is become more leveled, in terms with human digital activity. Soon it wouldn't be so what you can do with the computer but what the agent can do BETTER. We are already there for the most part. These are the early steps of full re-genitive self hosting, fully capable AI the is far more advanced then asking it to solve a 2 + 2 question.

The article worded it perfectly; friction-less "efforts"

Re: Temporary Cloudflare accounts for AI agents

#54

Post by georgemcbay »

Denzel wrote: post #44
deadbabe wrote: post #37

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.

> About half of US households don’t have any retirement at all.

...and the top 10% by wealth own 90% of the stock market.

So even among the half that do have retirement savings in 401ks and the like it is on average very little compared to how much the truly wealthy have invested.

Re: Temporary Cloudflare accounts for AI agents

#55

Post by sofixa »

simonw wrote: post #47

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://develo…

Never going to happen at such a platform.

They prefer waiving the occasional DDoS / misconfiguration over giving their customers to cause outages with something so trivially forgotten about and so disconnected from the tech and actual platform.

Re: Temporary Cloudflare accounts for AI agents

#56

Post by sofixa »

unix1 wrote: post #45
anilgulecha wrote: post #2

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…

> 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 o…

Not the OP, but for me it's a simple matter of not wanting to use typescript and the whole swamp on fire that is NPM.

Re: Temporary Cloudflare accounts for AI agents

#57

Post by piterrro »

kentonv wrote: post #46
piterrro wrote: post #41

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…

> it only makes sense to deploy small things there What makes you say that?

I’m running entire leadjobs.dev on cloudflare workers and its kind of unreliable for the traffic it gets - around 100 visitors/day. There are some weird errors in d1 from time to time which i cannot debug since its all black box. Also latencies are greater than I would expect, especially, again for d1. Overall its great value for money to get a globally available, low latency service - but I would think twice before going all in. As a sidenote, I expected that, thus the architecture of the service is build in a way that it abstracts the cf runtime and I can switch to any other infra, be it dedicated or another cloud, in a matter of a day

Re: Temporary Cloudflare accounts for AI agents

#58

Post by piterrro »

simonw wrote: post #48
piterrro wrote: post #41

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…

> Unless the agent creates something for cf workers from scratch 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

I didnt say LLMs dont know cf workers, I meant that the cf workers runtime is kind of unique and you cannot push there any code without making it cf workers ready in the first place. If you know what youre doing it should be one time step to connect your hono app to cf workers (so not a huge effort) but still its not like tou can run anything there

Re: Temporary Cloudflare accounts for AI agents

#59

Post by theplumber »

Denzel wrote: post #44
deadbabe wrote: post #37

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.

This sounds like Elon’s IPO…I give you 0.000000000009% of my company for your whole savings account. Now have a part of the pie!

Re: Temporary Cloudflare accounts for AI agents

#60

Post by IncreasePosts »

Hackbraten wrote: post #15

Cloudflare: let's give the bots their own accounts so they can scrape harder. Also Cloudflare: let's send normal humans who are trying to go about their daily lives into endless Turnstile spinner loops with absolutely zero recourse, grievance, or support infrastructure.

I'm sure they don't want humans to have that experience - the issue is that the human behavior looks very bot-like. This is usually only experienced by people whose setup is peculiar
Post reply on HN