Introduction

Djass helps you generate a production-ready Django SaaS codebase from django-saas-starter, with an API-first, agent-ready project shape.

The goal of this documentation is simple: help you understand the generated repository quickly, ship features safely, and keep human + agent execution aligned.

Who this documentation is for

Use these docs if you are:

• building a product with a generated Djass project,
• joining an existing generated codebase,
• extending the starter with custom business logic,
• operating API-first workflows for internal tools or integrations,
• or using AI coding agents to accelerate implementation.

What you get from a generated project

By default, generated projects are opinionated around:

• Django + PostgreSQL + Redis for backend and data
• Django Q2 for background jobs
• Tailwind CSS via the frontend build pipeline
• App boundaries under apps/ (core, api, pages, optional blog, optional docs)
• Configuration-first setup through explicit environment variables and clear app boundaries
• Agent-ready architecture where common tasks map cleanly to stable files, routes, and services

Suggested reading path

1. Local Development — run the project end-to-end.
2. Repository Structure — understand where code should go.
3. Background Jobs with Django Q2 — learn async execution patterns.
4. Generator Options — know what each scaffold toggle changes.
5. Workflows — add features safely and use AI effectively.

Scope note

This documentation focuses on the generated project and the architecture choices Djass applies. It is intentionally practical and implementation-oriented so teams can ship reliably whether work is done by humans, agents, or both.