Quotes from the Cloudflare Q2 earnings call transcript:

We see more and more customers building applications around Cloudflare workers our compute platform. A high-profile new economy delivery company signed a $1.3 million three-year deal. They use a number of our products, but increasingly are building their application using Workers in order to get fast scalable performance. They appreciate the flexibility it provides, as they literally deliver for their geographically distributed customer base.

A financial services software provider signed a three-year $3.3 million deal for a number of our products. They're using Workers as a hyper programmable middleware to stitch together multiple vendor solutions. They love how easy it is for developers on their team to get up and running on the platform, because of the broad programming language support and rich developer tools that have been honed and battle tested in production since Workers launched nearly four years ago.

An Asian fintech provider expanded their use of Cloudflare by $0.5 million, making their annual spend now $1.3 million. They are using Workers to accelerate their development cycle and replace spend with some of the traditional hyperscale compute providers.

So, more than 50,000 developers wrote their first Workers script or code this time [this quarter]. And that's not signed up for an account. That's actually wrote code and deployed an application.

We're increasingly seeing startups that are building entire applications from scratch on the Workers platform.

I host static content with them (with no fallback server) using their keyval stores.

All GETs result in a KV lookup. A PUT uses a signed payload and a set of public keys in another KV store to check that the caller is allowed to store the new page contents.

I can re-deploy a site in a matter of milliseconds and it is only loosely cached (updates are reflected within a minute or so), free for up to 100k requests a month, and serves content in a matter of milliseconds.

I've used them for serving development or debug builds of JS SDKS (e.g. you set a DEBUG=TRUE cookie in the request in production, serve bundle A if not serve bundle B). Made the lives of our Solutions Engineers a LOT easier.

Being able to do this in the CDN infra was pretty powerful.

Built with Workers: https://workers.cloudflare.com/built-with

I have a somewhat unusual use case that Workers are perfect for: I want to collect analytics on a SaaS service that is a CNAME under my domain, but that I do not control.

I made a websocket game server with cloudflare workers and durable objects.

Built major parts of our adtech platform on it before, will build the next one completely with Workers.

I've thought it would be fun to try and implement something like patchbay[0] on workers.

[0]: https://patchbay.pub/

I've made a website builder based on KV and Workers, and it has been quite brilliant - especially because of the global geo.

I just mentioned it above and then saw your comment, but here is an example cf app:

https://github.com/eidam/cf-workers-status-page

A status page pinging from multiple regions.

https://crates.live runs on Cloudflare workers (and yep, using Rust)