Fast Ruby updates
Run the new Ruby the week it comes out, and apply security releases in days. We test against previews and Ruby master ahead of time, so release day is a version bump, not a project.
Why fast updates matter
A new Ruby version is easiest to adopt in its first weeks. The changes are fresh and documented, gems are releasing compatible versions, and you only have one step to take. Leave it a year or two and the same work becomes a project, often started in a hurry when a version stops getting security fixes.
The work is mostly the same every year. The difference is whether you find the breakage in November, on a preview, or in the spring, in production.
How we work
- Test early. We add the next Ruby's preview and Ruby master to your CI, next to the version you run now. Breakage shows up months before the release, one change at a time.
- Fix ahead. We fix what we can on your current version, so the code runs on both, and report problems in gems upstream.
- Images ready. We prepare the Docker image for the new Ruby. If the official image is not out on release day, we build from the Ruby core team's images or compile Ruby from source, so the release date is yours to choose, not the image's.
- Release day. Change the version, deploy, watch. Most of the time it is that small, because the work was done before.
Fast builds, too
A fast update needs a fast build. A new Ruby version recompiles every gem with a native extension, and on Ruby master they may need rebuilding after any nightly build. We set up the build so that only what changed is rebuilt: compiled gems cached per Ruby version, a build cache that survives between deploys, and a separate stage for system libraries so they are not rebuilt with every Ruby. That way a Ruby update does not make every deploy slow.
Why us
Japan Voyage, our own product, runs in production on Ruby master, the development branch of Ruby, from the Ruby core team's nightly image. We get each change to Ruby the week it lands, months before a release.
It is not free, and we know exactly what it costs. In August 2026 a change to Ruby's fiber scheduler interface on master stopped our web server from booting, and a deploy failed. We traced it to a gem the server depends on, upgraded that gem, and kept running master. We also wrote a small check that boots a hello-world app on the new image, so the next time a deploy hangs we can tell a Ruby problem from our own in about a second. That is the work this service does for you, one release ahead of when it matters.
We also work on Ruby itself. Sampo Kuokkanen has merged changes into ruby/ruby, ruby/spec and JRuby. We wrote up one upgrade in detail: moving a Rails 8.1 application from Ruby 3.4 to 4.0 (in Japanese).
What you get
- CI that tells you what the next Ruby breaks, months before it is released
- Docker images for the new Ruby on release day, built from source if they have to be
- Your application on the new Ruby within a week of the release
- Ruby security releases applied within days on the monthly plan
Pricing
Prices in US dollars, before tax. A price marked "from" is the minimum; we agree a fixed price before we start, and invoices in yen are fine.
Release check
$800
fixed price, about two days
We run your test suite and boot your application on the next Ruby's preview or release candidate and on Ruby master, and write down everything that breaks, with a fix for each and a plan for release day.
Release-week upgrade
from $1,500
fixed quote after the check
Your application on the new Ruby within a week of its release: Gemfile and lockfile, CI, Docker images, gems with native extensions, and the deploy itself.
Ruby master watch
from $300
per month
Your CI runs nightly against Ruby master and the current previews. We fix what breaks as it breaks, and apply Ruby security releases within days.
Frequently Asked Questions
- When do new Ruby versions come out?
- A new Ruby version comes out every year on 25 December; Ruby 4.0 was released on Christmas 2025. Previews and a release candidate come out in the months before it, and security releases for the supported versions come out whenever they are needed.
- Why upgrade so soon? Isn't it safer to wait?
- Waiting feels safer, but it adds up. Each skipped version makes the next upgrade bigger, gems move on to the new Ruby, and a security fix is easiest to apply when you are already on a current version. Testing against previews before the release takes the risk out of upgrading early: by release day you already know what breaks.
- The official Docker image for the new Ruby is not out yet. What then?
- There are two ways round it. The Ruby core team publishes its own images (rubylang/ruby), including nightly builds of master, and we can build on one of those. Or we compile that Ruby from source in your Dockerfile: download the release tarball, build it in a build stage and copy it into the final image. Either way you are not waiting on anyone, and once the official image is published, switching back is a one-line change.
- What breaks most often on a new Ruby?
- Gems more than application code. Gems with C extensions have to be compiled for each new Ruby, and some only publish precompiled binaries for versions that existed at their last release, so on a new Ruby they are built from source and need a compiler and the right system libraries in the image. After that come deprecations that became errors and changes to the standard library, such as gems that moved out of it.
- Do you also handle Ruby security releases?
- Yes. A security release of Ruby is a patch version (3.4.x, 4.0.x), so it rarely breaks anything, but it still has to be built, tested and deployed. On the monthly plan we apply it within days. Our guide to Ruby and Rails security updates explains the support periods: https://sampo.ltd/blog/ruby-rails-security-updates
- Our application is several Ruby versions behind. Is this the right service?
- Start with the Rails and Ruby upgrade instead: it brings an old application up to date step by step. Once you are current, this service keeps you there.
Tell us about your project
Send a few lines about your application and what you need. We reply within two business days, in English or Japanese, with next steps and a rough estimate.
Other services
Rails and Ruby upgrades
Move an old Rails application to current Rails and Ruby step by step, without a rewrite and without stopping feature work. We start with a fixed-price roadmap.
Upgrade roadmap: $1,500
Ruby on Rails development
Ruby on Rails development at a fixed price: a first version of a new application, one feature, a fix, or monthly maintenance.
Feature or fix: from $1,000
Code audit and second opinion
An outside review of your Rails codebase, or of a proposal you have been given, written up in plain language so you can decide what to do next.
Second opinion: $500