Ruby 4.0 · Rails 8.1 · 2026

Optimized for human happiness.

Ruby is a programmer's best friend. Rails is the definitive full-stack framework built on it. Together, they scale from a weekend prototype to Shopify — without ever getting in your way.

1995
Ruby released
2004
Rails released
Today
Powering the web
A faceted ruby gemstone catching light — the visual metaphor for Ruby the language
Ruby (n.)
"A precious stone. A precious language."
Where Rails runs

From garage to global scale.

Rails doesn't just fit small teams. It powers entire industries — quietly, reliably, at absurd scale.

I · The Language

Ruby is a programmer's best friend.

Since 1995, Yukihiro "Matz" Matsumoto has shaped Ruby around a single principle: the tool should serve the person, not the other way around. The result is a language that reads like English, punishes you for nothing, and rewards elegance.

Visit ruby-lang.org →
01

Optimized for happiness

Ruby was designed with one goal: make programming a joy. Every syntax choice bends toward the human, not the machine. It reads like a well-written sentence — even to newcomers.

02

Expressive and concise

Where other languages need a paragraph, Ruby needs a line. Blocks, symbols, and open classes let intent lead the code. Less scaffolding, more meaning.

03

200,000+ gems, 30 years strong

A mature ecosystem battle-tested since 1995. Every problem you're about to hit — someone in the Ruby community has already solved it, documented it, and given it away.

The Ruby Way

Say more with less.

The same idea, in two languages. Ruby's expressiveness isn't a nice-to-have — it compounds every day for the life of your product.

Verbose enterpriseJava
public class ProductsController {
  @Autowired
  private ProductRepository repo;

  @GetMapping("/products")
  public ResponseEntity<List<Product>>
  index() {
    List<Product> products =
      repo.findAllByPublishedTrue();
    return ResponseEntity.ok(products);
  }
}
The Rails WayRuby
# app/controllers/products_controller.rb
class ProductsController < ApplicationController
  def index
    @products = Product.published
  end
end
$ bin/rails server => Booting Puma => Rails 8.1.3 application starting => Listening on http://0.0.0.0:3000

"Ruby is simple in appearance, but is very complex inside — just like our human body."

— Yukihiro Matsumoto, creator of Ruby
II · The Framework

Rails scales from PROMPT to IPO.

The world's most opinionated full-stack framework. Everything you need, nothing you don't. Built by 37signals, stewarded by a foundation, sharpened by two decades of production truth.

01

Convention over Configuration

Skip the boilerplate parliament. Rails gives you sensible defaults so you spend your energy on what actually makes your product unique.

02

The One-Person Framework

One developer. Full stack. Real product. Rails ships with everything — ORM, routing, jobs, mailers, storage, credentials — so you never wire the plumbing yourself.

03

Hotwire & Turbo

Reactive UIs without the SPA tax. Ship modern interactions with server-rendered HTML and a fraction of the JavaScript.

04

Scales from PROMPT to IPO

The same framework that fits in one file also runs Shopify. Rails 8 ships with Solid Queue, Solid Cache, and Kamal — production-ready, monolith-first, no vendor lock-in.

Backend · Rails API

The best backend you can ship this week.

Rails isn't just for full-stack monoliths. As a pure JSON API behind a React, iOS, or Flutter frontend, it's the fastest productive backend on the planet — with the most mature ecosystem for the boring problems (auth, jobs, migrations, caching, mail) that eat every other stack alive.

$ rails new my_api --api
$ cd my_api && bin/rails g scaffold Post title:string body:text
$ bin/rails db:migrate server
API-first

rails new --api

One flag scaffolds a lean JSON API — no views, no asset pipeline. Just controllers, serializers, and the fastest path from database to endpoint you'll ever ship.

Batteries included

Everything a backend needs

Active Record, migrations, background jobs (Solid Queue), caching (Solid Cache), WebSockets (Action Cable), mail, storage. No stitching six microservices together to send a signup email.

Conventions

Boring, on purpose

RESTful routes, predictable file layout, one obvious way to do things. New engineers ship a feature on day one instead of decoding your bespoke architecture.

Deploy

Kamal to any server

Push a Rails API to a $6 VPS with a single command. No Kubernetes, no serverless cold starts, no lock-in — just Docker and a health check.

