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
Working with Ruby on Rails?
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.
What it is
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.
The honest version
No technology is all upside. This is where Ruby on Rails earns its place and where it tends to cause trouble.
Sound familiar?
The Ruby on Rails problems that bring people to us, and what you have once each one is fixed.
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 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
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
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
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
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
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
Call us for one upgrade, or hand us the whole application.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
Estimates are free. Describe the application and what is going wrong, and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: