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, andpages, with optional blog and documentation content owned bypages) - 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
- Local Development — start your downloaded app, check local services, and verify your first account.
- Repository Structure — understand where code should go.
- Background Jobs with Django Q2 — learn async execution patterns.
- Generator Options — choose integrations for your first useful workflow and check what remains to configure.
- Workflows — add features safely and use AI effectively.
- Environment Variables — configure your downloaded app without mixing hosted-generator settings or connection addresses.
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.
Choosing a starting repository
Before generation, compare the hosted Djass workflow with a local Django template. Use the first-feature checklist to decide which starting point fits your stack and team.
Prepare your first production release
If generation or downloading was interrupted before local setup, use the existing-project recovery checklist. Resume the saved project ID instead of creating another job to recover a ZIP.
When the app works locally, follow the first production deployment checklist to prepare an application image, HTTPS, email delivery and durable data, then verify the web and worker release before inviting users. Local development settings are not production credentials.