Web Development

Ruby on Rails in 2026: is it still a good choice?

8 min readBy Sandeep Mahajan

A red gem resting on a model railway track beside a laptop

Yes, for many business web applications Ruby on Rails is still a good choice in 2026. It is actively maintained (Rails 8.1.4 was released on 24 September 2026), it ships with most of what a typical app needs, and Rails 8 made it simpler to run on your own servers without a pile of extra services. The trade-offs are real: a smaller hiring pool than JavaScript or PHP, a short support window per version that means regular upgrades, and less fit for CPU-heavy or very low-latency work.

Key takeaways

  • The current release is Rails 8.1.4 (24 September 2026). The 8.1 and 8.0 series are the only ones that still get fixes.
  • Rails gives each minor series one year of bug fixes and two years of security fixes from its first release, so plan an upgrade at least every year or two.
  • Rails 7.2 received its last release, 7.2.4, on 24 September 2026; Rails 7.1 and 7.0 reached end of life in October 2025.
  • Rails 8 added a built-in deployment tool (Kamal 2), database-backed queue, cache and WebSocket adapters, and an authentication generator.
  • Rails suits data-driven business applications, admin-heavy products and small teams who want one framework for the whole app.

What is the current Rails version and how long is it supported?

The latest release is Rails 8.1.4, published on 24 September 2026. Rails 8.1 itself arrived on 22 October 2025, with job continuations, structured event reporting and a way to run your CI checks locally. No Rails 8.2 or 9.0 beta had been published as of 29 October 2026.

The official maintenance policy on rubyonrails.org says minor releases receive bug fixes for one year and security fixes for two years after the first release in the series. The team aims for a feature release every six months, and if no release happens within a year, support for the previous release is extended until the next one ships. The supported table as of 29 October 2026:

Series Bug fixes until Security fixes until
8.1.x 10 October 2026 10 October 2027
8.0.x 7 May 2026 7 November 2026

The 8.0 bug-fix window was extended by six months in October 2025. Everything older is unsupported:

Series Status
7.2.x Last release 7.2.4 on 24 September 2026; fixes now only for 8.0 and 8.1
7.1.x End of life, announced 29 October 2025 (final release 7.1.6)
7.0.x End of life, announced 29 October 2025 (final release 7.0.10)
6.x, 5.x and older End of life

For unsupported series, the policy is that users are responsible for bugs and security issues; fixes may appear in git, but no new versions are released. So if your app still runs Rails 5, the version the original 2016 version of this post celebrated, it has gone years without official patches.

What changed in Rails 8 that matters to a business?

Rails 8.0, released on 7 November 2024 under the banner "No PaaS Required", aimed to make it practical to deploy and run an app on ordinary servers:

  • Kamal 2 and Thruster. Rails 8 "comes preconfigured with Kamal 2 for deploying your application anywhere", and Thruster sits in front of the Puma app server to handle asset caching and compression, so a separate Nginx layer is often not needed.
  • Solid Cable, Solid Cache and Solid Queue. Database-backed adapters for WebSockets, caching and background jobs. For many apps this removes the need to run Redis or a separate job system.
  • Authentication generator. bin/rails generate authentication creates a basic session-based login with User and Session models.
  • Propshaft became the default asset pipeline for new apps.

Rails 8.1 followed with Active Job continuations (long jobs can resume from their last completed step after a restart), a structured event reporter, local CI defined in config/ci.rb, Markdown responses from controllers, and registry-free deploys with Kamal.

For a business, the practical result is fewer moving parts to host and pay for, and fewer separate services to keep patched. Whether that matters depends on your setup: a team already happy on a managed platform may not change anything.

