[opensourcedex]

caddy is a free, open source networking & connectivity project written in Go and released under Apache-2.0. It has 78,660 GitHub stars, 5,232 forks and 286 open issues, and was last pushed 22 hours ago. On this registry it ranks #2 of 83 tracked projects in Networking & Connectivity, with 5 head-to-head comparisons available. It gained 2,470 stars over the last 30 tracked days.

What is caddy?

Caddy is a Go-based, Apache-2.0 licensed HTTP/1.1, HTTP/2, and HTTP/3 web server and reverse proxy that obtains and renews TLS certificates automatically by default, built for operators and teams who want every site on HTTPS without maintaining a separate certificate workflow.

What it is

Caddy is an extensible server platform written in Go, living in the Infrastructure & Operations / Networking & Connectivity space of this registry. It serves HTTP traffic and terminates TLS by default rather than as an opt-in step, and it presents a single static binary with no external dependencies, not even libc. Configuration can be written in the Caddyfile for readability or in the native JSON config format for full control, and a JSON API allows configuration to change dynamically. Caddy is developed in the open on GitHub under Apache-2.0, with the project homepage and full documentation hosted at caddyserver.com.

The concrete problem it solves is certificate management. A conventional deployment pairs an HTTP server with a separate ACME client and a renewal schedule, and a lapse in that schedule takes the site down. Caddy provisions certificates for public names through ZeroSSL and Let's Encrypt, runs a fully managed local CA for internal names and IP addresses, and supports multi-issuer fallback. It also keeps serving when other servers would fail due to TLS, OCSP, or certificate-related issues, which is the specific failure mode it removes from the operator's plate.

Key capabilities

  • Easy configuration through the Caddyfile, with config adapters available for operators who do not want to write JSON directly.
  • Powerful configuration through the native JSON config, plus dynamic configuration through the JSON API.
  • Automatic HTTPS by default, using ZeroSSL and Let's Encrypt for public names and a fully managed local CA for internal names and IPs.
  • Encrypted ClientHello (ECH) support and multi-issuer fallback.
  • HTTP/1.1, HTTP/2, and HTTP/3 all supported by default.
  • Coordination with other Caddy instances in a cluster.
  • A modular architecture extensible through plugins, with the xcaddy builder tool producing custom builds.

Who uses it and how

  • Large sites: the project reports scaling to hundreds of thousands of sites in production, having served trillions of requests and managed millions of TLS certificates.
  • Reverse proxy deployments, one of the project's declared topics, where Caddy fronts backend services.
  • Internal service meshes that need trusted certificates for internal names and IP addresses without public DNS, using the local CA.
  • Clustered deployments where multiple Caddy instances coordinate certificate issuance and renewal.
  • Minimal container and bare-metal environments, since the binary needs no external dependencies, not even libc.

Getting started

The simplest cross-platform route is to download Caddy from GitHub Releases and place the executable file in your PATH; other install instructions live at caddyserver.com/docs/install. Custom builds with plugins use xcaddy build, and source builds require Go 1.25.0 or newer.

How it compares

No competing product is named in the facts for this entry, so Caddy stands alone in this registry on the axes available. Any comparison against commercial load balancers, CDNs, or managed certificate services would have to be made from outside this listing.

When to use it — and when not to

A self-hoster runs the binary directly and must grant it permission to bind low ports, for example sudo setcap cap_net_bind_service=+ep ./caddy on Linux; building from source adds a Go 1.25.0+ toolchain requirement. The project carries 286 open issues, and the README is largely a feature list and build guide rather than a deployment manual, so operators wanting hand-holding or a managed control plane should look elsewhere. Teams that want someone else to run and upgrade the server are not the intended audience.

project readme (upstream, from github) — read inline

Caddy

</a>

a project

Every site on HTTPS

Caddy is an extensible server platform that uses TLS by default.

Releases · Documentation · Get Help

      @caddyserver on Twitter   Caddy Forum
Caddy on Sourcegraph   Cloudsmith

Powered by
CertMagic

</a>

Special thanks to:
Warp sponsorship

Warp, built for coding with multiple AI agents

Available for MacOS, Linux, & Windows

Menu

Features

  • Easy configuration with the Caddyfile
  • Powerful configuration with its native JSON config
  • Dynamic configuration with the JSON API
  • Config adapters if you don't like JSON
  • Automatic HTTPS by default
    • ZeroSSL and Let's Encrypt for public names
    • Fully-managed local CA for internal names & IPs
    • Can coordinate with other Caddy instances in a cluster
    • Multi-issuer fallback
    • Encrypted ClientHello (ECH) support
  • Stays up when other servers go down due to TLS/OCSP/certificate-related issues
  • Production-ready after serving trillions of requests and managing millions of TLS certificates
  • Scales to hundreds of thousands of sites as proven in production
  • HTTP/1.1, HTTP/2, and HTTP/3 all supported by default
  • Highly extensible modular architecture lets Caddy do anything without bloat
  • Runs anywhere with no external dependencies (not even libc)
  • Written in Go, a language with higher memory safety guarantees than other servers
  • Actually fun to use
  • So much more to discover

Install

The simplest, cross-platform way to get started is to download Caddy from GitHub Releases and place the executable file in your PATH.

See our online documentation for other install instructions.

Build from source

Requirements:

For development

