Laravel vs Ruby on Rails
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.
Which fits you
- 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.
- 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
| Used by | 72 makers' products | 23 makers' products |
|---|---|---|
| Moved to it on GitHubpull requests since Oct 2024 | 3 from Ruby on Rails | fewer than 3 |
| Downloads | ★ 34.9k | ★ 58.8k |
| Pricing | Framework is free (open source); paid add-ons exist (Forge, Vapor, Nova, Cloud). · paid from $5/mo (Laravel Cloud) | Free (open source). |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | Yes · self-hostable |
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.
- Analysis: Chatwoot Rails to Laravel API migration verificationmd-riaz/chatwoot · 2025-12-27
- Verify Rails to Laravel API migration completeness for production readinessmd-riaz/chatwoot · 2025-12-27
- Convert Peatio cryptocurrency exchange from Rails to Laravel 10+Decipheredmedia/PeatioCryptoExchange · 2025-11-10
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.
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.
So, here’s what we use; Gmail (obvious) AWS as our cloud of choice Laravel Forge to deploy our product on servers Webflow to power our landing page Ghost to power our blog Transistor.fm to
We use Laravel as the backbone of our app. Thanks to it, we've been able to built this from the ground up in record time, and have it super easy to run and maintain.
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.
Using ROR 7.1 shipping is quite fast! With most of the boilerplate handled by the framework itself, it becomes easy to focus on features. Support for webSockets, auth and background jobs is awesome!
It's already a mature web framework so if I need to implement feature X, usually there's already a gem for it which I just need to install and configure.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- 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
- 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

