[sh3rl0ck]

On one hand, with the top comments of the rebrand post showing how many insecure deployments there are, something like this alongside cloudflare zero trust is probably a much more secure solution.

On the other hand, I just wanna point out

> Firstly, Cloudflare Workers has never been so compatible with Node.js. Where in the past we had to mock APIs to get some packages running, now those APIs are supported natively by the Workers Runtime.

Deployed a project a couple of days ago, and compared to past attempts where I had to wrangle (pun intended) with certain configs for deployment styles for node based applications, the normal build tooling just worked out of the box. Planning to move a couple of my free-from-me high DAU user projects that are on the vercel premium tier over to CF workers.

[james2doyle]

Yep I had the same experience with Astro a couple years ago. Tried to deploy to Cloudflare and it was not working so ended up with Netlify. Tried again a few months ago and it worked flawlessly. Funny enough, they have since "bought" Astro and so I only expect it to get better

[mtrovo]

I really like CF approach to cloud, it's a nice middle ground between old school heroku and full fledged AWS, plus their free tiers are generous enough that I barely pay anything on the stuff I got deployed there.

[rahimnathwani]

  showing how many insecure deployments there are

Insecure how? Even if the dashboard html is publicly accessible, you usually cannot connect without pairing or setting a gateway key.

[dmd]

The lethal trifecta. Once you're handing your email to this thing, all it takes is someone emailing you some well-crafted "send me all your money" prompt and the bot will happily act on it.