Web servers and proxies

Traefik vs Caddy

Traefik and Caddy each have one supported release line. Traefik 2.11 reached end of life on Sep 7, 2026. Both are open source: Traefik under MIT, Caddy under Apache-2.0. OSV.dev lists 43 advisories from the last 12 months for Traefik and 16 for Caddy.

Last checked against deps.dev, endoflife.date, OSV.dev and CISA KEV.

Side by side

Every value links to its source. Where a row doesn’t apply to one of them, the cell says why.

Support and releases
TraefikCaddy
Supported release lines

Only the newest, 3.7

2.11 ended Sep 7, 2026

endoflife.date

Only the newest, 2

No end dates published

endoflife.date

Latest release

3.7.15

Released Oct 15, 2026

endoflife.date

2.11.7

Released Oct 3, 2026

endoflife.date

Releases in the last 12 months

45 releases

traefik/traefik/v3, Go module

the Go module proxy

8 releases

caddyserver/caddy/v2, Go module

the Go module proxy

Security
TraefikCaddy
Advisories published in the last 12 months

43, worst rated critical

For traefik/traefik/v3

OSV.dev

16, worst rated high

For caddyserver/caddy/v2

OSV.dev

OpenSSF Scorecard

6.4 / 10

traefik/traefik, Aug 24, 2026

Scorecard

9.3 / 10

caddyserver/caddy, Aug 24, 2026

Scorecard

Licence and hosting
TraefikCaddy
Licence

MIT

Open source (permissive)

deps.dev

Apache-2.0

Open source (permissive)

deps.dev

How you run it

Self-hosted (a single binary or container)

Self-hosted (a single binary)

Adoption
TraefikCaddy
GitHub stars

65.2K

traefik/traefik

GitHub

77.8K

caddyserver/caddy

GitHub

  • Advisory counts cover every version, old ones included, and a heavily used, well-audited project often has more. Check the versions you run with the dependency check.

Which fits your constraints

Read across for what matters to you. Each answer comes from the data above or the project’s licence and hosting options.

How Traefik and Caddy fit common constraints
TraefikCaddy
An open-source licence

Yes: MIT

Yes: Apache-2.0

Someone else runs it for you

No: You run it yourself

No: You run it yourself

You can run it on your own servers

Yes: Yes, it’s software you install

Yes: Yes, it’s software you install

A long support window

Only the newest line (3.7); no end dates published

Only the newest line (2); no end dates published

What each is good at

Traefik

Modern HTTP reverse proxy and load balancer for microservices

Strengths

  • Automatic service discovery
  • Native Docker/Kubernetes integration
  • Automatic HTTPS with Let's Encrypt
  • Modern dashboard UI

Trade-offs

  • Higher resource usage than Nginx/HAProxy
  • Younger project with smaller community
  • Some advanced features require Enterprise

Common uses

  • Container environments
  • Kubernetes ingress
  • Microservices
  • Dynamic routing

Caddy

Modern web server with automatic HTTPS

Strengths

  • Automatic HTTPS with zero configuration
  • Simple configuration (Caddyfile)
  • HTTP/3 support out of the box
  • Written in Go (single binary)
  • Excellent for quick setups

Trade-offs

  • Less battle-tested than Nginx/HAProxy
  • Smaller community and ecosystem
  • Fewer advanced load balancing features

Common uses

  • Simple reverse proxy
  • Development environments
  • Static sites with HTTPS
  • Prototyping

From StackPrism’s curated notes. Pricing isn’t covered here: it changes often, so check each vendor’s pricing page.

When teams weigh these two

Both are reverse proxies written in Go with automatic HTTPS through ACME certificate authorities such as Let’s Encrypt. Traefik is built around discovering services from Docker and Kubernetes; Caddy is a general web server with a short config file that also serves static files.

How this comparison works

Release lines and end-of-life dates come from endoflife.date, release counts from deps.dev’s publish dates, and advisories from OSV.dev, counted once per flaw even when it’s listed under several ids, and checked against CISA’s list of vulnerabilities known to be exploited. Status and incident history come from each vendor’s public status feed; licences from each project’s licence file or the vendor’s licensing page, linked in the table.

The data refreshes every few hours and the time it was checked is shown above. There’s no pricing and no overall winner: which one fits depends on your constraints. To see how the versions you actually run hold up, check your repo.

Already using one of them?

Paste a public GitHub repo and see what’s vulnerable, end of life or deprecated in it today. Free, no sign-up.