At this point it seems like openresty is almost completely unsupported. The largest user that I was aware of was cloudflare and they've now abandoned it in favor of their home built Rust server.

Angie is also notable in that it's led by former Nginx core team members who left F5. Freenginx is another fork which is also led by one of the former core Nginx devs who became disillusioned with F5s leadership and wanted to make it fully open source, unlike Nginx and Angie which both have paywalled features. I'm not sure if any of the original team are still at F5 at this point, Igor Sysoev retired from working on Nginx (or its forks) altogether.

I'm more impressed these days with the pace, activity, and helpful support from the Caddy development team: https://github.com/caddyserver/caddy/

Envoy Proxy, to be more specific -- https://www.envoyproxy.io

The name “Envoy” conflicts with a company (envoy[.]com) that has nothing to do with proxies.

I like Envoy Proxy too. I have used it to support a couple of projects at Apple, and the gRPC Access Log Service works well -- https://www.envoyproxy.io/docs/envoy/latest/api-v3/extension... , although, I wish the configuration file was more obvious when you read it, I spend hours decyphering names, understanding the meeting of certain things, and tuning values that otherwise should be self explanatory. As Leon Bambrick said, naming things is hard, and some engineers tend to name things in a stupid way.

I looked into Envoy a few years ago and found it difficult to get started. I recall the syntax involving long names that were hard to look up from the docs.

I'm assuming some of those issues may be why it isnt as commonly talked about as nginx or caddy

It's not a reverse proxy cache though.