Rails 8 is out, and behind the version number lies a shift in philosophy that speaks directly to application owners, not just developers. The thread running through this release comes down to one idea: fewer moving parts. Where a modern Rails application had, in recent years, been stacking up half a dozen external services, Rails 8 folds the essentials back into the framework. In practice, that means a lighter hosting bill, an application that's simpler to maintain, and a foundation that any Rails developer will know how to work on tomorrow. Here's what really changes.
The "Solid trifecta": goodbye Redis
This is the most concrete contribution of Rails 8. For years, any reasonably serious Rails application needed Redis — an extra, in-memory server to handle background jobs, caching and real-time features. Redis works very well, but it's one more building block: to install, secure, back up, monitor and pay for. Rails 8 makes it, in most cases, unnecessary, thanks to three components shipped by default — the Solid trifecta.
Solid Queue handles background jobs (sending emails, generating PDFs, calling external APIs) by relying on your existing database, without Redis. Solid Cache does the same for caching: it stores page fragments and computation results directly in the database, which incidentally lets you keep a far larger cache than you could in RAM, at a trivial cost. Solid Cable, finally, powers real-time features — notifications that appear without reloading the page, live updates — still without any external dependency.
The benefit for a business owner is easy to state: one less server to host and maintain. One moving part that can no longer break on a Sunday evening, one less line on the infrastructure bill, and an application whose architecture now rests on your database alone. The fewer components there are, the fewer things there are to break.
Deployment finally tamed
Getting a Rails application into production was long an art reserved for insiders, or a reason to pay dearly for turnkey platforms. Rails 8 ships with Kamal, a deployment tool that installs your application on any server — a VPS for a few euros a month, your own machine, or several at once — with a single command. It handles containers, zero-downtime deploys and rollbacks if something goes wrong.
Alongside it, Thruster takes on tasks usually delegated to separate front-end servers: compression, caching of static files, automatic HTTPS certificates. Here again, the logic is the same — bringing in-house what previously required third-party tools. For an application owner, this opens the door to hosting far cheaper than managed platforms, without sacrificing the simplicity or reliability of going live.
Built-in authentication, without the bloat
Almost every application needs user accounts: sign-up, log-in, forgotten password. Historically, this went through external libraries — powerful but heavy, often oversized for the actual need. Rails 8 now offers a native authentication generator: a clean, secure, dependency-free login foundation that you spin up with a single command.
It isn't meant to replace the most complete solutions in every case, but for the vast majority of applications it's enough, lighter and easier to evolve. One less dependency, again, and code your provider doesn't have to go decipher inside a third-party library.
Should you migrate, and when?
Let's be honest: if your application runs well on a recent version of Rails, there's no rush to switch for the sheer elegance of it. Rails 8 won't transform your revenue overnight. The real question isn't "is Rails 8 better?" — it is — but "where does my application stand today?".
If you're already behind — a version of Rails nearing the end of its support, a tech stack weighed down by Redis and a handful of external services, expensive managed hosting — then upgrading to Rails 8 becomes an excellent destination. You're not just catching up: you durably simplify the architecture along the way, and you cut your recurring costs. This is precisely the kind of fixed-price upgrade we take on: audit of the existing setup, tested migration, removal of dependencies that have become useless. To see what it would look like for your application, take a look at our resources or our pricing, and let's talk.