Django SaaS Boilerplate Documentation

The one idea behind the boilerplate, what each of its 13 apps does, and what you can build on it.

Accept the GitHub invite, start your own repository from the template, and set up updates so new releases reach you.

One setup script, then one command. Sign up, confirm your email from the terminal, and open the admin panel.

Trust the folder, ask one orientation question, and check that the answer proves Claude read the project's rules.

One prompt builds an invoices app that charges a credit, shows up in the panel, and runs a weekly job. Then four things to check.

A Pro plan and a credit pack in Stripe test mode: keys, one prompt, the local webhook listener, a purchase with card 4242, cancelling and refunds.

An AI payment reminder that costs 1 credit, runs in a background task and refunds on failure. Plus the one thing the tests could not catch.

Your name, colors, landing page words and help page. And the one setting that does not work from .env after day one.

A fresh server, Coolify, four required settings and one deploy. Every step was followed on a new server with the times measured.

A map of the reference docs and skills in the repo, how updates reach you, and when this boilerplate is the wrong choice.