9 ms·

Temporary Cloudflare accounts for AI agents

249 points by farhadhf 3mo ago

hottrends 3mo ago
[flagged]
anilgulecha 3mo ago
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)
- ndjdjxixjenej 3mo ago
  [dead]
- yodon 3mo ago
  >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.
- jgrahamc 3mo ago
  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-programmer-to-cto-to-board-of-directors/ https://blog.cloudflare.com/three-chapters-at-cloudflare-pro...
  - htrp 3mo ago
    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
    - tailscaler2026 3mo ago
      there's absolutely nothing positive we want to encourage copying from AWS's architectural approach to anything.
      - tough 3mo ago
        chuckles
  - CuriouslyC 3mo ago
    Not sure if it's the only blocker, but I wanted to use containers with UDP/SRT.
  - eek2121 3mo ago
    I'm pretty sure I heard your groan from all the way over here in Nashville. ;)
  - david_shi 3mo ago
    Speaking from personal experience, I already know exactly what I’m getting with containers. Same with Postgres.
  - anilgulecha 3mo ago
    No per-request billing, portable devops - easier multicloud, known semantics (env variables, entrypoint, websocket lifecycle).
- unix1 3mo ago
  > 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-details/workers-connections/ https://developers.cloudflare.com/containers/platform-detail...
  - sofixa 3mo ago
    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.
- csomar 3mo ago
  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.
soared 3mo ago
I’m going to need a wrapper for all these services offering this service.
conception 3mo ago
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!
- ndjdjxixjenej 3mo ago
  [dead]
chinallm_ai 3mo ago
[dead]
variety8675 3mo ago
posted yesterday as well: https://news.ycombinator.com/item?id=48598906 https://news.ycombinator.com/item?id=48598906
aniviacat 3mo ago
Wouldn't it make more sense to merge the temporary account into an existing one, instead of claiming it as a new account? This could lead to people having a large amount of separate accounts.
- kylecazar 3mo ago
  I assumed that's how it works if you sign in before claiming the account? It says to claim you can either sign up or sign in.
derektank 3mo ago
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-deployments/ https://developers.cloudflare.com/workers/platform/claim-dep...
- rdtsc 3mo ago
  > 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.
  - TeMPOraL 3mo ago
    DDoS is one thing you wouldn't be launching from Cloudflare, but if they can get enough types of other bot traffic (whether malicious or "legitimate" or just general grey zone) to use them as the starting point, it improves their error rates when dealing with bot traffic that didn't migrate.
    - inigyou 3mo ago
      Cloudflare knowingly protects DDoS services' payment systems.
- gwittel 3mo ago
  Given how little they do now to stop malicious content hosted behind/by Cloudflare, the bare minimum if anything.
827a 3mo ago
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.
- quinncom 3mo ago
  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.
  - 827a 3mo ago
    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-all/ https://blog.cloudflare.com/enterprise-grade-features-for-al...
- frogperson 3mo ago
  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.
- weird-eye-issue 3mo ago
  Oh actually it's worse now, they blocked email addresses with + in them!
Hackbraten 3mo ago
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.
- jwr 3mo ago
  I had similar thoughts: "let's convince everyone to outsource the decision on who can access their websites to us, because BOTS BOTS BOTS" and "let's make life easier for bots to do things".
- moritzruth 3mo ago
  First you spread the disease, then you sell the cure.
  - deadbabe 3mo ago
    I think this is more of a “keep friends close but enemies closer” type thing.
    - throw1234567891 3mo ago
      Sounds more like “let’s make money twice”.
    - TeMPOraL 3mo ago
      It's business so they have neither enemies nor friends, just various breeds of cattle to milk.
- isodev 3mo ago
  But think of the shareholders
  - deadbabe 3mo ago
    Anyone can be a shareholder.
truvem 3mo ago
[flagged]
jsyang00 3mo ago
> 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/ https://snail-game.solstice-barometer.workers.dev/ pretty cool.
simonw 3mo ago
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.
- simonw 3mo ago
  I just tried this out: % 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-79b85da98d10 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.dev https://cloudflare-redirect-resolver.educated-celery.workers... will be live for the next 59 minutes.
  - winterqt 3mo ago
    Interesting, it’s still live!
    - usef- 3mo ago
      Maybe someone else claimed it?
    - johanyc 3mo ago
