Skip to content
STACK IT FIRST
Install the skills
03 · Backend · Growth · Internal

Django + Postgres + Redis

Batteries included: the admin, the ORM, auth and background tasks are one framework the agent has read more of than any other.
Agent fit5/5 Growth · Charge for it Reviewed

The stack

Framework
Django with the built-in admin
Runtime
Python 3.14 with uv
Data
Postgres, Redis for cache and Celery
Auth
django-allauth with SSO
Hosting
Fly, Railway, or a container platform
Also
  • Celery beat for schedules
  • HTMX for the few interactive screens
  • pytest-django
AGENTS.md + real projects on STACK IT FAST (opens in a new tab)

Why agents do well here

5/5
  • Django's conventions are two decades old and everywhere in training data; agent-written models, views and admin classes look like the docs.
  • The admin gives a screen per model for free, so most internal tool requests become a model change the agent makes in one file.
  • Celery beat keeps the automation next to the models it acts on, in the same tests.

Avoid at this tier

  • A React admin panel; Django's admin covers the first two years.
  • Raw SQL in views; the ORM is the contract the agent can reason about.
  • Multiple Django projects; use apps inside one project.

How it fits together

Internal tools at growth need permissions, audit trails, schedules and a lot of screens quickly. Django’s admin, ORM and Celery cover all of it in one process with one set of conventions.

Folder layout

project/
  settings/       base.py, prod.py
  apps/<domain>/  models.py, admin.py, views.py, tasks.py, tests/
  templates/      server-rendered, HTMX where needed

First five decisions

Lock these in before the agent writes the second feature. Each one removes a choice it would otherwise make differently every time.

  1. 01 Django admin as the UI
  2. 02 Apps per domain
  3. 03 Celery beat for schedules
  4. 04 SSO through allauth
  5. 05 Pytest-django with a real database

When to move on

Stay here until the product forces the next tier. You are ready for Scale when:

  • More than one team deploys backend code independently
  • Data lives in more than one region or under residency rules
  • An auditor will ask who changed what
  • Latency and throughput are contractual, not aspirational
Scale · Internal Rails + Postgres + Redis The most convention-heavy full-stack framework there is, which at scale is exactly what keeps many teams' internal tools consistent. Next tier

Same tier, other profiles