The shift toward Caddy 2.9 in web infrastructure

Automation and performance realities

Caddy 2.8 hit 142,000 requests per second on 16-core ARM hardware for 1KB static files, a 22% throughput advantage over the 116,000 requests per second recorded for Nginx 1.26 in the same April 2026 benchmark. This performance gap changes depending on the workload. For a Go upstream returning a 2KB JSON response, Nginx 1.30.0 sustained 88,000 requests per second while Caddy 2.11.2 reached 81,000. Nginx maintains a clear lead for files larger than 1 MB. It provides a 17% throughput advantage and uses 38% less memory during 1 GB+ streaming workloads. The shrinking window for public TLS certificates creates a pressing operational requirement for automation. The CA/Browser Forum approved Ballot SC-081v3 sets a schedule to reduce certificate validity to 47 days by March 2029. Caddy manages this process through built-in ACME support and automatic certificate renewal. Nginx released version 1.31.8 on October 21, 2026, and includes the ngx_http_json_module. Nginx also provides the ngx_http_acme_module for certificate management, which remains available for Nginx Open Source and NGINX Plus customers. The Caddy 2.9 beta release includes new features and changes that may be unstable.

Nginx handles high-concurrency workloads through an event-driven architecture with a small number of worker processes. This model uses minimal RAM and requires roughly 2.5 MB per 10,000 connections. In comparison, an idle Caddy server uses between 25 and 35 MB of RAM because it statically links its Go runtime and TLS stack. Caddy uses Go goroutines to handle concurrency across operating-system threads. Nginx has 47 CVEs since 2020, while Caddy has 4.

TLS termination tilts performance comparisons toward Caddy. With automatic HTTPS configured, Caddy added only 0.8 ms of p99 latency overhead. Nginx with manually configured certificates added 1.1 ms because of OCSP stapling stalls.

Configuration and architecture

Caddy uses a native JSON configuration format and provides a RESTful configuration API for dynamic changes. This allows for programmable changes through a control plane. Most users prefer the Caddyfile, which allows for production-ready sites in a few lines. Nginx uses a custom directive language in the nginx.conf file. Apache relies on a combination of httpd.conf and per-directory .htaccess files.

Caddy’s implementation in Go provides memory safety that C’s manual allocation lacks. Nginx’s binary size is typically under 1 MB, whereas Caddy’s binary is around 45 MB. If you are managing a cluster of multiple client sites, you likely already value consistent server configurations. Why would you introduce the risk of a migration? Nginx provides granular control over locations, rewriting, and buffering. Apache remains the standard for legacy PHP applications that depend on mod_php or .htaccess for URL rewriting. Apache uses different Multi-Processing Modules, including prefork, worker, or event. Caddy’s architecture is a single static binary with zero external dependencies.

Deployment logic for modern teams

Nginx holds a market share of roughly 31.8% as of late 2026, while Apache holds 23.2% and Caddy holds 0.2%. These numbers reflect decades of production hardening. Nginx is the preferred choice for high-traffic sites needing maximum performance and granular control. It is the tool for teams that require advanced caching and complex routing rules. F5 acquired Nginx Inc. in 2019 for $670 million. In 2024, core developer Maxim Dounin forked the project as freenginx to preserve open development.

Caddy is the best choice for small-to-medium sites, APIs, microservices, and internal tools. It is ideal for DevOps teams that need a fast setup with built-in SSL. Caddy reduces operational complexity by removing the need for separate tools like Certbot for certificate management. Caddy also handles HTTP/3 and Zstandard encoding by default.

Nginx was created in 2004 to solve the C10K problem. It remains a staple in enterprise applications and cloud environments. Caddy is a modern web server designed around automatic HTTPS. It is particularly attractive for new cloud applications because it simplifies the infrastructure. Caddy effectively combines several responsibilities including TLS termination and request proxying.

You should pick Nginx when you need raw large-file streaming throughput or proven enterprise tooling. You should pick Caddy when developer experience and automatic HTTPS matter more than squeezing performance from a CDN edge node. You should pick Apache for shared hosting environments or legacy applications.