~/foss-indexA small, growing directory
← All tools

Servers & monitoring

Caddy

Fast, extensible web server with automatic HTTPS. No manual certificate handling.

Apache-2.0

Permissive like MIT, with an express patent grant from contributors and a requirement to state the changes you made.

Read the full license ↗

Plain-language summary, not legal advice.

Source code ↗Support this project ↓
Release notes / v2.11.9

Released 2026-11-05. Snapshot from the included release data, not a live check.

This is a quick follow-up on top of 2.11.8, to fix a regression it introduced and a few more security issues, mostly in FastCGI. It contains only fixes backported from master, plus a couple of small additions. **If you're on 2.11.8 and serve PHP, we recommend upgrading.** **Huge thank you to our sponsors for keeping the project alive with resources, and for our maintainers who triage and assist tirelessly in this relentless new age of AI.** ## Highlights - **Fixed: PHP directory indexes (regression in 2.11.8).** A request for a directory with a trailing slash, like `/wp-admin/`, was m…

Read the full release notes on GitHub ↗

Available on these platforms

These are server host targets, not graphical desktop clients or native phone apps. Hosting and exposing a service requires a separate configuration and security plan.

Compatibility details and official sources

Official availability checked 2026-11-12. Availability is not feature parity. The recorded release and license refer to the linked source project; separate clients can differ. No install or compatibility test was run.

Before you install

A web server whose HTTPS just works.

What does it run on?
Any Linux server, a Docker container or a package repo install. Its headline feature is automatic HTTPS: it obtains and renews Let's Encrypt certificates without configuration.
Where is my data?
Your sites and the Caddyfile live on your server. Certificates come from Let's Encrypt; no account with a vendor is required.
What will I maintain?
A short Caddyfile, updates, and the usual web-server care. It serves static files, reverse-proxies to apps and handles TLS renewal for you.

Advice and funding routes source-checked November 12, 2026. Researched, not an install or restore test. Installation source ↗ · Report a correction

Caddy's default welcome page confirming the web server is working, with next steps for serving a site
Our own screenshot of Caddy v2.11.9. Empty default state, not a production setup. The tool icon is the project's own mark. Image credits.

Caddy is an open-source web server written in Go. Its headline feature is automatic HTTPS: it obtains and renews TLS certificates from Let’s Encrypt without any configuration, which removes one of the most error-prone parts of running a site. It serves static files, reverse-proxies to apps, and handles HTTP/2 and HTTP/3 out of the box.

Quick start

Verified against Caddy’s own documentation on November 9, 2026.

Jump to: Docker Compose · Ubuntu Server · Fedora · CentOS / RHEL · NixOS

Docker Compose

Save this as compose.yaml:

services:
  caddy:
    image: caddy
    container_name: caddy
    restart: unless-stopped
    ports:
      - 80:80
      - 443:443
    volumes:
      - ./conf:/etc/caddy
      - caddy-data:/data
      - caddy-config:/config
volumes:
  caddy-data:
  caddy-config:

Put your Caddyfile at ./conf/Caddyfile (mount the folder, not the file itself), then docker compose up -d. The data volume keeps issued certificates. Works on any host with Docker and the Compose plugin: on Ubuntu Server, sudo apt install docker.io docker-compose-v2 covers both; on NixOS, virtualisation.docker.enable = true; enables Docker.

Ask your AI to help with setup · Docker Compose

Docker Compose · Fast, extensible web server with automatic HTTPS. No manual certificate handling. Paste into your AI assistant. It may only be able to guide you. Review changes before running anything.

Researched from the project's documentation. Checked 2026-11-12. No AI account or connection is needed here.

Read or copy the prompt manually

Ubuntu Server

Caddy’s official apt repository:

sudo apt install --yes debian-keyring debian-archive-keyring apt-transport-https curl
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/gpg.key' | sudo gpg --dearmor -o /usr/share/keyrings/caddy-stable-archive-keyring.gpg
curl -1sLf 'https://dl.cloudsmith.io/public/caddy/stable/debian.deb.txt' | sudo tee /etc/apt/sources.list.d/caddy-stable.list
sudo chmod o+r /usr/share/keyrings/caddy-stable-archive-keyring.gpg
sudo chmod o+r /etc/apt/sources.list.d/caddy-stable.list
sudo apt update
sudo apt install caddy

The package sets Caddy up as a systemd service; sudo systemctl enable --now caddy starts it. Until you write your own /etc/caddy/Caddyfile, it serves a default page on port 80.

Ask your AI to help with setup · Ubuntu Server

Ubuntu Server · Fast, extensible web server with automatic HTTPS. No manual certificate handling. Paste into your AI assistant. It may only be able to guide you. Review changes before running anything.

Researched from the project's documentation. Checked 2026-11-12. No AI account or connection is needed here.

Read or copy the prompt manually

Fedora

Caddy’s official COPR repository:

sudo dnf install dnf5-plugins
sudo dnf copr enable @caddy/caddy
sudo dnf install caddy

Then sudo systemctl enable --now caddy; it serves a default page on port 80 until you write /etc/caddy/Caddyfile. If firewalld is active, allow web traffic:

sudo firewall-cmd --permanent --add-service=http --add-service=https
sudo firewall-cmd --reload
Ask your AI to help with setup · Fedora

Fedora · Fast, extensible web server with automatic HTTPS. No manual certificate handling. Paste into your AI assistant. It may only be able to guide you. Review changes before running anything.

Researched from the project's documentation. Checked 2026-11-12. No AI account or connection is needed here.

Read or copy the prompt manually

CentOS / RHEL

sudo dnf install dnf-plugins-core
sudo dnf copr enable @caddy/caddy
sudo dnf install caddy

Then sudo systemctl enable --now caddy; it serves a default page on port 80 until you write /etc/caddy/Caddyfile. If firewalld is active, allow web traffic:

sudo firewall-cmd --permanent --add-service=http --add-service=https
sudo firewall-cmd --reload
Ask your AI to help with setup · CentOS / RHEL

CentOS / RHEL · Fast, extensible web server with automatic HTTPS. No manual certificate handling. Paste into your AI assistant. It may only be able to guide you. Review changes before running anything.

Researched from the project's documentation. Checked 2026-11-12. No AI account or connection is needed here.

Read or copy the prompt manually

NixOS

A Caddy reverse proxy is a few lines in configuration.nix:

services.caddy = {
  enable = true;
  virtualHosts."example.com".extraConfig = ''
    reverse_proxy localhost:8080
  '';
};

Then sudo nixos-rebuild switch.

Ask your AI to help with setup · NixOS

NixOS · Fast, extensible web server with automatic HTTPS. No manual certificate handling. Paste into your AI assistant. It may only be able to guide you. Review changes before running anything.

Researched from the project's documentation. Checked 2026-11-12. No AI account or connection is needed here.

Read or copy the prompt manually

Why it’s listed

The short configuration is easy to review. Automatic certificates remove a manual maintenance step.

Tags: Infrastructure, Self-hosted, NixOS module

Want help setting this up? Ask FOSSadmin ↗