Automatic HTTPS
Caddy automatically handles HTTPS by obtaining and renewing certificates from Let's Encrypt, simplifying the process of securing web applications.
Ease of Configuration
Caddy uses a straightforward configuration file (Caddyfile) that is easier to write and understand compared to other web servers like Nginx or Apache.
Cross-Platform
Caddy is designed to run efficiently on virtually any platform, including Windows, macOS, Linux, and Docker, giving it great flexibility for deployment.
Built-in Reverse Proxy
Caddy includes built-in support for reverse proxy functionality, which can easily be configured to distribute load among multiple servers.
Extensible
Caddy supports plugins for additional features, allowing users to extend its functionality without compromising its core simplicity.
Integrated Logging and Metrics
Caddy includes integrated logging and monitoring capabilities, which make it easier to maintain and debug the server without additional tools.
Active Community and Support
Caddy has an active community and is well-supported with extensive documentation, which helps new users get up to speed quickly and troubleshoot issues effectively.
Promote Caddy. You can add any of these badges on your website.
Caddy is generally considered a good choice for developers looking for a hassle-free, secure, and modern web server. Its automatic HTTPS and easy configuration make it particularly appealing for small teams and developers who need to deploy web services quickly without diving deep into server setup complexities.
We have collected here some useful links to help you find out if Caddy is good.
Check the traffic stats of Caddy on SimilarWeb. The key metrics to look for are: monthly visits, average visit duration, pages per visit, and traffic by country. Moreoever, check the traffic sources. For example "Direct" traffic is a good sign.
Check the "Domain Rating" of Caddy on Ahrefs. The domain rating is a measure of the strength of a website's backlink profile on a scale from 0 to 100. It shows the strength of Caddy's backlink profile compared to the other websites. In most cases a domain rating of 60+ is considered good and 70+ is considered very good.
Check the "Domain Authority" of Caddy on MOZ. A website's domain authority (DA) is a search engine ranking score that predicts how well a website will rank on search engine result pages (SERPs). It is based on a 100-point logarithmic scale, with higher scores corresponding to a greater likelihood of ranking. This is another useful metric to check if a website is good.
The latest comments about Caddy on Reddit. This can help you find out how popualr the product is and what people think about it.
In order to secure the backend, we used a service called "Caddy" with a custom configuration to require the presence of an API key as a header. - Source: dev.to / about 1 month ago
People still deal with SSL certificates? Lol ? https://caddyserver.com/. - Source: Hacker News / about 1 month ago
The Caddy[1] webserver also has built-in ACME. It has all the problems Rachel mentioned, of course, because now it's an ACME client embedded in an even bigger piece of software, but it's handy for sure! I don't know much about Caddy scalability but it's worked great for my personal sites. [1] https://caddyserver.com/. - Source: Hacker News / 4 months ago
This single record will suffice as we will be using a reverse proxy to map each of our application. For the reverse proxy solution, we will be using Caddy, particularly xcaddy. - Source: dev.to / 5 months ago
It looks nice and friendly, but for developers I can recommend exploring caddy[1] or nginx[2]. It's a useful technology to have worked with, even if they're ultimately only used for proxying analytics. [1] https://caddyserver.com/. - Source: Hacker News / 6 months ago
I began to self-host a Minecraft server using Crafty Controller, an Excalidraw instance, Docmost to replace Notion, Plane to replace Jira, and Penpot to replace Figma. To be able to access them from the internet, I used Nginx Proxy Manager to set up reverse proxies with SSL. You can use Traefik or Caddy instead, but I enjoyed the ease-of-use of NPM. For a dashboard solution, I started with Homarr, but later... - Source: dev.to / 6 months ago
Caddy is the ultimate web server anyone should be using. This is true for production as well as for local development. It is very fast, and by default obtains and renews SSL certificates automatically. This is useful for when you want to test certain website feature that is only allowed when they're accessed with HTTPS. You get free TLS for all your subdomains, and it does that in a scalable way. - Source: dev.to / 7 months ago
Fortunately Caddy is not evil: https://caddyserver.com/. - Source: Hacker News / 8 months ago
Sidecar containers: Google Cloud Run has a cool feature where you can run multiple containers next to each other. So for example, if you want to run Caddy or Traefik as a reverse proxy for your ingress container and then have both your web frontend container & backend api container co-located in the same service, you can do that & have everything be super low latency. - Source: dev.to / 9 months ago
FrankenPHP use Caddy as proxy server, so we'll need a Caddyfile to configure it and also provide basic php configurations. Here again we'll stick to the FrankenPHP documention. You can find it in the docker/frankenphp folder. - Source: dev.to / 10 months ago
Caddy to allow our logs to be sent over HTTPS. - Source: dev.to / 10 months ago
Ngrok is a reverse proxy tunnel, and in our case, we need it for a public network address in order to receive webhooks from VCS. Ngrok we used here is for demonstration purposes. For production use, we recommend using Caddy. - Source: dev.to / 10 months ago
Whilst nginx was good, I wanted to move to Caddy Server , first because my other product AssistFlare was already using it and then for the simplicity of Caddy over nginx with automatic SSL certificate provisioning for sites hosted on Stomod as well as better performance as per the difference benchmarks floating around the internet with it unlocking multi-core systems better than nginx. See bookmark below for... - Source: dev.to / 11 months ago
Ayo! Another day, another tech. When I struggle with SSL certs, I found unique way to solve specific problem and today, Iโd like to introduce you Caddy! It solves various kind of problems but I will focus on mine. - Source: dev.to / 11 months ago
Create a new website directory with three files, index.html, about/index.html, and login/index.html. Then, install the Caddy web server in an isolated shell and tell it to serve the current directory at http://localhost:3000. - Source: dev.to / 11 months ago
Not OP but I have a couple of implementations: one using caddyserver[0] as a reverse proxy in a docker-compose set up, and the other is a Kubernetes cluster using cert-manager[1]. [0] https://caddyserver.com/. - Source: Hacker News / 12 months ago
You can do a reverse proxy, such as with nginx or Caddy. - Source: dev.to / 12 months ago
Caddy server has proven to be a very promising project. Not only is it fast, but it also has many built-in features that greatly simplify configuration. One example is the automatic issuance of SSL certificates. Moreover, it's very easy to set up a service using Caddy. - Source: dev.to / 12 months ago
Not sure about lesser known but my top tools are: - Caddy server (Auto SSL, Dead simple Reverse Proxy) [0] - mkcert(local SSL) [1] - AWS Global Accelerator [2] (Static IP, Route traffic based on location) [2] [0] https://caddyserver.com/ [1] https://github.com/FiloSottile/mkcert. - Source: Hacker News / about 1 year ago
I recommend checking out [Caddy](https://caddyserver.com/), which replaces both Nginx and Certbot in this setup. [Tailscale](https://tailscale.com/) can remove the need to open port 22 to the world, but I wouldn't rely on it unless your VPS provider has a way to access the server console in case of configuration mistakes. - Source: Hacker News / about 1 year ago
A lot of the things you described sound like caddy? [1] [1] https://caddyserver.com/. - Source: Hacker News / about 1 year ago
Caddy, a modern web server known for its simplicity and robust feature set, has been making waves in the industry by addressing key concerns faced by developers and system administrators. As a prominent player among web servers, it stands alongside competitors like Nginx, Apache HTTP Server, Traefik, and Microsoft IIS, each catering to specific user needs and preferences.
One of the standout features of Caddy is its automatic HTTPS, which simplifies the process of securing sites by automatically obtaining and renewing SSL certificates via Let's Encrypt. This feature has found favor among users who prioritize security but prefer to avoid the complexity typically associated with SSL configurationโin stark contrast to older methods that require more manual certificate management. Consequently, Caddy is often recommended in discussions of lighter-weight alternatives or complements to more complex setups, such as those using Nginx paired with Certbot.
Caddy's configuration is notably simpler, using a straightforward text file which, while efficient, poses a learning curve for beginners accustomed to GUI-based configuration. For users who appreciate UNIX-style tooling, this design choice offers a clean, no-nonsense approach to web server configuration and management.
Caddy has been shown to work well in a diverse array of environments. From managing personal sites to full-fledged production deployments, its scalability suits a spectrum of project scopes. Developers point out that Caddy not only supports static site hosting but is also exceptionally adept at serving as a reverse proxy. This makes it an attractive option for those seeking a server that can easily integrate and facilitate microservices architectures.
The discussion around Caddy often highlights its use in self-hosted environments, where simplicity and reliability are paramount. Its role in home server setups, reverse proxy solutions, and even sidecar containers in Kubernetes clusters reinforce its flexibility and adaptability in handling modern web infrastructure needs.
Comparatively, Caddy often emerges as a simpler alternative to Nginx and Apache in scenarios where minimal configuration and automatic service provisioning are advantageous. Reviews frequently cite it as a viable option when managing HTTP/2 and HTTP/3 connections with its built-in capabilities for upgrading network protocols, further positioning it as a forward-thinking server choice befitting the evolving digital landscape.
Moreover, Caddy has been integrated into various modern development environments, as exhibited by its inclusion in Docker and other containerized setups, enhancing its reputation as a versatile and reliable tool for developers navigating contemporary software deployment paradigms.
Overall, public opinion acknowledges Caddy's strengths in providing an easy-to-use, robust, and feature-rich web server solution. While it may not replace more entrenched web servers for all use cases, particularly where advanced configuration is necessary, its niche appeal as a no-fuss server with strong automation and security features positions it as a formidable competitor in the web server landscape. This makes it a compelling choice for developers and system administrators seeking a balance between simplicity and powerful functionalities.
Do you know an article comparing Caddy to other products?
Suggest a link to a post with product alternatives.
Is Caddy good? This is an informative page that will help you find out. Moreover, you can review and discuss Caddy here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.
I've been using Caddy for a while now. Simple and reliable.