Django 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.
Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗
Which fits you
- The backend is the product — many models, an admin, jobs and emails
Use it whenYou need an internal admin to manage data without building one.
Trade-offConventions to learn, and a modern interactive frontend is a separate piece.
- 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 | 37 makers' products · 58 open-source projects | 24 makers' products |
|---|---|---|
| Downloads | 11.7M/wk | ★ 58.8k |
| Pricing | Free (open source). | Free (open source). |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | Yes · self-hostable |
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.
Django makes my life easy. I've used it at least 4 projects. It's been around for a while so it's stable and LLMs have a ton of knowledge about it. It's a great project that I will continue to use for life.
We chose Django for its robust framework and built-in tools, allowing us to build and maintain the backend efficiently with secure, scalable architecture.
I don't think there is a better framework for creating web apps with Python, simply amazing!
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.
Most loved
- Admin panel, ORM, migrations, password resets and security features come built in and work together, so makers skip rebuilding them. PHPH 2PH 3HN
- It is mature and stable with thorough documentation, and LLMs write it consistently because they know it well. PHHNHN 2
- When something is missing, a third-party package usually already covers it. PHPH 2
Watch-outs
On Product Hunt: 5.0★, 25 reviews · mentioned most: batteries included, built-in tools, rapid developmentMost 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
On Product Hunt: 5.0★, 18 reviews · mentioned most: rapid development, API integration, fast prototypingWho uses each
What makers pair each with
Frontend Framework
Payments
Transactional Email
Ruby on Rails + Resend:Billingrails Sandboxhuman.softwareJetSnaps
Payments
Ruby on Rails + Stripe:
3D Bust Maker
AI Form FillMissiveOneSEO
SkarbeSongstatsOyenCov
Ruby on Rails + Lemon Squeezy:Worthless
Hosting
Ruby on Rails + Heroku:OneSEORemote Game JobsCloseby
Ruby on Rails + Netlify:
3D Bust Maker
MyCRMBackup
Ruby on Rails + DigitalOcean:
Calm Jobs
Frontend Framework
Ruby on Rails + Next.js:Billingrails Sandbox
Skarbe
Ruby on Rails + React:human.softwareSongstats

