Fast, multi-platform web server with automatic HTTPS 🔒
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
365cent 56af1ceb32
fileserver: browse: Better grid layout (#5564)
5 days ago
.github chore: Adjustments to CI caching (#5495) 2 months ago
caddyconfig caddyfile: Track import name instead of modifying filename (#5540) 2 weeks ago
caddytest caddyhttp: Implement named routes, `invoke` directive (#5107) 4 weeks ago
cmd cmd: Implement storage import/export (#5532) 1 week ago
internal/metrics move common metrics-related funcs to internal package 1 year ago
modules fileserver: browse: Better grid layout (#5564) 5 days ago
notify notify: Don't send ready after error (fix #5003) 9 months ago
.editorconfig chore: Clean up adapt test line endings (#4660) 1 year ago
.gitattributes chore: Add .gitattributes to force *.go to LF (#4919) 11 months ago
.gitignore fileserver: Fix file browser footer in grid mode (#5536) 3 weeks ago
.golangci.yml chore: remove deprecated linters (#5525) 1 month ago
.goreleaser.yml ci: add `--yes` to cosign arguments (#5440) 3 months ago
AUTHORS Add authors file 4 years ago
LICENSE Add license 4 years ago go.mod: Upgrade quic-go to v0.33.0 (Go 1.19 min) 4 months ago
admin.go Add doc comment about changing admin endpoint 1 month ago
admin_test.go httpcaddyfile: Fix `protocols` global option parsing (#5054) 9 months ago
caddy.go cmd: Strict unmarshal for validate (#5383) 4 months ago
caddy_test.go core: Add support for `d` duration unit (#3323) 3 years ago
context.go core: Return default logger if no modules loaded 2 months ago
context_test.go chore: Bump up to Go 1.19, minimum 1.18 (#4925) 10 months ago
duration_fuzz.go core: Windows service integration (#4790) 11 months ago
go.mod go.mod: Upgrade quic-go to 0.35.1 1 week ago
go.sum go.mod: Upgrade quic-go to 0.35.1 1 week ago
listen.go core: Eliminate unnecessary shutdown delay on Unix (#5413) 3 months ago
listen_unix.go core: Use SO_REUSEPORT_LB on FreeBSD (#5554) 3 weeks ago
listen_unix_setopt.go core: Use SO_REUSEPORT_LB on FreeBSD (#5554) 3 weeks ago
listen_unix_setopt_freebsd.go core: Use SO_REUSEPORT_LB on FreeBSD (#5554) 3 weeks ago
listeners.go update quic-go to v0.35.0 (#5560) 2 weeks ago
listeners_fuzz.go core: Windows service integration (#4790) 11 months ago
listeners_test.go acmeserver: Configurable `resolvers`, fix smallstep deprecations (#5500) 1 month ago
logging.go log: Make sink logs encodable (#5441) 2 months ago
metrics.go caddyhttp: Impl `ResponseWriter.Unwrap()`, prep for Go 1.20's `ResponseController` (#5509) 1 month ago
modules.go cmd: Strict unmarshal for validate (#5383) 4 months ago
modules_test.go Couple of minor fixes, update readme 3 years ago
replacer.go replacer: Add HTTP time format (#5458) 2 months ago
replacer_fuzz.go core: Windows service integration (#4790) 11 months ago
replacer_test.go replacer: working directory global placeholder (#5127) 8 months ago
service_windows.go core: Chdir to executable location on Windows (#5115) 8 months ago
sigtrap.go go.mod: Upgrade CertMagic to v0.16.0 1 year ago
sigtrap_nonposix.go core: Windows service integration (#4790) 11 months ago
sigtrap_posix.go core: Windows service integration (#4790) 11 months ago
storage.go pki: Add trust subcommand to install root cert (closes #3204) 3 years ago
usagepool.go events: Implement event system (#4912) 9 months ago


a project

Every site on HTTPS

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

@caddyserver on Twitter Caddy Forum
Caddy on Sourcegraph Cloudsmith

Releases · Documentation · Get Help


Powered by


  • 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
  • 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


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


For development

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

$ git clone ""
$ 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 like so:

$ go run -exec ./ 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.

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 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

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. 🙂


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:

The docs are also open source. You can contribute to them here:

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 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).


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, a Stack Holdings 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.