Working with Ruby on Rails?

Rails app ageing or abandoned? We bring it current.

Most Rails apps that come our way were written quickly, shipped successfully, and then left alone for several years while the business moved on. We pick them up where they are, get the Ruby and Rails versions back onto supported ground, and keep the parts that already work.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

production.log

still failing

What it is

Ruby on Rails at a glance

Ruby on Rails is a web framework for the Ruby language, created by David Heinemeier Hansson and first released in 2004. It follows the Model-View-Controller pattern and popularised convention over configuration, meaning that if you lay a project out the way Rails expects, a great deal of code you would otherwise write by hand is already there.

The framework ships with scaffolding generators, database migrations, the ActiveRecord ORM, ERB templating, and more recently Hotwire, which is Turbo and Stimulus combined to modernise server-rendered pages. It still powers a long list of well-known products, including Basecamp, GitHub, parts of Shopify and some of Stripe's internal systems. Major versions arrive roughly once a year, and official security support is limited to the two most recent.

Type
Ruby web framework
First released
2004
License
MIT
Maintained by
The Rails core team and open-source contributors
Typically used for
SaaS products, startup web apps, internal admin tools, and JSON APIs

The honest version

Ruby on Rails pros and cons

No technology is all upside. This is where Ruby on Rails earns its place and where it tends to cause trouble.

Where Ruby on Rails is strong

  • Convention over configurationIf you follow the naming and layout Rails expects, most of the wiring between routes, controllers, models and views is already done, and a new developer can find their way around a familiar codebase quickly.
  • Productive from day oneGenerators, migrations and sensible defaults let a small team put a working product in front of real users in weeks rather than months, which is why so many startups still reach for it.
  • A mature ecosystem of gemsDevise handles authentication, Sidekiq handles background jobs, Pundit covers authorisation, and Stimulus and Hotwire deliver modern interactivity without a separate JavaScript stack.
  • ActiveRecord is a gold-standard ORMAssociations, migrations, scopes and query composition are expressive enough that most application queries never need handwritten SQL, and the pieces that do are easy to drop in.
  • A genuine test cultureRails has shipped with a testing story since the beginning, and the community around RSpec and Minitest means most serious codebases arrive with a suite worth running.
  • Hotwire modernises server-rendered UITurbo and Stimulus give you page updates, modals and live fragments without maintaining a separate single-page application alongside the Rails code.
  • A strong hiring pool in startupsPlenty of senior engineers have shipped production Rails in the last ten years, and smaller product companies in particular know how to work with it.

Where Ruby on Rails bites

  • The toolchain goes end of lifeRuby, Rails and the gems you depend on all pin to compiler toolchains that eventually stop getting security fixes. Ruby 2.7, Rails 5.2 and Rails 6.0 are all unsupported now, and apps stuck on them have nowhere safe to sit.
  • Monkey-patched gems break between versionsRubygems routinely reach into Rails internals, and a gem that works on one minor version can blow up on the next. Upgrades mean reading changelogs across dozens of libraries, not just Rails itself.
  • ActiveRecord has footguns at scaleN+1 queries, counter cache drift, and lazy loading in templates all silently turn one page view into hundreds of database round trips once the data set grows.
  • Background jobs are their own systemSidekiq or similar needs Redis, a worker fleet, retry policies and monitoring that are separate from the web application, and when it falls behind the symptoms show up in the main app.
  • Multi-major upgrades are weeks of workGoing from Rails 4 to Rails 7 means stepping through 5.0, 5.1, 5.2, 6.0, 6.1 and 7.0 in turn, resolving deprecations at every stop. It is rarely the week-long job people hope for.
  • Experienced Rails hiring is harder than it wasMany developers who learned Rails in its peak years have moved to other stacks, so finding someone to inherit a legacy codebase is noticeably harder in 2026 than it was in 2015.

Sound familiar?

Common Ruby on Rails problems we fix

The Ruby on Rails problems that bring people to us, and what you have once each one is fixed.

Ruby 2.7 end of life

The Ruby version is unsupported

The language the whole app runs on stopped receiving security fixes, and some of your dependencies will not install on anything newer without changes.

Ruby and Rails on supported versions

Rails 5.2 no security patches

The Rails version is years behind

Rails 4 or 5 in production, with each successive major release adding breaking changes that have to be worked through one step at a time.

Upgraded through every intermediate version

ConnectionTimeoutError

The app runs out of database connections

Each Puma worker holds its own pool, background jobs open more, and Postgres hits its limit under modest load.

Pool sized correctly, pooler in front

last commit 14 months ago

The original developer moved on

Repository access is in someone else's name, the deployment steps live in a wiki nobody can find, and nobody is sure how to run the test suite.

Ownership and runbook back in your hands

p95 response 6.4s

Pages are slow to render

N+1 queries from a view partial, missing indexes on foreign keys, and cached fragments that never actually get written.

Pages measured and brought under a second

bundle install fails

The dependencies will not install

A gem pinned to an old native extension, a build toolchain that no longer ships on current operating systems, and a Gemfile.lock nobody has regenerated in years.

Dependencies back on a clean install

Sidekiq retry exhausted

Background jobs quietly fail

Jobs retry up to the limit and then vanish from the dashboard, so emails, invoices or exports stop arriving without an obvious error anywhere.

Dead jobs visible and acted on

What we do

Rails help, from upgrade to upkeep

Call us for one upgrade, or hand us the whole application.

Upgrades
Ruby and Rails moved onto supported versions one step at a time, with the test suite green at every stop.
Takeovers
Inheriting an app from a developer who has moved on. We document, tidy, and get a clean deploy into your name.
Performance
Query tuning, index work, caching and worker sizing, with before and after numbers for the pages that matter most.
Rescue
Down, failing requests, or background jobs piling up. We put the app back in service first, then trace which gem or query caused the stall.
Feature work
New features and integrations built the Rails way, so the next person to touch them is not lost.
Managed Tech
Monitoring, patching, backups and a team to call on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Ruby on Rails alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Ruby on Rails questions

Something else? Call+1 737 727 7327

Can you upgrade our Rails 4 or 5 application to Rails 7 or 8?

Yes, this is routine work for us. We step the application through each intermediate major version in turn, resolving deprecations and gem incompatibilities at every stop, and we keep the test suite green between releases rather than at the end.

Can you take over a Rails app from a developer who moved on?

Yes. We take the repository as it stands, get it running locally and in a staging environment, document what is there, move hosting and secrets into your name, and from that point the app is something your business owns rather than something only one person could touch.

Why does our Rails app run out of database connections?

Each Puma or Unicorn worker holds its own connection pool, and Sidekiq processes hold more on top of that. Multiply the pool by the number of workers and the total often sits above what the database allows, so the answer is usually a pooler such as PgBouncer and a corrected pool size rather than a bigger database plan.

How do we speed up slow pages in our Rails app?

Most slow Rails pages come down to the same handful of causes, which are N+1 queries from a view partial, missing indexes on columns used in joins and where clauses, fragment caches that were written but never read, and views that render far more data than the user actually sees.

Should we rewrite our Rails app or keep upgrading it?

Almost always, keep upgrading it. A working Rails codebase represents years of product decisions, and a rewrite throws them away alongside the bugs. We only recommend a rewrite when a specific section of the app would genuinely cost less to replace than to maintain, and we show you the reasoning before any code is touched.

How much does Rails help cost?

Estimates are free. Describe the application and what is going wrong, and you get a price before any work starts.

Free estimate

Rails app giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.