Web development that doesn't hurt
Companies using Rails
How Rails is being used
  • Zinc

    #<User:0x00007fa2e0cf9060> Zinc

    We use Rails to power most of our APIs and internal services.

  • Mobile and Web Apps

    #<User:0x00007fa2de258ba8> Mobile and Web Apps

    Web has always been in Rails from the beginning, so we used Redis for caching our items, which we had, from the beginning. Rails is kind of what we were comfortable with, and we knew we wanted the front end to be really, really snappy, so we de-normalized all the item attributes into Redis, and that's how it got served out.

  • Karma Website and Mobile Apps

    #<User:0x00007fa2dc03d528> Karma Website and Mobile Apps

    We use Rails for webpages and projects, not for backend services. Actually if you click through our website, you won't notice it but you're clicking though, I think, seven or eight different Rails projects. We tie those all together with a front-end library that we wrote, which basically makes sure that you have a consistent experience over all these different Rails apps.

    It's a gem, we call it Karmeleon. It's not a gem that we released. It's an internal gem. Basically what it does is it makes sure that we have a consistent layout across multiple Rails apps. Then we can share stuff like a menu bar or footer or that kind of stuff.

    So if we start a new front end project it's always a Rails application. We pull in the Karmeleon gem with all our styling stuff and then basically the application is almost ready to be deployed. That would be an empty page, but you would still have top bar, footer, you have some custom components that you can immediately use. So it kind of bootstraps our entire project to be a front end project.

  • EverTrue


    Services that require a short iteration cycle, or any proof-of-concept work.

  • Packet

    #<User:0x00007fa2f0ba6e78> Packet

    Rails is one of the easiest frameworks to use for API development.

  • avalanche2_system

    #<User:0x00007fa2f01973b0> avalanche2_system

    Our monolithic application. Its the core of our stack.

  • StackShare

    #<User:0x00007fa2ef1ff1c8> StackShare

    The first live version of Leanstack was actually a WordPress site. There wasn’t a whole lot going on at first. We had static pages with static content that needed to be updated manually. Then came the concept of user-generated content and we made the switch to a full on Rails app in November of last year. Nick had a lot of experience with Rails so that made the decision pretty easy. But I had also played around with Rails previously and was comfortable working with it. I also knew I’d need to hire engineers with a lot more experience building web apps than I do, so I wanted to go with a language and framework other people would have experience with. Also, the sheer number of gems and tools available for Rails is pretty amazing (shout to RubyToolbox ).

    I don’t see us ever having to move away from Rails really, but I could be wrong. Leanstack was built in Rails 3. For StackShare we decided to upgrade to Rails 4. Biggest issue with that has been caching. DHH decided to remove the standard page and action caching in favor of key-based caching (source)[http://edgeguides.rubyonrails.org/caching_with_rails.html#page-caching]. Probably a good thing from a framework-perspective. But pretty shitty to have to learn about that after testing out your new app and realizing nothing is cached anymore :( We’ll need to spend some more time implementing "Russian Doll Caching", but for now we’ve got a random mixture of fragment and action caching (usually one or the other) based on which pages are most popular.

  • pludoni GmbH - RoR

    #<User:0x00007fa2ef063738> pludoni GmbH - RoR

    Well-established framework for rapid development of web apps. Huge repository of good integrated 3rd party libraries (Gems)

  • Publitory

    #<User:0x00007fa2ea92dbe8> Publitory

    Rails allows us fast prototyping.

  • SmartLogic

    #<User:0x00007fa2e11812e0> SmartLogic

    Rails makes it easy to build out sophisticated Web apps quickly, without re-inventing the wheel for each of our clients. SmartLogic ♥ Rails!

  • AppFriend

    #<User:0x00007fa2f0937318> AppFriend

    Backend business logic

  • Sparta

    #<User:0x00007fa2dee0c670> Sparta

    Backend and API.