1) Nginx Plus and HAProxy have nice consoles to view your thousand upstreams and their current health. The Nginx Plus GUI is Apache 2.0 (https://github.com/ngin

1) Nginx Plus and HAProxy have nice consoles to view your thousand upstreams and their current health. The Nginx Plus GUI is Apache 2.0 (https://github.com/nginxinc/nginx-plus-dashboard https://github.com/nginxinc/nginx-plus-dashboard). 2) Nginx has this concept of rewrite "last" (instead of permanent or temporary) 3) Nginx Plus and HAProxy both have TCP routing OOTB without needing to recompile 4) Nginx and Nginx Plus have more ability to intercept a response from an upstream and modify it vs Caddy's fairly limited handle_response {} 5) Modify body content from upstream seems to require a Caddy module 6) Very difficult to find good Caddy configs and thus why LLMs have such a hard-time helping people with Caddy configs. Having a library of configs would probably help this training There seems to be an incredible market opportunity for Caddy as I've lost a lost of trust in the Nginx ecosystem and commercial environment. I would get some of these modules into core Caddy so that they are easy to distribute to people used to just installing via apt. And then attack the Nginx Plus features one by one. Add a visual console even though I understand why it doesn't seem like a necessity. I'd love to see Caddy take share and would love to re-allocate my Nginx Plus spend over to Caddy support.