It's about time you upgrade your Rails version

I'm ready. Let's talk!

You need to upgrade Rails to patch security vulnerabilities, use the latest features, and get the latest performance improvements.

You know you need to upgrade Rails, but you just don't have the time or people to solve this problem today.

You know Rails 5.1 (and even Rails 4.2!) is more performant than 3.0 and that Rails 3.2 is no longer supported by the community.

But hey, you have a big release coming up, and you really, really need to get these features out next week.

So you can't upgrade Rails just now. But maybe in the future...

But next week you have to start a new sprint. And your application keeps getting more and more out of date.

Not to mention the security risks that keep piling up.

As the Rails maintainers release more features, you continue to lag behind (now Rails 5.1 is out!)

We know how it goes. We have been there ourselves with our own products.

You want to upgrade. You know you need to upgrade, like, yesterday.

But you just don't have the time or people to do it right now.

Here is the truth: Rails upgrades are hard!

And you know a new version is just around the corner.

So you know you have a problem. You know you don't have the time or people to fix it just now, but you have the budget to solve the problem.

Now picture a world in which your team gets to stay productive and you get the set of changes you need to upgrade your Rails application.

In this world your technical stack is up to date with the latest security patches, performance improvements, and useful new features.

Here is the great news: we can upgrade your Rails application while your developers focus on shipping new features and critical bug fixes.

That's why we created, to take you from an out-of-date to an up-to-date tech stack with a fast, cost-effective, and reliable productized service.

At Ombu Labs we focus on Rails upgrades with minimal disruption. We can easily plug into your project and start upgrading Rails and its dependencies from day 1.

We just need a few things from you:

Our team of software engineers who are specialized in Ruby upgrades will work on your Rails upgrade without disrupting your team.

So, why us?

We have been upgrading Rails applications since 2009 and we are used to working with agile teams in rapid development environments.

You will get help from experienced developers who specialize in Rails upgrades, long-term support, and performance optimization.

We have done this before and we have shared articles about our experience. Feel free to check out some of our latest articles or open source contributions.

So, how does it work?

  1. We do an initial call to make sure this is a good fit. You tell us about your project, test coverage, software development process, current and target version.
  2. We sign an NDA. You give us access to your code. We take a look and decide to move forward. We send you an estimate for the Rails upgrade project.
  3. You approve our estimate and decide to move forward. We start upgrading your app one version at a time. We rebase your changes into our Git branch as much as needed to make sure we don't have conflicts at the end of the project.
  4. We use your test suite to make sure we don't break anything in the process. We apply our secret sauce, make progress, and finally get to your target Rails version. The build passes and we do our own code review.
  5. We submit a pull request to your project. Your team reviews our changes, asks questions, makes suggestions, and we improve our pull request based on your feedback.
  6. Once the pull request is approved, we deploy to your staging environment. You test that everything works as expected and approve our work.
  7. You merge the Rails upgrade into your stable branch and deploy to production. Your users can take advantage of the latest version of Rails.

So, what do you get when you hire us?

You will get a pull request with the set of changes needed to bring your Rails app up to speed. It doesn't matter whether it's a huge Rails monolith or a tiny minimum viable product.

On top of that, you will get a free code quality report. We use static code analysis, the twelve-factor methodology, workflow analysis, and software engineering best practices.

You will get a 1-month warranty for the changes we introduced. If our upgrade introduced any bugs, we will fix them free of charge.

Finally you will be able to take advantage of the latest version of Rails.

If you've gotten this far, we should talk!

Let me see if I can guess what you're thinking right now:

"But we update our stable branch too fast for you to keep up..."

We have worked with extremely active teams in the past. You just tell us which branch to use. We will branch off and rebase as much as necessary (and not more than that).

"But our developers are used to Rails 3..."

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.

"But I don't have tests in my project..."

Well, that is a real problem. We can't upgrade your Rails application if you don't have a decent test suite. We expect our clients to have at least 80% test coverage in their applications. 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, just send us a message via the Ombu Labs contact page.

"But I don't know what my test coverage is..."

You can easily calculate it by using simplecov. Here is a step by step tutorial to generate a test coverage report. You should run it before you contact us.

"But we don't have the budget just yet..."

I completely understand - money doesn't grow on trees for any business. But think about this: How much money would you lose if any of those known security issues got exploited?

The price for our Rails upgrades depends on the size of your application and the number of sprints needed to complete the project. It may be more affordable than you think!

"Just shut up and take my money! How long does it take?"

It depends on the size of your project and the number of version jumps. If we are taking your app from Rails 5.0 to 5.1 and you have a simple application, it could take one week.

If we are taking your app from Rails 2.3 to 5.1 and your application is a huge monolith, it could take up to eight weeks.

But don't take our word for it. Just read what our happy customers have to say.

Take advantage of Rails' latest features, performance upgrades, and security patches

Let's talk!


We'll take a look at your app and send you an upgrade plan completely free of charge.