Updated

Laravel vs Ruby on Rails

Of the 195 makers' products we know the backend framework of, 66 chose Laravel (34%) and 26 Ruby on Rails (13%). Among the 44 launched in 2025, Laravel is in 25% and Ruby on Rails in 14%. On GitHub, 0 public pull requests moved projects from Laravel to Ruby on Rails, and 3 the other way.

Two batteries included options for backend framework. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Which fits you

Choose Laravel if
  • The backend is the product — many models, an admin, jobs and emails

Use it whenYou want first-party tools for deploying and running the app, not just the framework.

Trade-offThe smoothest path runs through Laravel's paid add-ons.

Choose Ruby on Rails if
  • The backend is the product — many models, an admin, jobs and emails

Use it whenYou know Ruby and are building a CRUD-heavy web app end to end.

Trade-offA smaller hiring and library pool than JavaScript or Python.

At a glance

LaravelRuby on Rails
Used by66 makers' products26 makers' products
Moved to it on GitHubpull requests since Oct 20243 from Ruby on Railsfewer than 3
Downloads★ 35k★ 58.8k
PricingFramework is free (open source); paid add-ons exist (Forge, Vapor, Nova, Cloud). · paid from $5/mo (Laravel Cloud)Free (open source).
Free tierYesYes
Open sourceYes · self-hostableYes · self-hostable

New launches vs older products

A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the backend framework decision (by the year they launched on Product Hunt).

LaunchedLaravelRuby on RailsProducts
202430% 2113% 969
202525% 1114% 644

Who moves from one to the other

Public pull requests on GitHub since Oct 2024 whose title says "Laravel to Ruby on Rails" or the reverse — real code changes, by developers in general rather than makers only.

Fewer than 3 pull requests move from Laravel to Ruby on Rails.

What makers say

Makers on using it for backend framework, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.

On Laravel
I use Bitbucket to manage my git repository and have Laravel Homestead running locally so I can test and work on my code in an environment that matches my production servers.
ClearCheckbook Money Management, the makerSep 2021 ↗
Long-time Laravel fan, and I've never once regretted the decision to use it as the foundation for Buildstash - our software binary and release management platform. The ecosystem and community around Laravel both just keep getting stronger.
Buildstash, the makerSep 2026 ↗
There are no alternatives. It was the best tool for the job, team expertise, and business goals.
Built for Devs, the makerSep 2026 ↗
39 more on the Laravel page →
On Ruby on Rails
For development, I use my favorite web framework Ruby on Rails , with Bulma for the front-end, as it’s so beautiful and easy to use, it makes me look like I actually know front-end design.
Remote Game Jobs, the makerApr 2022 ↗
We chose Ruby on Rails for the backend because of its rapid development capabilities, strong ecosystem, and ability to handle API-driven applications, which is essential for integrating various third-party services seamlessly.
Skarbe, the makerSep 2026 ↗
Our tech stack combines React / React Native for the front, sitting on top of a Rails backend and a PostgreSQL database.
Songstats, the makerFeb 2023 ↗
15 more on the Ruby on Rails page →

Loved and watch-outs

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

Laravel
Most loved
  • First-party packages for billing, queues, WebSockets and UI let one developer build and run a large product from one codebase. PHPH 2PH 3HN
  • Eloquent ORM, authentication, rate limiting and protection against SQL injection and CSRF come built in instead of from scattered packages. PHPH 2HNHN 2
  • Its documentation and community are strong enough that makers get an MVP running in days. PHPH 2PH 3PH 4
Watch-outs
  • The framework is a huge codebase on a dynamic language, which some see as a maintenance and type-safety risk next to Go. HNHN 2
  • PHP's shared-nothing runtime makes worker concurrency, memory use and real-time workloads harder to tune. HNHN 2
On Product Hunt: 5.0★, 67 reviews · mentioned most: fast development, robust ecosystem, strong community support
Ruby on Rails
Most loved
  • Strong conventions with auth, WebSockets and background jobs built in let solo founders and small teams ship an MVP fast. PHHNHN 2HN 3
  • A mature gem ecosystem means most common features, like authentication with Devise, are an install away. PHHN
  • Its conventions constrain the choices an LLM makes, so agent-written Rails code comes out consistent. HNHN 2
Watch-outs
  • Ruby's runtime is slow, so scaling Rails often means throwing more instances at the load. HNHN 2
  • Its implicit magic is hard to understand, and customizing beyond the conventions gets difficult without knowing the internals. HNHN 2
On Product Hunt: 5.0★, 18 reviews · mentioned most: rapid development, API integration, fast prototyping

Who uses each

What makers pair each with

With Ruby on Rails
Hosting
Payments
HonoMinimal routerSmall TypeScript APIs that run on Node, Bun, Deno or edge platforms like Cloudflare Workers.
ExpressMinimal routerNode.js servers where you want a widely documented default and a huge middleware catalog.
FastifyMinimal routerNode.js APIs that want low overhead, JSON-schema request validation and a structured plugin system.
FastAPIMinimal routerPython APIs with request validation and interactive docs generated from type hints.
DjangoBatteries includedPython apps that want an ORM, migrations, auth and an admin panel on day one.vs Laravel →vs Ruby on Rails →
NestJSStructured TypeScriptLarger TypeScript backends organized into modules, with dependency injection and decorators.

Questions

Laravel or Ruby on Rails: which do makers choose?

Of the 195 makers' products we know the backend framework of, 66 chose Laravel (34%) and 26 Ruby on Rails (13%). Among the 44 launched in 2025, Laravel is in 25% and Ruby on Rails in 14%. On GitHub, 0 public pull requests moved projects from Laravel to Ruby on Rails, and 3 the other way. Choose Laravel if the backend is the product — many models, an admin, jobs and emails; choose Ruby on Rails if the backend is the product — many models, an admin, jobs and emails.

When should I pick Laravel over Ruby on Rails?

Pick Laravel if: The backend is the product — many models, an admin, jobs and emails.

When should I pick Ruby on Rails over Laravel?

Pick Ruby on Rails if: The backend is the product — many models, an admin, jobs and emails.

Are people switching from Laravel to Ruby on Rails?

Public GitHub pull requests since 2024-10-02: 3 from Ruby on Rails to Laravel.