Browse categories
Explore
Fiverr Pro
English
$
USD
I will upgrade your legacy ruby on rails app to rails 8 and fix its bugs
Andrew Kwak
About this gig
Stuck on an old Rails version, with red tests and gems that will not install? We fix the bugs first, then upgrade your app one version at a time to Rails 8, so nothing breaks on the way.
Every order starts with a health check you keep
- Rails and Ruby versions, outdated or abandoned gems, failing tests, security warnings
- - A written upgrade plan, useful even if another developer does the work
What you get
- Bugs, failing tests and broken deploys fixed
- - One version step at a time, deprecations cleared before the next step
- - Pull requests on a separate branch, tested on staging. Nothing goes live until you merge
- - A short report of every change
Rails 7.2 and older no longer receive security fixes. A supported version is the simplest way to stay patched.
Rails 5.2 and newer, PostgreSQL or MySQL, Sidekiq, Redis, Hotwire or React, on Heroku, Render, Fly.io, AWS or your own server.
Dearnode is led by an IEEE Senior Member and has built Ruby on Rails apps since 2017.
Message us your Rails version before ordering and we confirm which package fits.
Ruby logo (c) 2006 Yukihiro Matsumoto, used under CC BY-SA 2.5.
Get to know Andrew Kwak
Andrew Kwak
Web apps, booking systems and automation
- FromUnited States
- Member sinceSep 2026
Languages
Korean, English
We are Dearnode, a software studio building web apps, booking and payment systems, automations and Mac and iOS apps for businesses in Australia, Korea and the US since 2017. Our Mac app Orbit was #7 Product of the Day on Product Hunt, and our sleep app The Sleep reached users in 41 countries, with our patent cited as prior art in five Apple patent documents. We start with a written spec, show a working demo every week and hand over the full source code.
FAQ
What size of app fits these packages?
Apps up to about 40 database tables. Moving the front-end build (e.g. Webpacker to importmap or jsbundling) is quoted separately. For larger apps, start with the health check and we quote the rest from it.
My app has few or no tests. Can you still upgrade it?
Yes. The top package adds smoke tests for your key flows before upgrading, so we can show nothing broke. On the 2-version package, thin coverage means more manual checks, and we flag that in the health check.
Will my app go down during the upgrade?
No. We work on a separate branch and a staging copy. You review the pull request and deploy when you are ready, or add release-day deploy support and we deploy with you.
What about gems that are no longer maintained?
The health check lists them. For each one we suggest a maintained replacement, a small piece of your own code or a patch, and agree the choice with you before changing anything.
Can you upgrade apps older than Rails 5.2?
Often, yes, but they need more steps and more checks. Message us your Rails and Ruby versions before ordering and we quote after the health check.
Do you need my production database?
No. A staging copy or anonymised data is enough. Error logs and your error tracker (e.g. Sentry or Honeybadger) help us find bugs faster.
What counts as one fix?
One error, failing test or broken deploy with a clear cause. If a fix turns into rebuilding a feature, we tell you before starting and quote it separately.