AI · Generative Ruby

Ship AI features without switching stacks.

Ruby is having an AI moment. A new wave of gems makes LLMs, embeddings, agents, and RAG feel native — no Python sidecar, no Node microservice. Just Active Record, a background job, and an elegant call to your model of choice.

Multi-provider LLM client

RubyLLM

One elegant API for OpenAI, Anthropic, Gemini, Bedrock, Ollama and more. Streaming, tools, structured output, embeddings — the Ruby way.

Agents & chains

langchainrb

The LangChain equivalent for Ruby. Build agents, retrieval pipelines, vector search, and tool-using assistants without leaving the stack.

Official-style OpenAI SDK

ruby-openai

Battle-tested community gem. Chat, images, audio, assistants, and the Responses API — with first-class streaming in a few lines.

Vector search in Postgres

Neighbor / pgvector

Store embeddings in the same database that already runs your app. No new service, no sync jobs — just Active Record with cosine similarity.

# Chat with any model, one API
chat = RubyLLM.chat(model: "claude-sonnet-4")
chat.ask "Summarize this PR", with: pr.diff

# Stream tokens straight to the client
chat.ask(prompt) do |chunk|
  Turbo::StreamsChannel.broadcast_append_to :thread, target: "reply", html: chunk.content
end
Why Rails for AI apps

The glue is already written.

  • Solid Queue for long-running generations and retries.
  • Action Cable + Turbo Streams for real-time token streaming to the UI.
  • Active Storage for images, audio, and document uploads to feed your models.
  • pgvector + Neighbor for RAG in the database you already trust.
One monolith. One deploy. AI shipped.
4M+
Shopify stores on Rails
100M+
GitHub developers served
200k+
Gems in the ecosystem
30 yrs
Battle-tested since 1995
§ 08 · Compared

Ruby & Rails vs. everything else.

Every stack has trade-offs. Here's an honest look at where Ruby and Rails out-ship the alternatives — and where the alternatives earn their keep.

Written by Rubyists — biased, on purpose.

  • The default
    JavaScript / Node
    Rails wins on cohesion
    Them

    A thousand micro-decisions before you write a line of business logic. Pick a framework, an ORM, a validator, a router, a bundler, an auth lib — then glue.

    Ruby on Rails

    Rails ships one integrated answer: ActiveRecord, Action Cable, Action Mailer, Solid Queue, Turbo. One `rails new` and you're building the product on Monday.

  • Types everywhere
    TypeScript
    Ruby wins on velocity
    Them

    Types catch a class of bugs — and cost you refactoring speed, generic gymnastics, and a compile step for every change.

    Ruby on Rails

    Ruby's dynamism plus a strong test culture (RSpec, Minitest, system tests) gives you correctness without the ceremony. Sorbet and RBS are there when you want gradual typing.

  • The closest cousin
    Python / Django
    Rails wins on convention
    Them

    Django is excellent — but leans on you to pick the async story, the background jobs, the deploy story, the frontend story.

    Ruby on Rails

    Rails takes strong opinions so you don't have to. Hotwire, Kamal, Solid Queue, Active Storage — batteries and the whole factory included.

  • The enterprise stack
    Java / Spring
    Ruby wins on readability
    Them

    AbstractSingletonProxyFactoryBean. XML. Annotations. Ten files to add one endpoint. Optimized for large teams by punishing small ones.

    Ruby on Rails

    A Rails controller is a class. An action is a method. What you read is what runs. Small teams stay small; big teams stay fast.

  • Systems-flavored
    Go
    Rails wins on product speed
    Them

    Fantastic for infrastructure and CLIs. For a CRUD-heavy product with auth, billing, admin, jobs, and email — you'll rebuild half of Rails yourself.

    Ruby on Rails

    Rails is a product framework. Ship a full SaaS with auth, payments, uploads, admin, and background work in a week — not a quarter.

  • The direct heir
    PHP / Laravel
    A worthy rival — Ruby wins on language
    Them

    Laravel borrows liberally from Rails and does it well. The language underneath, though, still shows its age.

    Ruby on Rails

    Ruby was designed for humans first. Blocks, symbols, metaprogramming, and a 30-year gem ecosystem give Rails a ceiling Laravel can't quite reach.

