Need advice about which tool to choose?Ask the StackShare community!

Caddy

263
261
+ 1
20
Puma

834
256
+ 1
19
Add tool

Caddy vs Puma: What are the differences?

Caddy: The HTTP/2 Web Server with Automatic HTTPS. Caddy is a production-ready open-source web server that is fast, easy to use, and makes you more productive. HTTP/2 and HTTPS by default; Puma: A Modern, Concurrent Web Server for Ruby. Unlike other Ruby Webservers, Puma was built for speed and parallelism. Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications.

Caddy and Puma can be categorized as "Web Servers" tools.

"Easy HTTP/2 Server Push" is the primary reason why developers consider Caddy over the competitors, whereas "Easy" was stated as the key factor in picking Puma.

Caddy and Puma are both open source tools. It seems that Caddy with 22.7K GitHub stars and 1.79K forks on GitHub has more adoption than Puma with 5.78K GitHub stars and 987 GitHub forks.

According to the StackShare community, Puma has a broader approval, being mentioned in 73 company stacks & 30 developers stacks; compared to Caddy, which is listed in 14 company stacks and 5 developer stacks.

Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Caddy
Pros of Puma
  • 6
    Easy HTTP/2 Server Push
  • 6
    Sane config file syntax
  • 4
    Builtin HTTPS
  • 2
    Letsencrypt support
  • 2
    Runtime config API
  • 3
    Convenient
  • 3
    Free
  • 3
    Easy
  • 2
    Multithreaded
  • 2
    Default Rails server
  • 2
    First-class support for WebSockets
  • 2
    Consumes less memory than Unicorn
  • 1
    Lightweight
  • 1
    Fast

Sign up to add or upvote prosMake informed product decisions

Cons of Caddy
Cons of Puma
  • 3
    New kid
  • 0
    Uses `select` (limited client count)

Sign up to add or upvote consMake informed product decisions

What is Caddy?

Caddy 2 is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go.

What is Puma?

Unlike other Ruby Webservers, Puma was built for speed and parallelism. Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Caddy?
What companies use Puma?
See which teams inside your own company are using Caddy or Puma.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Caddy?
What tools integrate with Puma?
    No integrations found

    Blog Posts

    What are some alternatives to Caddy and Puma?
    NGINX
    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.
    Traefik
    A modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components and configures itself automatically and dynamically.
    HAProxy
    HAProxy (High Availability Proxy) is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
    Envoy
    Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.
    Apache HTTP Server
    The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.
    See all alternatives