One Django Backend, Twenty-Plus Frontends: The Hub-and-Spoke Bet

Sat, 21 Feb 2026 10:00:00 +0530

With python-pay-ccavenue extracted and payments finally living in a package I trusted (chapter 5), the Django platform had stopped being a rescue operation and started being a foundation. Which was exactly when the shape of the real problem came into focus — and it wasn’t a backend problem at all.

Happy Thoughts was never going to be one app. The foundation wanted a public site to browse courses, a separate learner app to actually watch them, a Hindi-first experience distinct from the English one, a landing site per major course launch, a donations site, a react-admin panel for the content team, an events microsite, and — because most of India consumes video on a phone — a native Android app. Off to the side, the same organisation ran Ambarsthan (a bookable facility) and an internal ERP for departments and staff. By the time I counted honestly, we were looking at roughly twenty Next.js web apps plus an admin panel plus Android, all of which needed the same three things: the same content, the same user identity, and the same payments.

Keycloak on Kuldeep Pisda

One Django Backend, Twenty-Plus Frontends: The Hub-and-Spoke Bet