Phusion white papers Phusion overview

Phusion Blog

Who’s running Phusion Passenger in production?

By Hongli Lai on September 25th, 2008

An interesting thread appeared on the Phusion Passenger mailing list, in which user asked who’s running Phusion Passenger in production. We’re actually very interested as well, seeing as we’re currently building a new website for Phusion. Please drop a note at the mailing list (or here, though the mailing list is preferred) if you’re running it in production as well.

  • Hi

    I have Phusion Passenger in production on a small scale intranet site and also that website is running on Passenger. No problems no far. 🙂


  • Will Green

    I am. and

  • we’re using passenger since 1.0 at are very satisfied!

  • loving passenger at

  • Patric

    Would like to, but it seems to be compilation issues on Solaris 10 (which is fixed in the development code).

  • Hi I’m also using passenger sucessfully for my production environment of and and I’m quite satisfied with it so far :-).

  • I’m using passenger on my web monitoring system at

    So far I’ve been very happy with the decrease in memory usage in combination with Ruby Enterprise, and the more simple deployment and monitoring procedures.

  • gjg

    Running it at Great stuff!

  • Mathijs Kwik

    I have passenger on 3 servers serving about 20 sites.
    Works fast, solid and stable, deployment with capistrano is easier too for passenger since I don’t have to assign port numbers.
    Just waiting for neverblock to support passenger.

  • Hongli asked me to mirror my reply from the mailing list on the blog as well:

    I’d again like to reiterate the importance of what you guys are
    currently doing for us right now, and would like to encourage the
    reader out there to post their experiences with passenger here.
    Besides acting as a morale boost (to read what we’re all doing it
    for :-)), it also provides us with an opportunity to showcase our
    technology (and our skills) to potential clients. Seeing as we’ve made
    this open source from the get-go, this has always been the plan, but
    what people may not realize is that maintaining Passenger costs a lot
    of time and money. Open source is NOT free, at least not for one
    party, i.e. the contributing party. Seeing as we’ve never asked, and
    never will ask you for your money for Passenger unless you WANT to, we
    need to find ways to sustain the project (thanks contributors!) as
    well as ourselves. That hasn’t been easy, seeing as Passenger was
    built to be robust and stable, not many of you out there would ever
    feel the need to have commercial support (another guy you may know
    called Zed Shaw experienced the exact same with Mongrel) : this kind
    of gives us mixed feelings, on the one hand, you couldn’t be more
    proud to have contributed to a robust product and see it do what it
    should do, and to see what fortune 500 companies are using it. On the
    other hand, we’re investing lots and lots of hours to sustain a
    project that isn’t able to sustain us financially in return even to
    the point that we’re currently considering to discontinue professional
    open source as one of our business models. The only reason why we
    haven’t done that till this point is because we love open source, and
    are very grateful to it as well. So before you get me wrong, I’d like
    to say we were well aware of all of this before we decided to open
    source passenger instead of sticking a commercial license to it (for
    what it’s worth, we’d do it again in a heartbeat 🙂 ). It has opened
    many doors for us that would very likely have remained closed to us
    otherwise, and for the larger part, we have the nice things people
    said about passenger to thank for that! So you probably may not
    realize this, but your testimonials are worth gold to us (almost
    literally). So keep ’em coming guys 🙂

  • Thijs

    We’re using it in production on all sites we host. And we’re using it for our product ConfNetwork which will be launched in a few weeks.

  • We’re using in production on and haven’t had any problems with it.

    Less systems administration == more gooderer. Thanks Phusion.

  • Seb

    We’re using it in production on, it’s working like a charm 😉

  • Just launched an e-commerce site:
    ruby enterprise + passenger, works great!
    increased speed & reduced memory. no more mongrel clusters.

  • Foo

    Using passenger to run five intranet apps.

  • I am using passenger to run It’s working very nicely.

  • We are using Passenger for both Rack and Rails at …It’s fantastic!

  • Lisa

    Just wanted to let you know that your work has led me to choose Rails as a development framework. I had concerns about ease of deployment before discovering Passenger. Thanks. 🙂

  • I am using mod_rack with It works great. Many thanks for this great product.

  • Both and are on passenger. Will never go back to mongrels now – you guys are doing amazing work.

  • We’re using it in production for almost all the sites we host and we love it! No real problems so far.

  • dalvarad

    Desde passenger 1.x lo hemos venido usando en y
    Sitios con alto tráfico de Chile. Estabilidad las caga. Chao mongrel

  • We are using Passenger 2.0.3 for .
    It’s working great.

  • It’s being used at, one of the highest traffic websites in Argentina.

  • EP

    We use Passenger on which serves 10 million pages per month.

  • We’re using Passenger as well as Ruby Enterprise Edition on and Thanks for putting such a quality product out. Our deployment and management is so much easier now.

  • We’re currently using it on our site, which is a rails app for generating QR Codes. We’ve had zero problems with it so far – it took us less than an hour to get a new production machine up and running with passenger and our application. Good work!

  • We have been using Passenger in producton for a couple of months at