What are the honest strengths of Rails?

  • Speed of building standard business features. Database models, forms, validations, email, file uploads, background jobs and real-time updates all come in the box, with conventions that mean less decision-making per feature.
  • One framework for the whole app. Rails ships with Turbo, and import maps are the default for JavaScript from Rails 7, so a small team can build interactive screens without a separate JavaScript front end. API-only mode is still there when you do want a separate mobile app or front end.
  • Mature, stable ecosystem. Rails has been in active development for about two decades (the official blog's release posts go back to 2005), and its gems cover payments, admin panels, search and authorisation.
  • Clear upgrade guidance. The official upgrading guide gives a repeatable process and generates a file of new framework defaults you can switch on gradually.
  • Good fit with PostgreSQL and other common databases, and deployable with Docker-based tooling.

What are the trade-offs?

  • Hiring and handover. Ruby is a less common language than JavaScript, Python or PHP, so it can be harder to find developers locally or replace a departing one. Check the market where you hire before committing.
  • Upgrade cadence. With one year of bug fixes and two years of security fixes per series, you need a budget for upgrades every year or so. Skipping several versions makes each upgrade bigger.
  • Ruby version churn. Rails 8.0 and 8.1 require Ruby 3.2 or newer, but the Ruby project lists Ruby 3.2 as end of life since 1 April 2026, so in practice plan for Ruby 3.3 (security maintenance until an expected 31 March 2027), 3.4 or 4.0, checking each gem's compatibility.
  • Performance profile. Rails handles typical web traffic well with sensible caching and background jobs, but CPU-heavy processing, very low-latency services or heavy concurrent connections may be better served by another language for that part of the system.
  • Convention over configuration cuts both ways. It speeds up teams who follow the Rails way, and slows teams who fight it.

When is Rails a good choice, and when is it not?

Rails fits well Consider something else
Data-driven web apps: portals, SaaS products, marketplaces, internal tools Mostly static marketing sites, where a static or headless setup is simpler
Small teams that want one framework end to end Teams whose skills are all in JavaScript or PHP
Products where the admin and back office matter as much as the front end CPU-heavy or real-time workloads at very large scale
An existing Rails app with good tests, where an upgrade is cheaper than a rewrite Projects that cannot budget for yearly framework upgrades

If you are comparing stacks, our guide to choosing a tech stack for a web or mobile app covers the questions to ask, and our article on Laravel in 2026 is a useful comparison point for a PHP team.

How do I upgrade an old Rails app?

The official upgrading guide recommends this order:

  1. Get test coverage first. "The best way to be sure that your application still works after upgrading is to have good test coverage before you start the process."
  2. Upgrade Ruby first, to the newest version you can, then Rails.
  3. Move one minor version at a time: go to the latest patch of your current series, fix failures and deprecation warnings, then move to the next minor version (7.0, 7.1, 7.2, 8.0, 8.1).
  4. Run bin/rails app:update at each step and review the changed files.
  5. Adopt new defaults gradually using the generated new_framework_defaults file, then update config.load_defaults.

An app on Rails 5 or 6 has several steps to climb, and some gems along the way may be abandoned and need replacing. Our Ruby on Rails development team can assess an existing app and plan the steps. If the app is being rebuilt anyway, our website redesign and migration service covers moving content and data safely.

FAQ

Is Ruby on Rails dead in 2026?

No. Rails 8.1.4 was released in September 2026, and the project publishes security and bug-fix releases on a published maintenance policy.

What is the latest Rails version?

Rails 8.1.4, released on 24 September 2026. Check rubyonrails.org for anything newer.

Is Rails 7 still supported?

No. Rails 7.0 and 7.1 reached end of life in October 2025, and 7.2.4 was announced as the last 7.2 release, with fixes now only provided for 8.0 and 8.1.

How often do I need to upgrade a Rails app?

Plan for at least one minor upgrade a year. Each series gets bug fixes for one year and security fixes for two years.

Which Ruby version should I use with Rails 8?

Rails 8.0 and 8.1 need Ruby 3.2 or newer, but 3.2 is end of life, so use a maintained Ruby (3.3, 3.4 or 4.0) that your gems support.

Is Rails good for building an API for a mobile app?

Yes. Rails has an API-only mode that generates a slimmer app aimed at serving JSON.

Sources (13 links)
Share this article