What people actually say about Caddy

69 mentions across 4 sources · 84% positive · researched Jul 3, 2026

Hacker News, App Store, GitHub, Lemmy

What users praise

  • Automatic HTTPS via Let's Encrypt with zero config.
  • Caddyfile syntax is simpler than Nginx or Apache.
  • Built-in reverse proxy supports load balancing and unix sockets.

What frustrates them

  • TLS-SNI panic crash in v2.7.x affects production stability.
  • Encrypted Client Hello (ECH) still not implemented after years.
  • SSL cert failures on reboot reported by some users.

This is a summary. The full report adds every quote we found, a per-source breakdown, recurring themes, hidden costs and the learning curve — run a free scan below, or see the full Caddy review.

What comes up again and again about Caddy

Recurring themes across everything we collected, with where each one showed up.

  • Ease of setup and simplicity compared to alternatives

    praised · seen on Hacker News, Lemmy

  • Automatic HTTPS is a major selling point

    praised · seen on Hacker News, GitHub, Lemmy

  • TLS-SNI panic bug causing production crashes

    criticised · seen on GitHub

  • Desire for improved privacy features like ECH

    criticised · seen on GitHub

  • Great for self-hosted and homelab setups

    praised · seen on Hacker News, Lemmy

How hard is Caddy to learn?

Users describe it as beginner · typically 5 minutes to get going

Where people get stuck

  • Understanding the Caddyfile syntax for advanced features
  • Debugging TLS-SNI panic if encountered

Who Caddy actually suits

Works well for

  • Self-hosters running multiple services behind a single server
  • Developers who want quick HTTPS without manual cert management
  • Homelab enthusiasts building simple secure setups

Not the right fit for

  • Enterprises requiring advanced traffic management and health checks
  • Users needing Encrypted Client Hello for privacy compliance

What people are discussing right now

Discussion volume is medium and trending stable

  • Caddy as reverse proxy
  • Automatic HTTPS
  • Self-hosting
  • TLS-SNI bug
  • ECH feature request
Back to Caddy
LIVE MARKET SENTIMENT

What people really think about Caddy

A real-time sweep of the open web — social media, forums, review sites, video reviews and live community discussions — distilled into one honest verdict with the actual mentions behind it.

Real-time Live mentions Unbiased Downloadable
No card needed

What's inside your Caddy report

Everything you need to decide — distilled from real, current user opinion.

Live mentions

The actual posts, reviews & complaints about Caddy — with links and dates.

Honest verdict

A straight answer on whether it lives up to the hype — and who it’s really for.

Praise & gripes

What users genuinely love and the frustrations that keep coming up.

Real quotes

Representative voices from real users, not marketing copy.

Recurring themes

The patterns across hundreds of opinions, surfaced at a glance.

Red flags

Hidden costs and dealbreakers people only discover after signing up.

How it works

1

Sign up free

Create an account in seconds — get 5 free scans, no card.

2

We sweep the web

Live social media, forums, reviews & video opinions — in ~30–60s.

3

Get your report

An honest, downloadable verdict with the real mentions behind it.

Ready to see the real verdict on Caddy?

Your scan is ready in under a minute · ₹20 / $1.

Compare Caddy head-to-head

See how it stacks up against the tools people weigh it against.

Top alternatives to Caddy

Researching options? Explore the closest alternatives.

Check sentiment on these too

Run a live scan on the alternatives before you decide.

Caddy — questions buyers ask

What do people complain about most with Caddy?

The complaints that recur most often are TLS-SNI panic crash in v2.7.x affects production stability, encrypted Client Hello (ECH) still not implemented after years and SSL cert failures on reboot reported by some users. Drawn from 69 mentions across 4 sources.

What do users like about Caddy?

Users consistently praise automatic HTTPS via Let's Encrypt with zero config, caddyfile syntax is simpler than Nginx or Apache and built-in reverse proxy supports load balancing and unix sockets.

Is Caddy hard to learn?

Users describe it as beginner; most people are up and running in 5 minutes; the usual sticking points are understanding the Caddyfile syntax for advanced features and debugging TLS-SNI panic if encountered.

Who should not use Caddy?

Based on what users report, it is a poor fit for enterprises requiring advanced traffic management and health checks and users needing Encrypted Client Hello for privacy compliance.

What are people saying about Caddy right now?

Discussion volume is medium and trending stable. Current topics: caddy as reverse proxy, automatic HTTPS and self-hosting.

How current is this report?

Each scan runs live the moment you click — it reflects what people are saying now, and every report lists the dated mentions behind it.

Can I download it?

Yes — download the full report as a polished, shareable PDF.

← Back to CaddyBrowse ProductivityAll AI toolsAll comparisons