Django vs Flask
Of the 195 makers' products we know the backend framework of, 31 chose Django (16%) and 4 Flask (2%). Among the 44 launched in 2025, Django is in 16% and Flask in 0%. They're different kinds of tool, batteries included and minimal router, so the counts don't measure the same choice.
Two sides of the backend framework decision: batteries included and minimal router. 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 need an internal admin to manage data without building one.
Trade-offConventions to learn, and a modern interactive frontend is a separate piece.
- Small Python web apps and APIs where you add only the extensions you need.
Use it whenYou want the simplest Python server for a few endpoints or server-rendered pages.
Trade-offNo built-in async-first design, validation or ORM; larger apps end up assembling many extensions.
At a glance
| Used by | 31 makers' products · 65 open-source projects | 4 makers' products · 135 open-source projects |
|---|---|---|
| Downloads | 9.6M/wk | 30.9M/wk |
| Pricing | Free (open source). | Free (open source). |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | Yes · 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).
| Launched | Products | ||
|---|---|---|---|
| 2024 | 14% 10 | 0% 0 | 69 |
| 2025 | 16% 7 | 0% 0 | 44 |
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.
We chose Django for its robust framework and built-in tools, allowing us to build and maintain the backend efficiently with secure, scalable architecture.
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
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.
No maker quote about Flask for backend framework yet.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- 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
Who uses each
What makers pair each with
Neither quite right?
See the whole backend framework decision →Questions
Django or Flask: which do makers choose?
Of the 195 makers' products we know the backend framework of, 31 chose Django (16%) and 4 Flask (2%). Among the 44 launched in 2025, Django is in 16% and Flask in 0%. They're different kinds of tool, batteries included and minimal router, so the counts don't measure the same choice. Choose Django if the backend is the product — many models, an admin, jobs and emails; choose Flask if small Python web apps and APIs where you add only the extensions you need.
When should I pick Django over Flask?
Pick Django if: The backend is the product — many models, an admin, jobs and emails.

