Except this feels different from what was promised at launch, before the radio silence for the last 9 months.

Except I can't get unlimited egress, because the product isn't available yet.

Egress isn't our price pain point anyway, as you may have guessed, it's request pricing. $4.50/million seems cheap, but when you're dealing with objects of 4-20KB that only exit our platform approximately once it doesn't end up being where the significant expense lies.

The blog posts in September all seemed intentionally vague on request pricing (which I and many others commented on in September) and no one from Cloudflare seemed willing to weigh in then.

I could also mention my disappointment with Durable Objects, especially as our primary use case for them was to be websockets (which also seems to be one of the biggest pitches the documentation makes for Durable Objects). But in no world does $12.50/million GB-s make sense per open connection (that's $1.56/month for a single continuous websocket connection by the way).

I even remember reading in a blog at some point (that seems to be missing now or so long ago that I can't find it anymore) that Cloudflare recognised that fact and planned to implement something that makes sense by the time Durable Objects came out of beta. But the product seems to be no longer in beta and the pricing page seems to be very specific, even having the gall to actually list a websocket example[1] on the pricing page. $409.72/month for 100 connections doing 1 message per month is not a figure I'd be shouting from the rooftops. This is literal orders of magnitude (over 100x) more expensive than alternate solutions. Heck, it's over 4x more expensive than the AWS Lambda + API Gateway equivalent if you want to compare serverless with serverless.

And as I'm sure you're aware, whilst Cloudflare have great deals for free & pro plans, as soon as you want to deliver anything that isn't really text-base at scale you need to move to the enterprise plans. The Cloudflare T&Cs basically prohibit anything that isn't HTML or from an API (see section 2.8)[2] And whilst I'll acknowledge these are less expensive than AWS, I'd hardly call these cheap. The last pricing I saw was $0.045/GB, but obviously, given it's not listed anywhere publicly on the Cloudflare website it's in the category of "if you need to ask…"

Ultimately my pain and frustration comes from loving so much of what Cloudflare is and some of the truly wonderful ways in which you and your team John, solve the technical challenges of being one of the largest CDNs on the net. But I'm disappointed that I don't get to use any of them. We're either priced out or we get excited that a new Cloudflare product is going to solve a pain point, but after waiting months for an announced product to become available, we're forced to move on or the released version doesn't deliver on the original promises.

Which brings to me to my primary point. I wish Cloudflare didn't announce products until they're actually (or very close to) available, and definitely with complete pricing with notes on quotas & limits.

Ignore my comments if you like, I had high hopes that R2 & Durable Objects would solve some of our issues. Unfortunately the small variance in price for R2 isn't going to justify re-engineering and moving our data not only to a different platform but to an entirely different organisation.

[1] https://developers.cloudflare.com/workers/platform/pricing/#...

[2] https://www.cloudflare.com/terms/