Django + Next.js SaaS boilerplate
Start with Django and Next.js already connected, including authentication, billing, background jobs, and the foundations every SaaS needs.
Next.js frontend
React, TypeScript
Django backend
Business logic, database
Celery Worker
Background execution
Celery Beat
Scheduled tasks
Product evidence
No staged dashboard shots. What you can inspect today is the delivered structure itself: how a request moves, what the two applications own, and where slow work runs.
Source-derived diagram · Reference architecture
How a signed-in request travels from the browser through the UI, the token-checked API contract, and the Django core to persistent data.
Delivered applications
One codebase, two applications
A Next.js product UI and a Django API core, already connected instead of wired together from scratch.
Source-derived diagram · Reference architecture
Requests dispatch work to workers, and recurring jobs run on a schedule, so the interface is not blocked by heavy tasks.
The starting line
Before the product itself can begin, the same cross-stack work shows up again and again. SaaS Hammer starts past it, so the first thing you build is the thing that makes your product different.
01
Decide how the React frontend and the Django API trust each other: authentication, request handling, and CORS and CSRF choices that come before the first real screen.
02
Signup, login, sessions, and user management that work across both applications instead of one at a time.
03
The decisions around plans and billing flows that wrap the product before it can charge for itself.
04
Background jobs and recurring schedules for emails, imports, and other slow tasks, so the interface stays responsive.
05
Project structure, environment configuration, and build tooling for two applications that have to move together.
What's included
SaaS Hammer brings the cross-stack starting point into one codebase. Scan it by who owns what, not by a wall of equal cards.
Product UI
What ships on the frontend side of the boundary.
App Router, React, and TypeScript, structured for a real product UI.
Tailwind CSS and a practical set of UI components for fast screens.
Business core
What runs inside Django, close to the data.
Python, the ORM, and the admin site for your domain and data.
Signup, login, and sessions shared across both applications.
Accounts and profiles, ready to extend around your product.
The commercial layer around your product, ready for your billing flow.
Async work
What keeps slow work away from your users.
Celery workers move slow work out of the request cycle.
Celery Beat runs recurring jobs without hand-rolled cron.
Developer workflow
The cross-stack foundation that holds everything together.
A clean API boundary between the React frontend and the Django backend.
Introduction
👋 Hey, I'm Michael. I'm a Django developer and SaaS builder.
Every Django SaaS I built started with the same setup work before the product itself could begin.
SaaS Hammer is the foundation I wanted: a smaller starting line, and more room for the product.
Short answers before you start. For setup and structure, the docs go deeper.
Get started
Build the part that makes your SaaS different.