Note: These steps will not embed proper version information. For that, please follow the instructions in the next section.

$ git clone "https://github.com/caddyserver/caddy.git"
$ cd caddy/cmd/caddy/
$ go build

When you run Caddy, it may try to bind to low ports unless otherwise specified in your config. If your OS requires elevated privileges for this, you will need to give your new binary permission to do so. On Linux, this can be done easily with: sudo setcap cap_net_bind_service=+ep ./caddy

If you prefer to use go run which only creates temporary binaries, you can still do this with the included setcap.sh like so:

$ go run -exec ./setcap.sh main.go

If you don't want to type your password for setcap, use sudo visudo to edit your sudoers file and allow your user account to run that command without a password, for example:

username ALL=(ALL:ALL) NOPASSWD: /usr/sbin/setcap

replacing username with your actual username. Please be careful and only do this if you know what you are doing! We are only qualified to document how to use Caddy, not Go tooling or your computer, and we are providing these instructions for convenience only; please learn how to use your own computer at your own risk and make any needful adjustments.

Then you can run the tests in all modules or a specific one:

$ go test ./...
$ go test ./modules/caddyhttp/tracing/

With version information and/or plugins

Using our builder tool, xcaddy...

$ xcaddy build

...the following steps are automated:

  1. Create a new folder: mkdir caddy
  2. Change into it: cd caddy
  3. Copy Caddy's main.go into the empty folder. Add imports for any custom plugins you want to add.
  4. Initialize a Go module: go mod init caddy
  5. (Optional) Pin Caddy version: go get github.com/caddyserver/caddy/v2@version replacing version with a git tag, commit, or branch name.
  6. (Optional) Add plugins by adding their import: _ "import/path/here"
  7. Compile: go build -tags=nobadger,nomysql,nopgx

Quick start

The Caddy website has documentation that includes tutorials, quick-start guides, reference, and more.

We recommend that all users -- regardless of experience level -- do our Getting Started guide to become familiar with using Caddy.

If you've only got a minute, the website has several quick-start tutorials to choose from! However, after finishing a quick-start tutorial, please read more documentation to understand how the software works. 🙂

Overview

Caddy is most often used as an HTTPS server, but it is suitable for any long-running Go program. First and foremost, it is a platform to run Go applications. Caddy "apps" are just Go programs that are implemented as Caddy modules. Two apps -- tls and http -- ship standard with Caddy.

Caddy apps instantly benefit from automated documentation, graceful on-line config changes via API, and unification with other Caddy apps.

Although JSON is Caddy's native config language, Caddy can accept input from config adapters which can essentially convert any config format of your choice into JSON: Caddyfile, JSON 5, YAML, TOML, NGINX config, and more.

The primary way to configure Caddy is through its API, but if you prefer config files, the command-line interface supports those too.

Caddy exposes an unprecedented level of control compared to any web server in existence. In Caddy, you are usually setting the actual values of the initialized types in memory that power everything from your HTTP handlers and TLS handshakes to your storage medium. Caddy is also ridiculously extensible, with a powerful plugin system that makes vast improvements over other web servers.

To wield the power of this design, you need to know how the config document is structured. Please see our documentation site for details about Caddy's config structure.

Nearly all of Caddy's configuration is contained in a single config document, rather than being scattered across CLI flags and env variables and a configuration file as with other web servers. This makes managing your server config more straightforward and reduces hidden variables/factors.

Full documentation

Our website has complete documentation:

https://caddyserver.com/docs/

The docs are also open source. You can contribute to them here: https://github.com/caddyserver/website

Getting help

  • We advise companies using Caddy to secure a support contract through Ardan Labs before help is needed.

  • A sponsorship goes a long way! We can offer private help to sponsors. If Caddy is benefitting your company, please consider a sponsorship. This not only helps fund full-time work to ensure the longevity of the project, it provides your company the resources, support, and discounts you need; along with being a great look for your company to your customers and potential customers!

  • Individuals can exchange help for free on our community forum at https://caddy.community. Remember that people give help out of their spare time and good will. The best way to get help is to give it first!

Please use our issue tracker only for bug reports and feature requests, i.e. actionable development items (support questions will usually be referred to the forums).

About

Matthew Holt began developing Caddy in 2014 while studying computer science at Brigham Young University. (The name "Caddy" was chosen because this software helps with the tedious, mundane tasks of serving the Web, and is also a single place for multiple things to be organized together.) It soon became the first web server to use HTTPS automatically and by default, and now has hundreds of contributors and has served trillions of HTTPS requests.

The name "Caddy" is trademarked. The name of the software is "Caddy", not "Caddy Server" or "CaddyServer". Please call it "Caddy" or, if you wish to clarify, "the Caddy web server". Caddy is a registered trademark of Stack Holdings GmbH.

Caddy is a project of ZeroSSL, an HID Global company.

Debian package repository hosting is graciously provided by Cloudsmith. Cloudsmith is the only fully hosted, cloud-native, universal package management solution, that enables your organization to create, store and share packages in any format, to any place, with total confidence.

Frequently asked questions

Is caddy free to use?

caddy is open source under the Apache-2.0 licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does caddy do?

Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS

What is caddy written in?

caddy is primarily written in Go. Its source is publicly available at https://github.com/caddyserver/caddy, and it has 78,660 GitHub stars.