Case study

Japan Voyage: four sites, five languages, one Rails app on Rails main and Ruby master

Our own product: one Rails codebase that serves four sites in five languages, with iOS and Android apps, running in production on the development branches of both Rails and Ruby.

The product

Japan Voyage helps people find golf partners, ski partners, travel ideas and a place to live in Japan. It is four public sites, golf, snow, travel and homes (owner-managed rentals and housing guides for foreign residents), plus the portal that ties them together. All of them come from a single Rails application. It also serves this website.

We built it, and we run it. Everything on this page is a decision we made and still live with.

The stack

  • Rails main, the development branch of the next Rails (8.2), with Hotwire (Turbo and Stimulus) and ViewComponent. No separate JavaScript front end.
  • One codebase, four sites. The subdomain picks the site; colours, venues and copy follow from it. Shared features like chat, events, trip planning and profiles are written once.
  • Five languages: English, Japanese, Finnish, and Chinese in both Traditional and Simplified characters, with path-based locale URLs and hreflang on every page. Venue, festival and guide pages also come as Markdown, for AI assistants and search agents.
  • iOS and Android apps built with Hotwire Native, reusing the web screens, with push notifications through Firebase.
  • Real-time chat over ActionCable.
  • SQLite in production, with analytics in a database of its own and continuous backups through Litestream. The Falcon web server, Kamal for deploys, and scheduled jobs from a plain cron file.

The data

  • More than 2,000 golf courses, about 480 ski resorts, more than 1,200 travel destinations, 50 festivals and more than 150 guides.
  • Travel pages are written in all five languages and kept in version-controlled seed files. Our own tooling edits them one value at a time and refuses any edit that adds a defect, such as a missing translation or a mixed date format.
  • When a venue's owner edits their page on the site, the seed keeps the owner's text instead of overwriting it, and tells us which file to update.
  • About 18,000 hotels, ryokan and hostels from OpenStreetMap, imported every month, feed the trip planner's hotel list and the "Where to stay" lists on travel pages. Hotels we have researched ourselves get a page of their own.

Running on Rails main and Ruby master

Japan Voyage runs in production on Ruby master, the nightly build of Ruby's development branch, currently Ruby 4.1 in development with the new ZJIT compiler switched on. It also runs on Rails main rather than a released Rails. We do it on purpose: it shows us how the next Ruby and Rails releases will affect a real application months before our clients upgrade.

It is not free. On 26 August 2026 a change in Ruby master moved the fiber scheduler to a new interface version. The io-event gem, which Falcon depends on, still implemented the old one, so every write under the scheduler spun without making progress. Workers burned 100% CPU, never reported healthy, and five deploys in a row failed.

We found the cause, upgraded io-event to the release that supports the new interface rather than pinning Ruby, and wrote a smoke test that boots a hello-world app under Falcon on a given image. It now tells a Ruby or Falcon boot failure apart from an application failure in under a minute. The same kind of problem is what our upgrade work finds for clients, before it reaches production.

We wrote up the earlier move from Ruby 3.4 to 4.0 in a blog post (in Japanese), and what it would take to run the same application on JRuby in another.

What carries over to client work

  • Multilingual Rails done properly: locale routing, hreflang, sitemaps, translation workflow
  • One codebase for web, iOS and Android with Hotwire Native
  • Small-team operations: SQLite with continuous backups, Kamal, one-command deploys
  • Content kept in the repository, with tooling that checks every edit
  • Early warning on Ruby and Rails changes, from running ahead of them

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.