aplomb1026 3mo ago
[flagged]
piterrro 3mo ago
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…
- kentonv 3mo ago
  > it only makes sense to deploy small things there What makes you say that?
  - piterrro 3mo ago
    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
    - kentonv 3mo ago
      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 your code to run on the same machine as the database itself. Your queries run on a local file, synchronously, rather than going over a network. There is essentially zero latency when using sqlite storage in a Durable Object. If your app does no more than one DB query per request, then D1 is fine: the Worker runs near the end user, and talks over the long-haul network to D1 just once. Whereas with Durable Objects, your Worker would talk over the long-haul network to the Durable Object. No difference. But if your app ever does two or more queries in series for a single request, then Durable Objects becomes vastly better, because you get to move that query-chaining code to happen directly where the database lives, rather than have multiple round trips. Really, though, the only reason D1 exists is for comfort. Once you know how to use Durable Objects, there's no reason to use D1. We offer D1 because a lot of people don't want to learn a new model. (Which is fair. People are busy and may have better things to do.) One caveat: D1's read replica support still isn't exposed in a way that you can use it in raw Durable Objects, so if you are using that, it's a legitimate advantage to D1. But we do plan to bring this functionality to raw Durable Objects at some point.
simonw 3mo ago
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/#workers https://developers.cloudflare.com/workers/platform/pricing/#...
- sofixa 3mo ago
  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.
- Zababa 3mo ago
  Yeah, especially with agents this seems necessary.
- cj 3mo ago
  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 does drive me crazy that their enterprise tier “caps” bandwidth. Our company overaged on one of our domains, so we moved the domain out of our enterprise license onto a self-serve plan, and like magic, back to unlimited bandwidth.
  - iancarroll 3mo ago
    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.
mahirsaid 3mo ago
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"
KaiShips 3mo ago
[flagged]
deleted 3mo ago
[deleted]
balgaly 3mo ago
[flagged]
jackbucks 3mo ago
Excuse me for asking, doesnt this make it easier to run a malware bot farm and disappear without a trace?
dools 3mo ago
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.
deleted 3mo ago
[deleted]
jessinra98 3mo ago
[dead]
siriuslv 3mo ago
[flagged]
taosu_la 3mo ago
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.
FergusArgyll 3mo ago
https://codex-cloudflare-skill-site.aspiring-sheep.workers.dev/ https://codex-cloudflare-skill-site.aspiring-sheep.workers.d...
GreyOcten 3mo ago
[flagged]
dixit_algorismi 3mo ago
[flagged]

249 points by farhadhf 3mo ago

[flagged]

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)

ndjdjxixjenej 3mo ago
[dead]
yodon 3mo ago
>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.
jgrahamc 3mo ago
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-programmer-to-cto-to-board-of-directors/ https://blog.cloudflare.com/three-chapters-at-cloudflare-pro...
- htrp 3mo ago
  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
  - tailscaler2026 3mo ago
    there's absolutely nothing positive we want to encourage copying from AWS's architectural approach to anything.
    - tough 3mo ago
      chuckles
- CuriouslyC 3mo ago
  Not sure if it's the only blocker, but I wanted to use containers with UDP/SRT.
- eek2121 3mo ago
  I'm pretty sure I heard your groan from all the way over here in Nashville. ;)
- david_shi 3mo ago
  Speaking from personal experience, I already know exactly what I’m getting with containers. Same with Postgres.
- anilgulecha 3mo ago
  No per-request billing, portable devops - easier multicloud, known semantics (env variables, entrypoint, websocket lifecycle).
unix1 3mo ago
> 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-details/workers-connections/ https://developers.cloudflare.com/containers/platform-detail...
- sofixa 3mo ago
  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.
csomar 3mo ago
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.

soared 3mo ago

I’m going to need a wrapper for all these services offering this service.

conception 3mo ago

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!

ndjdjxixjenej 3mo ago
[dead]

chinallm_ai 3mo ago

[dead]

variety8675 3mo ago

posted yesterday as well: https://news.ycombinator.com/item?id=48598906 https://news.ycombinator.com/item?id=48598906

aniviacat 3mo ago

Wouldn't it make more sense to merge the temporary account into an existing one, instead of claiming it as a new account? This could lead to people having a large amount of separate accounts.

kylecazar 3mo ago
I assumed that's how it works if you sign in before claiming the account? It says to claim you can either sign up or sign in.

derektank 3mo ago

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-deployments/ https://developers.cloudflare.com/workers/platform/claim-dep...

