Updated

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.

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 Flask if
  • 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

DjangoFlask
Used by31 makers' products · 65 open-source projects4 makers' products · 135 open-source projects
Downloads9.6M/wk30.9M/wk
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).

LaunchedDjangoFlaskProducts
202414% 100% 069
202516% 70% 044

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 Flask

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.

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
FlaskNothing that recurs in what we collected yet.

Who uses each

What makers pair each with

With Flask
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 →vs Flask →
Ruby on RailsBatteries includedFull-stack Ruby apps where one developer builds models, views, jobs and emails with strong conventions.vs Django →
LaravelBatteries includedPHP apps with ORM, queues, auth scaffolding and an optional paid ecosystem for hosting and admin panels.vs Django →
NestJSStructured TypeScriptLarger TypeScript backends organized into modules, with dependency injection and decorators.

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.