Updated

Django vs Ruby on Rails

Of the 195 makers' products we know the backend framework of, 31 chose Django (16%) and 26 Ruby on Rails (13%). Among the 44 launched in 2025, Django is in 16% and Ruby on Rails in 14%.

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 Django if
  • 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.

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

DjangoRuby on Rails
Used by31 makers' products · 65 open-source projects26 makers' products
Downloads9.6M/wk★ 58.8k
PricingFree (open source).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).

LaunchedDjangoRuby on RailsProducts
202414% 1013% 969
202516% 714% 644

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 Django
We chose Django for its robust framework and built-in tools, allowing us to build and maintain the backend efficiently with secure, scalable architecture.
Layer, the makerSep 2026 ↗
Karabo would not be possible if not for the awesome Python Django Framework. The ability to go from zero to hero in two seconds and still produce a world class application with API ... only in Django
KaraboAI, the makerSep 2026 ↗
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.
CamelAI, the makerSep 2026 ↗
9 more on the Django 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.

Django
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
  • It trades runtime performance for development speed, and template-level database access makes pages slower still. HNHN 2
  • Dynamic Python offers weaker runtime guarantees, pushing some teams toward statically typed stacks, especially for agent-written code. HNHN 2
On Product Hunt: 5.0★, 25 reviews · mentioned most: batteries included, built-in tools, rapid development
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.vs Django →
LaravelBatteries includedPHP apps with ORM, queues, auth scaffolding and an optional paid ecosystem for hosting and admin panels.vs Django →vs Ruby on Rails →
NestJSStructured TypeScriptLarger TypeScript backends organized into modules, with dependency injection and decorators.

Questions

Django or Ruby on Rails: which do makers choose?

Of the 195 makers' products we know the backend framework of, 31 chose Django (16%) and 26 Ruby on Rails (13%). Among the 44 launched in 2025, Django is in 16% and Ruby on Rails in 14%. Choose Django 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 Django over Ruby on Rails?

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

When should I pick Ruby on Rails over Django?

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