Puma

Threaded Ruby web server for Rack apps, default in Rails. Our application servers ranking puts Puma at #9 of 14.

Commercial relationships can affect which products appear and how prominently. The Puma link is marked as every vendor link is, see disclosure.

Visit Puma See it in the application servers ranking

01

At a glance

HeadquartersNot stated by the vendor
Pricing modelBSD-3-Clause gem; the pages read show no paid plan or price
APINot stated in the pages we read
Best forRails and Rack teams tuning threads and worker processes on one host
DeploymentUnclear from the vendor pages
Free planNo free plan recorded
02

What is Puma?

Puma is a concurrent HTTP 1.1 web server for Ruby, built only to run Rack applications. Its home page says it was created by Evan Phoenix in late 2011 as a derivative of Mongrel, and the copyright line credits Evan Phoenix and Contributors without naming a company or foundation.

A Ragel extension handles HTTP parsing, and the page notes that Puma performs best on Ruby implementations with true parallelism. The README adds that it is the default server for Rails and is included in the generated Gemfile. The code sits in the puma account on GitHub under the BSD-3-Clause licence. The pages we read show no paid plan or price, and the home page does not mention HTTP/2.

03

Puma key features

  • Threads per worker. Each worker runs a thread pool, set with -t or --threads. The README gives a default of 0:16, or 0:5 on MRI, which means a small Ruby app can serve overlapping requests without extra processes.
  • Clustered mode. Several worker processes are started with -w or --workers, or through the WEB_CONCURRENCY environment variable. Setting workers to auto needs the concurrent-ruby gem, a detail the README states explicitly.
  • Preloading. The --preload flag, or the preload_app setting in the config file, loads the application before workers are forked. The README warns that preloading cannot be combined with phased restart, so the choice affects how you deploy updates.
  • Hot restart. A hot restart keeps server sockets open between restarts, so connections made during the switch are not refused. The README says this does not hold on JRuby, where restarts do not keep sockets open.
  • Config file lookup. Puma reads puma.rb, loaded with -C. Without a flag it looks for config/puma.rb or config/puma/environment.rb, and --no-config switches that lookup off, which keeps behaviour predictable in odd layouts.
  • pumactl control tool. The pumactl command talks to a running server through its control server, using --control-url and --control-token, for example to ask for a restart without logging into the process.
  • Rails default. Rails generates a Gemfile that already includes Puma. The README still recommends bundle exec puma over rails server when you need access to the full set of configuration options.
04

Who Puma suits

  • Rails developers. Anyone starting a new Rails app already has Puma in the generated Gemfile, so the server is available from day one and can be tuned through puma.rb as traffic grows.
  • Teams running Rack apps outside Rails. Custom Rack applications get a threaded server built for exactly that interface, without the Rails-specific assumptions of a framework runner, and with the same puma.rb file to tune it.
  • Operators needing zero-drop restarts. Where hot restart is supported, an operator can restart the server through pumactl while sockets stay open, which suits deploys that should not interrupt live connections.
05

Getting started with Puma

Puma is distributed as a Ruby gem, so installation follows the usual gem or Bundler route. For Rails projects it is already listed in the generated Gemfile, and the README advises starting it with bundle exec puma rather than rails server so that every option is reachable. Choose the thread count with -t, and move to clustered mode with -w or WEB_CONCURRENCY when you want several worker processes.

Put long-lived settings in config/puma.rb, which Puma finds without a flag, or point to another file with -C. If you use the preload_app setting, remember it excludes phased restart. For control after launch, pumactl with a control URL and token can restart a running server. The pages we read give no step-by-step production guide beyond this.

06

Strengths and limits of Puma

Where Puma wins
  • Puma is a Ruby server built only for Rack apps, created by Evan Phoenix in late 2011 as a derivative of Mongrel, and it is the default server for Rails.
  • Strongest for: Rails and Rack teams tuning threads and worker processes on one host.
  • Marked in our records as rack.
  • Marked in our records as BSD-3-Clause.
  • Catalogue tag: Clustered mode.
Where Puma does not
  • Preloading the app cannot be combined with phased restart.
  • Cluster mode is unsupported on JRuby, and restarts there do not keep server sockets open.
  • Not for: Non-Ruby teams, or anyone wanting a vendor support contract.
07

What we make of Puma

Puma is a Ruby server built only for Rack apps, created by Evan Phoenix in late 2011 as a derivative of Mongrel, and it is the default server for Rails.

Each worker runs a thread pool, with clustered mode for several workers. The README says cluster mode does not work on JRuby for lack of fork, and the home page does not mention HTTP/2. No company or foundation is named.

The application servers list places Puma 9 of 14: it follows Gunicorn and comes before Uvicorn. Challengers hold places 1 to 3 where a category has them; the number here is a place in the order, not a mark out of ten.

The vendor states no country of establishment, so Puma is left out of the regional count for this list.

