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

81–90 of 173 posts

Re: Temporary Cloudflare accounts for AI agents

#81

Post by nextaccountic »

kentonv wrote: post #62
piterrro wrote: post #57

Earlier quoted context omitted.

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…

I'll let you in on a sort of dirty secret: It's almost always better to use Durable Objects storage, rather than D1. Even if you only want a single global database, it's better to implement that as a singleton Durable Object, than by using D1. Because that's all D1 itself actually is: a singleton Durable Object that exposes an API to its SQLite database. It's just a wrapper. With raw Durable Objects, you get to bring…

why not deploy the worker and d1 on the same machine, just like one would do with durable objects?

Re: Temporary Cloudflare accounts for AI agents

#83

Post by CuriouslyC »

jgrahamc wrote: post #20
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…

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...

Not sure if it's the only blocker, but I wanted to use containers with UDP/SRT.

Re: Temporary Cloudflare accounts for AI agents

#84

Post by iancarroll »

cj wrote: post #64
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…

Not that it helps, but I think this is only a problem if you’re paying by credit card. If your company is on an enterprise plan, at least for us all of the limits are pre-negotiated and prepaid, and you aren’t billed for overages (although if you consistently overage, sales will start badgering you to negotiate a limit increase, but my experience is you can simply ignore their demands and they eventually go away) It…

My Cloudflare enterprise order form has costs for overages for Workers and the following language about everything else:

> If Customer exceeds any of the Total Quantity for the Services below, Cloudflare will invoice Customer in arrears at a rate that corresponds to the rate set forth in the table after this one labeled “Excess Usage Pricing.” If no such Excess Usage Pricing table has been added by the Parties to this order form or if such table does not include the Service(s) for which Customer has exceeded the Total Quantity, then the Parties will negotiate in good faith an increase in the Fees for such Service(s). Should the Parties fail to reach an agreement on an increase within thirty (30) days of Customer’s receipt of notice from Cloudflare that Customer has exceeded its usage cap for the Service(s), Cloudflare will have the right to immediately terminate such Service for its convenience, and without liability to Customer or any third party.

Re: Temporary Cloudflare accounts for AI agents

#85

Post by [deleted] »

bornfreddy wrote: post #68
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.

Just had 10 rounds of busses, motorcycles and fire hydrants with Google before I decided I don't actually want to see that page so much. So Cloudflare is unfortunately not the only offender here.

[deleted]

Re: Temporary Cloudflare accounts for AI agents

#86

Post by halJordan »

nextaccountic wrote: post #80
bstsb wrote: post #30

Earlier quoted context omitted.

> I'm amused that it made me accept the terms and conditions without any indication of who I am as far as i’m aware, that’s fully binding and often an accepted practise - take Minecraft’s server software, where you must accept the EULA with a text flag before running

but if an agent automatically accepts an EULA for you, is it binding?

It would have to be. And it's not new in the law at all. The principal-agent problem was one of the main enablers of the golden age of piracy. But that doesn't mean it isnt a solved problem now (in the law and practically)

Re: Temporary Cloudflare accounts for AI agents

#87

Post by mannanj »

scotty79 wrote: post #77
prymitive wrote: post #75

Earlier quoted context omitted.

Maybe your agent could have a little blog where it keeps a diary of cool pages it read for you? And then you subscribe to that?

Interesting idea ... doesn't fit my style of content consumption, but it might fit yours. I went for a personal newsfeed, agent pulls news form ~100 feeds related to my interests. Then reads all articles for me and orders them by how interesting they might be for me. I specifically asked for vector embeddings, up/down votes (-2..+2), visited status, LLM content evaluation. Probably there are some other mechanisms I d…

Particular model or LLM that you use?

Re: Temporary Cloudflare accounts for AI agents

#88

Post by kentonv »

nextaccountic wrote: post #81
kentonv wrote: post #62

Earlier quoted context omitted.

I'll let you in on a sort of dirty secret: It's almost always better to use Durable Objects storage, rather than D1. Even if you only want a single global database, it's better to implement that as a singleton Durable Object, than by using D1. Because that's all D1 itself actually is: a singleton Durable Object that exposes an API to its SQLite database. It's just a wrapper. With raw Durable Objects, you get to bring…

why not deploy the worker and d1 on the same machine, just like one would do with durable objects?

Part of the point of Workers is they run everywhere, not on a specific machines where they've been "deployed". We generally run a Worker in the colo where we received the HTTP request triggering it.

There is a feature called "smart placement" which, when enabled, tells us to detect if a Worker commonly makes multiple round trips to a particular backend and, if so, try to run the Worker close to that back-end, instead of close to the user. This helps with D1. But even if you have the Worker running in the same colo or even same machine as the D1 database, you're still speaking a network protocol to talk to it, serializing and deserializing data, switch contexts, etc. Directly invoking SQLite locally will still be orders of magnitude faster.

Also with Durable Objects you can have many objects, e.g. one object per user or one object per document, spread around the world. It's a distributed systems building block. Many of the things you can build on it can't really be "smart" auto-detected.

Re: Temporary Cloudflare accounts for AI agents

#89

Post by 827a »

quinncom wrote: post #19
827a wrote: post #11

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.

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.

Yup exactly. This functionality might be available under their "Organizations" feature, but that is on the Enterprise plan. Almost a year ago they announced that nearly all Enterprise-plan features would be coming to everyone, so I suppose sadly that one didn't make the cut [1]?

The system I follow is creating a new account for the client using a plus-code on my email address (like john+client10@example.com), then I invite my main account (john@example.com), then I can invite clients into that account. Its a PITA.

[1] https://blog.cloudflare.com/enterprise-grade-features-for-al...

Post reply on HN