01
SaaS products
Multi-tenant Rails apps with accounts, roles, billing hooks and admin screens, built on Rails 8.1 and PostgreSQL.
FIG 01 · Ruby on Rails Development
Ruby on Rails development services, from new Rails 8 apps to overdue upgrades
New Rails 8 apps with Hotwire, Solid Queue and Kamal deployment, upgrades that move Rails 6 and 7 apps back onto supported versions, and Rails developers who join your team.
See how it works
FIG 02 · Quick answer
What do Ruby on Rails development services include?
Ruby on Rails development services cover building, upgrading and maintaining web apps on the Rails framework. Elgrith builds Rails 8 apps with Hotwire, Solid Queue and Kamal deployment, upgrades older Rails and Ruby versions before security support ends (Rails 8.0 support ends on 7 November 2026), and supplies dedicated Rails developers.
- New builds start on Rails 8.1, the current release series
- 8.1
- Projects delivered since 2015
- 1,000+
- Clients across the USA, UK and India
- 250+
- Your code, repository and IP
- 100%
FIG 03 · Why it matters
Rails 7.2 lost security fixes in August. Rails 8.0 follows on 7 November.
From the Rails maintenance policy, endoflife.date and the Ruby branches page, read on 23 Oct 2026.
01
7 Nov 2026
Rails 8.0 security support ends
Rails releases get “security fixes for two years after the first release in its series”. Rails 8.0 shipped on 7 Nov 2024, so its security fixes stop on 7 Nov 2026. Bug fixes already ended on 7 May 2026.
Source: Ruby on Rails, maintenance policy (read 23 Oct 2026)(opens in a new tab)02
9 Aug 2026
Rails 7.2 went out of support
Rails 7.2’s security support ended on 9 Aug 2026. Rails 7.2.4, released on 24 Sep 2026, is the last 7.2 release. Rails 7.1 and older were already unsupported.
Source: endoflife.date, Ruby on Rails (read 23 Oct 2026)(opens in a new tab)03
1 Apr 2026
Ruby 3.2 reached end of life
Ruby 3.2 is end of life and Ruby 3.3 now gets security fixes only, with end of life expected on 31 Mar 2027. Ruby 4.0 (25 Dec 2025) and 3.4 are in normal maintenance.
Source: ruby-lang.org, Ruby maintenance branches (read 23 Oct 2026)(opens in a new tab)
FIG 04 · Version check
Is your Rails version still supported?
Check the rails gem in your Gemfile.lock and the Ruby version in .ruby-version, then find them below. Once security support has ended, new vulnerabilities in that version are not patched.
| Version | Status, 23 Oct 2026 | Support ends | What to do |
|---|---|---|---|
| Rails 8.1 | Current series (8.1.4, 24 Sep 2026); bug-fix window listed until 10 Oct 2026 | Security fixes until 10 Oct 2027 | New builds start here |
| Rails 8.0 | Security fixes only | 7 Nov 2026 | Upgrade to 8.1 now |
| Rails 7.2 | Unsupported; 7.2.4 was the last release | Ended 9 Aug 2026 | Upgrade to 8.0, then 8.1 |
| Rails 7.1 and older | Unsupported | 7.1 ended 1 Oct 2025; 7.0 on 1 Apr 2025; 6.1 on 1 Oct 2024 | Upgrade one minor version at a time |
| Ruby 4.0 | Normal maintenance (released 25 Dec 2025) | To be announced | Target for new builds once your gems support it |
| Ruby 3.4 | Normal maintenance | To be announced | Safe target for upgrades |
| Ruby 3.3 | Security maintenance only | 31 Mar 2027 (expected) | Plan the move to 3.4 or 4.0 |
| Ruby 3.2 and older | End of life | 3.2 ended 1 Apr 2026 | Upgrade alongside Rails |
Sources: rubyonrails.org/maintenance, endoflife.date/rails, the Rails blog and ruby-lang.org, all checked 23 Oct 2026. With the 8.1 bug-fix window passed and no Rails 8.2 released yet, check rubyonrails.org/maintenance for the current bug-fix status; this table is updated when 8.2 ships.
Budgeting the work? Our 2026 custom software development cost guideFIG 05 · What you get
Ruby on Rails development company: what we build
Rails is at its best when a small team needs to ship a lot of product. These are the apps we build on it, from the first migration to the support after launch.
02
Marketplaces
Buyer and seller flows, listings, search, messaging and payouts, with Active Record models designed for growth.
03
MVPs
A first release of the core journey, fast, using the Rails 8 authentication generator and conventions instead of custom plumbing.
04
Internal tools and admin panels
Back-office apps with forms, tables, approvals and reports, where Rails conventions save the most time.
05
APIs in Rails API mode
JSON APIs for mobile apps and front ends, with versioning, token auth and documentation.
06
Hotwire front ends
Turbo and Stimulus for fast, server-rendered interfaces that feel like a single-page app, without a separate JavaScript front end.
07
React or Vue front ends
A Rails back end behind a React or Vue app when the interface needs it, with shared conventions for auth and errors.
08
Background jobs and real-time features
Solid Queue or Sidekiq for jobs, Action Cable or Solid Cable for live updates, with retries and monitoring.
Deliverables
11
deliverables, in writing
Included in every build, written into your fixed quote before work starts.
FIG 06 · Upgrade path
Rails upgrade services
Rails upgrades go wrong when they jump several versions at once. We audit first, add tests where they are missing and move one minor version at a time, so the app stays deployable at every step.
1. Audit
- Check
- Rails, Ruby, every gem and its maintenance status
- Find
- Abandoned gems, monkey patches and deprecated APIs
- Output
- A written upgrade plan in your fixed quote
2. Test coverage
- Measure
- What your RSpec or Minitest suite actually covers
- Add
- Tests around sign-up, checkout and the journeys that earn money
3. One minor at a time
- How
- 6.1 → 7.0 → 7.1 → 7.2 → 8.0 → 8.1, never a big jump
- Why
- Each step’s deprecation warnings point to the next step’s breaks
4. Ruby alignment
- Move
- Ruby 3.2 or older to 3.4 or 4.0, at the step your gems allow
- Check
- Native extensions and gem compatibility
5. Deprecations and defaults
- Fix
- Each deprecation, then switch on the new framework defaults
- Optional
- Sprockets → Propshaft, Redis → Solid Queue and Solid Cache
6. Deploy and watch
- Release
- Staged deploy with a rollback ready
- Then
- Error and performance monitoring, and an upgrade calendar
FIG 07 · Rails 8
What’s new in Rails 8
Rails 8 was announced on 7 Nov 2024 as “no PaaS required”: fewer moving parts to run, and a deploy story built in. Rails 8.1 followed on 22 Oct 2025.
06principles
Solid Queue, Solid Cache, Solid Cable
Jobs, caching and WebSocket pub/sub backed by your database. The Rails team says Solid Queue “replaces the need for not just Redis” but a separate job framework too.
Kamal 2 and Thruster
Rails 8 comes preconfigured with Kamal 2 to deploy to your own servers, and Thruster, a proxy in front of Puma, for caching and compression.
Authentication generator
bin/rails generate authentication gives you Session and User models and the controllers to sign in, a reviewed starting point instead of a custom one.
Propshaft
Propshaft is the new default asset pipeline, simpler than Sprockets. We move apps across when it fits their front end.
Active Job Continuations (8.1)
Long-running jobs split into steps, so after a restart or deploy they continue from the last completed step, not from the beginning.
Local CI (8.1)
A CI declaration in config/ci.rb, run by bin/ci, so the same checks run on a laptop and in your pipeline.
FIG 08 · Consulting
Ruby on Rails consulting and code audits
For a Rails app that is slow, fragile or about to change hands. You get a written report with findings ranked by risk, and a fixed quote for the fixes if you want us to do them.
06principles
Performance
N+1 queries, missing indexes, slow endpoints and memory growth, found with profiling and query logs, not guesses.
Security
Brakeman static analysis, gem vulnerability checks, auth and permissions review, and secrets handling.
Background jobs
Sidekiq or Solid Queue set-up, retries, idempotency and queues that back up under load.
Architecture and code health
Fat models, callback chains and service objects reviewed, with a refactoring plan you can follow in sprints.
Upgrade readiness
How far your app is from Rails 8.1 and Ruby 3.4, and the order to get there.
Hosting and deploys
PaaS costs, Kamal or container deploys, and CI pipelines that catch problems before production.
DevOps consulting
FIG 09 · Hire
Hire Ruby on Rails developers
Dedicated Rails developers who join your stand-ups, work in your repository and follow your review rules, managed from our New Delhi HQ. Every developer is vetted on a Rails code exercise and a review of real pull requests before you interview them.
04principles
Dedicated Rails developer
One full-time developer on your Rails product, in your tools and your sprint.
Rails team extension
Developers, a tester and a lead added for a release, an upgrade or a backlog.
Fixed-scope project
A defined app, feature or upgrade for a fixed quote, delivered in sprints with weekly demos.
How dedicated teams work
Interviews, onboarding, replacements and hand-over, explained.
Hire dedicated developers
FIG 10 · Decide
Is Rails right for your project?
Rails fits database-backed web products where speed of delivery matters more than squeezing every millisecond: SaaS, marketplaces, MVPs and admin-heavy apps. It is a weaker fit for CPU-heavy services, very high-concurrency real-time systems or teams that want one language from browser to server.
04principles
Rails or Django?
Both are mature, batteries-included frameworks. Django wins when the product leans on Python’s data and AI libraries.
Python and Django developmentRails or Node.js?
Node.js fits real-time features and teams that want JavaScript end to end.
Node.js development
FIG 11 · Process · 6 steps
Build it on Rails 8, keep it supported
A fixed written quote after a free call, sprints with weekly demos, and an upgrade calendar so your Rails and Ruby versions never drift out of support. You own the code and IP.
- Step 01
Free call
Tell us what you are building or what is breaking. We ask about users, data, integrations and deadlines, not just the framework.
- Step 02
Code or idea review
For a new app: users, data model, integrations and whether Hotwire or a separate front end fits. For an existing app: Rails, Ruby and gem versions, test coverage and the upgrade path.
- Step 03
Fixed written quote
A written scope, a fixed quote and the plan for versions, hosting and hand-over, before any work starts.
- Step 04
Sprints with weekly demos
Sprints in your repository, with pull requests you can read, tests and Brakeman in CI and a demo on staging every week.
- Step 05
Launch
A planned release with Kamal or your existing pipeline, migrations rehearsed on staging and a rollback ready.
- Step 06
Support and upgrades
Rails and Ruby security releases applied in a patch window agreed in your written scope, plus planned upgrades before your versions lose support.
FIG 12 · What you get
Everything included
Written into your fixed quote, so you know exactly what you are paying for before work starts.
11items
- Written scope and fixed quote
- Version and gem audit for existing Rails apps
- Rails 8.1 app or upgraded app in your repository
- PostgreSQL schema and migrations
- RSpec or Minitest suite in CI
- Brakeman and gem vulnerability checks
- Kamal or container deploy pipeline and staging
- Background jobs with retries and monitoring
- Upgrade calendar for Rails, Ruby and key gems
- Runbooks and hand-over notes
- IP assignment: code and data are yours
FIG 13 · Tech & tools
The tools behind the work
Proven, well-supported tools, chosen for your project and set up in accounts your business owns.
- Ruby on Rails 8.1
- Ruby 3.4
- Ruby 4.0
- Hotwire
- Turbo
- Stimulus
- Active Record
- PostgreSQL
- Solid Queue
- Solid Cache
- Solid Cable
- Sidekiq
- Action Cable
- Kamal 2
- Thruster
- Propshaft
- RSpec
- Minitest
- Brakeman
- Bundler
FIG 14 · Who it’s for
Rails work for teams that need it built, upgraded or rescued.
New builds, upgrades and dedicated developers, with the same rules: your repository, your IP, supported versions.
3 audiences
SaaS teams
New Rails 8 products.
SaaS products, marketplaces and MVPs on Rails 8.1 and PostgreSQL, with Hotwire or a React front end and a deploy you control.
- Rails 8.1 and Ruby 3.4+
- Hotwire or React
- Tests and Brakeman in CI
- Kamal or container deploys
Older Rails apps
Rails 6 and 7 apps, back in support.
Apps on Rails 7.2 or older, or Rails 8.0 after 7 Nov 2026, upgraded one minor version at a time with Ruby aligned, so you stop running a framework without security fixes.
- Gem and test-coverage audit
- One minor version at a time
- Ruby 3.2 → 3.4 or 4.0
- Upgrade calendar after
UK teams
Ruby on Rails developers for UK teams.
UK projects run through our London client-partnership centre, with engineering at our New Delhi HQ. We write in UK English, design data handling around UK GDPR and agree working hours in your written scope.
- London client partner
- UK English throughout
- Fixed written quote in GBP
- UK GDPR-aware data handling
FIG 15 · Working with us from the USA and UK
Built in New Delhi. Run on your hours.
Every project gets a point of contact in New York or London and an engineering team in New Delhi. Here is how today’s working days line up, live.
New York
North America
--:--ET
New Delhi team Your working day- Shared working time
- ≈ 3 hours today
- New Delhi is
- 10.5 h ahead
- Live calls, your time
- 9 a.m. to 12 p.m. ET
London
UK & Europe
--:--UK
New Delhi team Your working day- Shared working time
- ≈ 4.5 hours today
- New Delhi is
- 5.5 h ahead
- Live calls, your time
- 9 a.m. to 1:30 p.m. UK
Three ways to work together
- 01
Fixed-scope project
A written scope, one fixed price and a dated plan. Suits websites, apps and MVPs.
- 02
Dedicated team
Designers and engineers on your roadmap every month, billed monthly.
- 03
White label
For US and UK agencies: our work, your brand, unbranded deliverables.
Every engagement
- Fixed quote in USD, GBP or INR after a free 30-minute call
- NDA before discovery. You own all code, designs and content
- A working demo every sprint, not status slides
- Reply within one business day, calls inside your hours
Book a call
Calls on ET or UK hours
FIG 16 · Hire
Dedicated Rails developers vs team extension vs fixed-scope project
We don’t publish rates. This is how the three ways to work with Rails developers compare.
| Dedicated developer | Team extension | Fixed-scope project | |
|---|---|---|---|
| Best for | A steady backlog on one product | A release or a backlog spike | A defined app, feature or upgrade |
| Who manages the work | You, in your sprint | You, with our lead | Us, against a written scope |
| How it is priced | Monthly, per developer | Monthly, per team | One fixed quote |
| Code and IP | Yours | Yours | Yours |
FIG 17 · Compare
Rails vs Django vs Node.js: which back end?
| Ruby on Rails | Django | Node.js | |
|---|---|---|---|
| Language | Ruby | Python | JavaScript or TypeScript |
| Style | Convention over configuration, batteries included | Batteries included, explicit settings | Minimal core; you pick the framework (Express, NestJS, Fastify) |
| Built in | ORM, jobs, caching, WebSockets, auth generator, deploy (Kamal) | ORM, admin site, auth, forms | Very little; libraries for each layer |
| Best for | SaaS, marketplaces, MVPs and admin-heavy apps | Data- and AI-heavy products | Real-time apps and JavaScript-only teams |
| Weaker for | CPU-heavy or very high-concurrency services | Real-time features without extra tooling | Large apps without strong conventions |
| Our page | You are here | Python development | Node.js development |
FAQ
Frequently asked questions
Straight answers about Ruby on Rails Development with Elgrith.
Yes. Rails is actively maintained: Rails 8.1 shipped on 22 October 2025, with 8.1.4 released on 24 September 2026, and Rails 8.1 gets security fixes until 10 October 2027. Rails 8 also cut the infrastructure a Rails app needs, with Solid Queue, Solid Cache and Kamal. It remains a strong choice for SaaS products, marketplaces and MVPs.
FIG 18 · Related
Keep exploring
Free 30-minute call
Build it on Rails 8.
Tell us about the app you need, or the Rails version you are stuck on. After a free call you get a written scope, an upgrade plan if you need one, and a fixed quote.
Pick a day for your call
OpenPick a day. You'll choose a time in your own time zone on the next step.