08

Puma pros and cons in practice

Works well
  • It ships as the Rails default, so most Rails teams already have it installed.
  • Threads inside each worker allow concurrent requests even from a single process.
  • Hot restart and pumactl give operators a way to restart without dropping sockets where supported.
  • The BSD-3-Clause licence and absence of a price remove procurement steps.
Gets in the way
  • Cluster mode is not supported on JRuby because of a lack of fork(2), according to the README.
  • The home page does not mention HTTP/2, so check how your front proxy handles it.
  • Preloading cannot be used with phased restart, which forces a choice between the two.
  • Only Rack applications are in scope, so non-Ruby workloads need another server.
09

Puma in practice

Puma's thread count is set with -t or --threads and defaults to 0:16, or 0:5 on MRI; workers are set with -w or WEB_CONCURRENCY, and :auto needs the concurrent-ruby gem.

It reads config/puma.rb unless --no-config is given, supports hot restart that keeps sockets open, and ships pumactl for control through a control URL and token.

The README recommends bundle exec puma over rails server for full configuration access.

10

What Puma costs

In the catalogue: BSD-3-Clause gem; the pages read show no paid plan or price.

The pages we read show no paid plan or price for Puma. It is open-source Ruby gem software under the BSD-3-Clause licence, as shown on the puma repository, so there is no licence fee to budget for. Costs come from the servers or containers that run it. The home page names Evan Phoenix and Contributors in its copyright line and no company, foundation or support service, so a commercial support contract or invoice is not described on the pages we read. Organisations that need one would have to look for it outside the project, through a Ruby consultancy or a platform provider that bundles Puma.

Checked against puma.io for Best Application Servers in 2026, review date 15 November 2026.

11

Puma: data and security

Puma runs inside your own infrastructure, so request data never passes through a vendor. The pages we read mention no certifications, audit reports or data processing terms, and no company is named as operator.

The pumactl control server uses a control URL and token, so that token deserves the same care as any administrative credential. Hardening, TLS termination and update cadence are left to the team deploying it, with the BSD-3-Clause licence placing no obligations on how you operate it.

12

Fact sheet: Puma

ProductPuma
Vendor websitepuma.io
Catalogue tagsRack, Clustered mode, BSD-3-Clause
Price visibilityModel recorded, no figure
Not in our datauptime history and customer numbers
Rank there#9 of 14
Head-to-head pagesNo comparison written
Primary guideBest Application Servers in 2026
Alternatives pageNo dedicated page
HeadquartersNot stated by the vendor
13

Integrations and ecosystem

Integrations the vendor names (9):

  • Rack
  • Ruby on Rails
  • Bundler
  • RubyGems
  • MRI
  • JRuby
  • concurrent-ruby
  • pumactl
  • Ragel
14

Also ranked in

15

Alternatives to Puma

Closest by traits, not by rank: 4 products from the same list that overlap most with Puma.

  • Apache TomEE (#5 of 14): Jakarta EE server built on Tomcat, in four distributions.
  • WildFly (#7 of 14): Modular Java application server with Galleon provisioning and a Kubernetes operator. Watch out: the pages read do not state who develops WildFly day to day or where it is based.
  • Gunicorn (#8 of 14): Pre-fork WSGI server for Python, started with a single command.
  • Uvicorn (#10 of 14): ASGI web server for Python async frameworks, run with one command. Suits: Teams running async Python frameworks needing WebSockets and HTTP/2 from one server.
16

Puma: questions

9 answers
Is Puma one of the top application servers?

Puma is #9 of 14 in our application servers ranking.

Which tools compete with Puma?

Start with Apache TomEE, WildFly, Gunicorn and Uvicorn. Compare their entries before settling on Puma.

Who should choose Puma?

Rails and Rack teams tuning threads and worker processes on one host. Less suited to: non-Ruby teams, or anyone wanting a vendor support contract.

Is Puma free, or what does it charge?

The pricing entry for Puma reads: BSD-3-Clause gem; the pages read show no paid plan or price. On free access, we recorded no free plan.

Is Puma a European company?

The vendor pages we reviewed state no country of establishment for Puma, so we do not give one.

Is Puma only for Rails?

No. The home page says it is designed only for running Rack apps, and Rails happens to use it as the default server.

How many threads does it use by default?

The README states a default of 0:16, or 0:5 on MRI, adjustable with -t or --threads.

Does it work on JRuby?

It runs there, but the README says cluster mode is not supported on JRuby and restarts do not keep server sockets open.

What licence applies?

The puma repository on GitHub shows the BSD-3-Clause licence.

17

Puma: sources

Read from the vendor’s own pages on 14 November 2026.

18

How we rank

The same four questions are asked of every application servers product: time to value, real cost, the way out and the intended buyer. Here that gives Puma the #9 position in a list of 14. Details: how we rank software.