Trade-offs are real. The best tool is the one your team ships with — for product-shaped web apps built by small teams that care about craft, that tool is Rails.

Batteries · Included

What ships in the box.

A green check means it's built in and blessed by the framework — no gem-picking, no third-party glue, no bikeshedding.

Feature (out of the box)RailsNode/ExpressTypeScriptDjangoSpringGoLaravel
ORM & migrations
Background jobs
Caching store
WebSockets / realtime
Transactional email
File uploads & storage
Encrypted credentials
Auth generator
SPA-less reactivity
One-command deploy
Testing framework
Scaffolding & generators
VI · Rails in the Fortune 500

Built for enterprise.

The same framework that lets a solo founder ship in a weekend runs regulated, audited, mission-critical systems for the largest software companies on earth. Rails isn't a stepping stone — it's the destination.

Security & Compliance

Encrypted credentials, signed cookies, CSRF/XSS/SQLi defenses on by default. Rails ships with the primitives that pass SOC 2, HIPAA, and PCI audits — used by banks, healthtech, and payroll platforms.

Long-term Support

A 20-year-old framework with an active core team, the Rails Foundation, and predictable release cadence. Backports and security patches for stable branches keep long-lived enterprise apps safe.

Proven at Massive Scale

Shopify handles millions of RPM on Black Friday. GitHub runs a 2M+ LOC Rails monolith for 100M+ developers. Rails is not a prototyping toy — it is battle-tested infrastructure.

Total Cost of Ownership

Convention over configuration means smaller teams ship more. One senior Rails engineer replaces a squad of specialists. Kamal deploys to your own hardware — no per-seat platform tax.

Interoperable by Design

JSON APIs, GraphQL, gRPC, SAML/OIDC SSO, ActiveJob adapters for every queue, first-class Postgres, Oracle, and SQL Server support. Rails plugs into the enterprise stack you already run.

Talent & Ecosystem

200,000+ gems, a hiring pool of senior craft-focused engineers, and vendors (thoughtbot, 37signals, Cookpad, Doximity) with decades of Rails production experience.

Enterprises running Rails in production
ShopifyGitHubGitLabZendeskIntercomProcore1PasswordGustoChimeClioCookpadDoximity
VII · Ship to any cloud, keep your sanity

Deploy Rails to any cloud.

Rails ships production-ready Dockerfiles, encrypted credentials, and Kamal out of the box. That means one artifact and one deploy playbook — whether you run on AWS, Azure, GCP, or a $6/mo VM.

AWS

The default enterprise pick
Core services

ECS Fargate · EKS · Elastic Beanstalk · RDS Postgres · ElastiCache · S3 · CloudFront · Secrets Manager

Recommended approach

Containerize with the Rails-generated Dockerfile. Push to ECR, run on Fargate behind an ALB, terminate TLS at CloudFront, store secrets in Secrets Manager (never in ENV files). Use RDS Postgres with Multi-AZ, ElastiCache Redis for Sidekiq/Solid Queue, and S3 + CloudFront for Active Storage. Autoscale on RPM, not CPU.

AWS Rails guide

Azure

Great for .NET-adjacent orgs
Core services

Container Apps · AKS · App Service · Azure Database for PostgreSQL · Azure Cache for Redis · Blob Storage · Key Vault

Recommended approach

Ship the Docker image to Azure Container Registry and run on Azure Container Apps with a managed ingress and KEDA autoscaling. Use Azure Database for PostgreSQL Flexible Server, Azure Cache for Redis, and Blob Storage for Active Storage. Pull secrets from Key Vault via managed identity — no keys in the image.

Azure Container Apps

GCP

Fastest cold starts
Core services

Cloud Run · GKE Autopilot · Cloud SQL Postgres · Memorystore · Cloud Storage · Secret Manager · Cloud Build

Recommended approach

Cloud Run is the sweet spot: give it a container, get autoscaling to zero and a managed HTTPS URL. Use Cloud SQL Postgres with the Auth Proxy sidecar, Memorystore Redis, and Cloud Storage for uploads. Wire Secret Manager into env vars and let Cloud Build handle CI from a push.

Cloud Run for Rails

