Need to upgrade
Rails but don't
have the time?
Let the experts at FastRuby.io upgrade your application
FastRuby.io is a specialized Rails upgrade service. We have worked alongside teams from 1 to 100 people, upgrading applications without interrupting product development.
Whether you’re stuck on 2.3 or want to prepare for 6.2, we’ve seen it all before and know the best approaches. We’ve fixed thousands of old dependencies and evaluated countless migrations
Our years of upgrade experience means you can hand over the work to us, freeing up your developers to concentrate on shipping new features.
FastRuby.io, over 80 apps upgraded since 2012
You’re probably in the same situation as many other companies. You keep meaning to upgrade to Rails 6.2, but new features take priority and the project always gets pushed back.
That’s why we created FastRuby.io. Our core service is upgrading applications like yours onto a secure, supported version of Rails.
We can integrate with your team and adapt to your environment, updating your application without distracting you from your product timeline.
So, why us?
We have upgraded over 80 applications ranging from MVPs to 500,000 line monoliths, worked with every version from 2.3 to 6.1 and coordinated with companies ranging from small startups to Fortune 500s.
As upgrade specialists we are constantly refining our workflows, keeping up with the latest Rails developments, and sharing our recipes.
We also maintain a range of open-source tools to help people DIYing their upgrades, such as next_rails, bundler-leak and skunk.
When working with us you will get:
A new branch where the updates are made and rebased as much as necessary to avoid interruptions.
Advice for your developers about future API changes and the possibility of performance optimizations.
Contributions to any of your open source dependencies that aren’t compatible with your required version of Rails.
Help to assess and choose migration options, such as ActiveStorage vs. Shrine.
You need proven experts to ship your upgrade
You can read about some of our past upgrade projects in our case studies, such as upgrading a large app from 5.0 to 5.1 or taking an app all the way from 2.3 to 4.2.
Or see what our past clients say about us:
- Slide 1
- Slide 2
- Slide 3
“The FastRuby.io team executed a full upgrade of our application from Rails 4.0 to 5.1, including preparation for an eventual 5.2 upgrade. The team adapted to our environment and kept a clear focus on the goal, resisting the temptation of feature-type distractions. Their effort allowed us to keep up to date with Rails versions without detracting from progress on other goals.”
Ben Langfeld, Solutions Architect at Power HRG
"In addition to producing high quality code they also suggest improvements to our development processes and mentor our new engineers."
Preston St. Pierre, CTO at Predictable Revenue
"The FastRuby.io team exceeded our expectations. They went above and beyond and tried to help out even when the contract was up. They were willing to integrate with our team, and worked with the Junior Developer on our team to get to full productivity."
Will Bridges, Director of Engineering at Storenvy
Assessing the work required
A Rails upgrade can take anywhere from a few days to over a year. It depends on your whether your codebase requires work such as:
Fixing hundreds of Deprecation Warnings
Replacing many incompatible dependencies
Migrating to Webpacker
So it’s hard to assess what’s required in terms of allocated dev time or the budget for outsourcing.
If you’re considering doing it yourself then you can download our free eBook: The Complete Guide to Upgrade Rails. Yes, we actually wrote the book on Rails upgrades!
We start most projects with an audit. We comb through every line of code and dependency to create The Roadmap, a report detailing all the work your codebase requires.
Once clients are on the latest Rails version, we then help them prepare for the next release through our Stay Up To Date service.
Change is hard, but we can help get your developers up to speed with newer versions of Rails. As we rebase your changes into the Rails upgrade branch, we will flag out of date code and notify your developers in order to resolve the conflict.
Well, that is a real problem. We can't upgrade your Rails application if you don't have a decent test suite. We require clients to have at least 80% test coverage in their applications unless they have a dedicated QA team. We use the build to check expected behavior for current code.
We can help you write your test suite, but that's a totally different service. If you're interested, send us a message using the OmbuLabs contact form.
An upgrade can take anywhere from a few days to over a year depending on a range of factors. The only way to even estimate it is to go through your codebase and gems.
If you need this number to request the necessary budget or any other reason, then check out The Roadmap.
Finally get your upgrade sorted
Whether you’re a few versions behind, need help prepping for 6.2 or would like an audit, we can have a call to talk through your situation.We should talk!