ness VS workers.cloudflare.com

Yeah there are a bunch of selfhostable things:

Caprover (https://caprover.com/)

Dokku (https://github.com/dokku/dokku)

But people still choose Netlify and Vercel for ease of use I think.

Maybe we need something that's just Netlify. The closest I've seen to the "right" UX is Ness:

https://ness.sh

Use AWS Amplify or https://ness.sh

I think you mean something human-friendly on the marketing page, but if you are comfortable with Cloudformation YAML templates, you can find all the resources here: https://github.com/nessjs/ness/tree/main/static/stacks

Next, I plan to add preview environments for new pull requests on GitHub through an official GitHub Action. I'd love to hear if others are finding this tool useful and what features they'd like to see moving forward. Find me on Twitter and/or GitHub (pull requests are welcome!).

Finding the Right Fit: I used Cloudflare Workers for the Nuxt frontend application. It is simple to use and has a generous free tier. Cloudflare also acts as your DNS manager, and offers performance optimizations and DDOS protection for free! This seems like a smart strategy on their part – support smaller projects with potential to grow, and they get word of mouth recommendations, case and point, I’m mentioning their services in this video!

Server functions may encounter performance issues due to Lambda cold starts, impacting user response time. Some providers have minimal delays (like Cloudflare Workers due to V8 engine), while others require additional steps. For instance, one way to mitigate this is by periodically invoking the server function, although this would require investigation and potential costs.

I believe you can replace most cases (static sites) with Cloudflare Workers [1].

[1] https://workers.cloudflare.com/

Cloudflare has a serverless compute platform called Workers. Workers are automatically replicated across all Cloudflare data centers, meaning that the developer can make an API or other application that automatically scales with zero infrastructure! Workers also automatically routes user requests to their nearest data center, meaning that latency is reduced significantly!

Cloudflare Workers are Cloudflare’s answer to AWS Lambda. They let you deploy serverless code instantly across the globe and are blazing fast. You write code and deploy it to cloud environments without the need for traditional infrastructure.

Cloudflare Workers

This article guides you on how to build a remote function for Slack's automation platform on Cloudflare Workers. The slack-cloudflare-workers library provides the toolset for swiftly creating such an app in TypeScript.

Both of these OSS options were designed for the Edge architecture based on Cloudflare Workers, but unfortunately, they no longer seem to be maintained.

Can't you stop endpoint execution with other tools, like CF workers/ Imperva and so on, on the CDN layer?