Kamal + your own VMs

The Rails 8 default
Core services

Hetzner · DigitalOcean · Linode · Fly.io Machines · bare metal · any Docker host

Recommended approach

kamal deploy ships zero-downtime Docker rollouts to any Linux box with SSH. Rails 8 also brings Solid Queue, Solid Cache, and Solid Cable so you can drop Redis entirely on smaller apps. Put Cloudflare or a managed load balancer in front, back it with managed Postgres, and pay a fraction of the hyperscaler bill.

Kamal docs

Heroku & Render

PaaS — least ops
Core services

Heroku · Render · Railway · Fly.io · Scalingo

Recommended approach

git push and you're live. Perfect for MVPs, staging environments, and teams that would rather buy ops than run it. Use managed Postgres and Redis add-ons, background workers as separate process types, and preview environments per pull request. Migrate to Kamal or a hyperscaler when you outgrow the price/perf curve.

Deploying Rails on Render
Six practices that hold across every cloud

One image, many environments

Build the Docker image once in CI. Promote the exact same digest through staging and production. Environment differences live in secrets and env vars — never in the image.

Secrets in a vault, never in ENV files

AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, or Rails encrypted credentials. Rotate on a schedule. Never bake API keys into the image or commit .env to git.

Managed Postgres from day one

RDS, Cloud SQL, Azure Database for PostgreSQL, Neon, Supabase. Multi-AZ, automated backups, point-in-time recovery. Do not run your own database on a VM in 2026.

Background jobs as separate processes

Sidekiq or Solid Queue in their own containers/dynos. Autoscale independently from web. Health checks on both. Never run jobs in-process with the web server.

Zero-downtime deploys

Rolling deploys with health checks (Kamal, ECS, Cloud Run, Container Apps all support this out of the box). Run migrations before the new release boots, and keep them backwards-compatible.

Observability from day one

Structured logs to CloudWatch, Cloud Logging, or Datadog. APM with AppSignal, Skylight, New Relic, or Datadog. Error tracking with Sentry or Honeybadger. You cannot fix what you cannot see.

Zero-downtime deploy
$ bin/kamal setup && bin/kamal deploy
Kamal docs →
The stewards

The Rails Foundation

A non-profit dedicated to improving documentation, education, marketing, and events — ensuring a prosperous, decades-long Ruby on Rails ecosystem.

rubyonrails.org/foundation →
Core Members
37signalsShopifyProcore1Password
Contributing Members
Gusto ·Chime ·Clio ·AppSignal ·Planning Center ·Fullscript
Save the date

Rails World
2026

When
Sep 23–24, 2026
Where
Austin, Texas
Format
2 days · 2 tracks
Community
1,200+ devs
Details & tickets →
III · Your first Rails app is one weekend away

Get started with Ruby & Rails.

A curated, opinionated shortlist of the best resources on the planet — official docs, free tutorials, paid training, and the books every serious Rubyist keeps on the shelf.

Quick start
$ gem install rails && rails new my_app && cd my_app && bin/rails server
Full guide →
The objections

You've heard the myths.

Every one of these gets asked at every meetup. Every one has an answer.

Isn't Ruby too slow?
Performance is almost never a language problem — it's an architecture problem. Shopify serves millions of requests per minute on Rails. GitHub runs 100M+ developers on a single Rails monolith. Ruby 4's ZJIT closes the gap even further. Your bottleneck is not the interpreter.
Is Rails hiring hard?
Rails attracts senior engineers who care about craft, testing, and shipping. A tighter pool of high-signal talent beats a huge pool of framework tourists. The Ruby community is famously welcoming, and the learning ramp is short.
Is Rails still relevant in 2026?
Rails 8 ships in 2026 with Solid Queue, Solid Cache, Kamal deployment, and a doctrine explicitly built for AI-agent-authored code. The Rails Foundation is backed by Shopify, GitHub, 37signals, Procore, and 1Password. Rails World 2026 sold out. Rails is not slowing down — it's accelerating.
What about the JavaScript frontend?
Rails ships with Hotwire (Turbo + Stimulus): reactive UIs backed by server-rendered HTML. You can still bring React, Vue, or Svelte if you want — Rails is a beautifully minimal companion to any frontend.