rdtsc 3mo ago
> 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.
- TeMPOraL 3mo ago
  DDoS is one thing you wouldn't be launching from Cloudflare, but if they can get enough types of other bot traffic (whether malicious or "legitimate" or just general grey zone) to use them as the starting point, it improves their error rates when dealing with bot traffic that didn't migrate.
  - inigyou 3mo ago
    Cloudflare knowingly protects DDoS services' payment systems.
gwittel 3mo ago
Given how little they do now to stop malicious content hosted behind/by Cloudflare, the bare minimum if anything.

827a 3mo ago

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.

quinncom 3mo ago
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.
- 827a 3mo ago
  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-all/ https://blog.cloudflare.com/enterprise-grade-features-for-al...
frogperson 3mo ago
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.
weird-eye-issue 3mo ago
Oh actually it's worse now, they blocked email addresses with + in them!

Hackbraten 3mo ago

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.

jwr 3mo ago
I had similar thoughts: "let's convince everyone to outsource the decision on who can access their websites to us, because BOTS BOTS BOTS" and "let's make life easier for bots to do things".
moritzruth 3mo ago
First you spread the disease, then you sell the cure.
- deadbabe 3mo ago
  I think this is more of a “keep friends close but enemies closer” type thing.
  - throw1234567891 3mo ago
    Sounds more like “let’s make money twice”.
  - TeMPOraL 3mo ago
    It's business so they have neither enemies nor friends, just various breeds of cattle to milk.
isodev 3mo ago
But think of the shareholders
- deadbabe 3mo ago
  Anyone can be a shareholder.

truvem 3mo ago

[flagged]

jsyang00 3mo ago

> 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/ https://snail-game.solstice-barometer.workers.dev/ pretty cool.

simonw 3mo ago

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.

simonw 3mo ago
I just tried this out: % 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-79b85da98d10 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.dev https://cloudflare-redirect-resolver.educated-celery.workers... will be live for the next 59 minutes.
- winterqt 3mo ago
  Interesting, it’s still live!
  - usef- 3mo ago
    Maybe someone else claimed it?
  - johanyc 3mo ago

aplomb1026 3mo ago

[flagged]

piterrro 3mo ago

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…

kentonv 3mo ago
> it only makes sense to deploy small things there What makes you say that?
- piterrro 3mo ago
  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
  - kentonv 3mo ago
    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 your code to run on the same machine as the database itself. Your queries run on a local file, synchronously, rather than going over a network. There is essentially zero latency when using sqlite storage in a Durable Object. If your app does no more than one DB query per request, then D1 is fine: the Worker runs near the end user, and talks over the long-haul network to D1 just once. Whereas with Durable Objects, your Worker would talk over the long-haul network to the Durable Object. No difference. But if your app ever does two or more queries in series for a single request, then Durable Objects becomes vastly better, because you get to move that query-chaining code to happen directly where the database lives, rather than have multiple round trips. Really, though, the only reason D1 exists is for comfort. Once you know how to use Durable Objects, there's no reason to use D1. We offer D1 because a lot of people don't want to learn a new model. (Which is fair. People are busy and may have better things to do.) One caveat: D1's read replica support still isn't exposed in a way that you can use it in raw Durable Objects, so if you are using that, it's a legitimate advantage to D1. But we do plan to bring this functionality to raw Durable Objects at some point.

simonw 3mo ago

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/#workers https://developers.cloudflare.com/workers/platform/pricing/#...

sofixa 3mo ago
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.
Zababa 3mo ago
Yeah, especially with agents this seems necessary.
cj 3mo ago
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 does drive me crazy that their enterprise tier “caps” bandwidth. Our company overaged on one of our domains, so we moved the domain out of our enterprise license onto a self-serve plan, and like magic, back to unlimited bandwidth.
- iancarroll 3mo ago
  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.

mahirsaid 3mo ago

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"

KaiShips 3mo ago

[flagged]

deleted 3mo ago

[deleted]

balgaly 3mo ago

[flagged]

jackbucks 3mo ago

Excuse me for asking, doesnt this make it easier to run a malware bot farm and disappear without a trace?

dools 3mo ago

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.

deleted 3mo ago

[deleted]

jessinra98 3mo ago

[dead]

siriuslv 3mo ago

[flagged]

taosu_la 3mo ago

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.

FergusArgyll 3mo ago

https://codex-cloudflare-skill-site.aspiring-sheep.workers.dev/ https://codex-cloudflare-skill-site.aspiring-sheep.workers.d...

GreyOcten 3mo ago

[flagged]

dixit_algorismi 3mo ago

[flagged]