Caddy

caddyserver.com ↗

Serve sites and reverse-proxy traffic with a configurable web server that automates HTTPS for public domains.

SI Score
75/100
Pricing
Open Source AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about Caddy

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Caddy homepage

What it does

Caddy is an extensible web server with a text-based Caddyfile configuration and modules for tasks such as serving static files or proxying requests. Its quick-start guide begins with a local address, while automatic HTTPS is designed for eligible public hostnames. The server is Apache 2.0 licensed, and its repository separates the open-source project from related commercial services and support.

Serve a local page before changing DNS

The Caddyfile quick-start begins with a plain-text file whose site address is localhost. That is a useful first test for learning the configuration format; the file_server directive can then serve a static directory, while reverse_proxy is available when requests should go to an application process. When moving from local use to a public hostname, Caddy can manage HTTPS certificates automatically when the domain and network setup meet its requirements. The quick-start notes that binding the standard HTTP and HTTPS ports may need elevated privileges on some operating systems; choosing higher ports is another local option. This is a web server to configure and operate, not a hosting provider that supplies the application runtime or DNS. The Caddy repository publishes Apache License 2.0. The product site also links to a store and commercial services, so this record describes the open-source server and its documentation rather than assigning a price to every Caddy-related offer.

Strengths

  • A readable Caddyfile provides a compact way to describe local sites and server behavior.
  • The same server can serve static files or proxy requests to an application.
  • Automatic HTTPS can reduce certificate-management work for eligible public sites.

Watch out for

  • Public HTTPS depends on suitable domain and network configuration, and local binding to standard ports can require elevated privileges.
  • Caddy is server software; operators still provide hosting, application processes, and DNS where needed.

Best for

  • Developers serving static content or reverse-proxying a local application.
  • Operators who want a text-configured web server with automatic certificate management for public sites.
  • Teams comfortable managing a web server rather than buying a managed application-hosting platform.

Sources