Generator Options
Choose generator options around the first workflow you need to deliver, not the longest feature list. Enable an integration when you know what it will do and who will configure it. Djass generates the selected code and configuration; you still supply service credentials, implement product rules, and verify the result before launch.
Still choosing a starter? Compare Djass with SaaS Pegasus by hosted generation, team membership and the next upstream update before selecting integrations.
These are build-time generator choices, not runtime release controls. The Django feature-flags production guide explains when a generated application needs a separate flag system for rollout and rollback.
Choose your first build
The table describes decisions to make, not additional presets in the generator.
Check the current form or call get_generator_options before submitting an
agent-generated configuration. Several integrations default to enabled; leaving
an option unspecified is not the same as turning it off.
| Your first workflow needs… | Option to review | What you still need to do |
|---|---|---|
| Payments inside your own app | use_stripe |
Configure Stripe, then verify the first sandbox subscription and decide which states grant access. This does not change your Djass account's generation entitlement. |
| Media in object storage | use_s3 |
Configure storage credentials and access policy. Add upload validation and authorization; the toggle does not build a private-file workflow. |
| Usage and conversion measurement | use_posthog |
Configure your own project and verify the generated app's first event, including identity and privacy settings. |
| Production error reporting | use_sentry |
Configure the DSN, sensitive-data filters, and who responds to errors. |
| Scheduled-job heartbeat monitoring | use_healthchecks |
Configure the check and connect job completion to the expected schedule. This is separate from the app's readiness route. |
| AI calls in the application | use_ai |
Configure the provider and implement the task, error handling, and spending limits. Using a coding agent alone does not require this option. |
| An MCP interface in the application you generate | use_mcp |
Define the tools and their authorization. Leave this off if you only want to use Djass's hosted MCP server to generate the repository. |
| Public articles or product documentation | generate_blog, generate_docs |
Write the content you intend to publish; these options do not create a content strategy. |
| Automated repository checks | use_ci |
Connect the repository and verify its CI configuration and required environment. |
For example, an internal tracker with no payments, uploaded files, AI features,
or public content can explicitly turn off use_stripe, use_s3, use_ai,
use_mcp, generate_blog, and generate_docs. Review the remaining options
individually, including monitoring, email rendering, and CI. This is a starting
decision, not a complete payload or a promise of zero configuration.
Before generating, write down:
- The first useful action: what a signed-in user should accomplish.
- An explicit choice for each toggle: use
"y"or"n"when preparing an API or agent payload, rather than relying on remembered defaults. - The setup still required: credentials, provider accounts, permissions, and application rules. Keep secrets out of the project description and Git.
- The acceptance check: an observable result for each enabled service, such as a test payment producing the intended access state.
Then generate with an AI agent or use the Djass dashboard. After downloading, follow the generated repository's setup instructions and the local-development guide before adding your first feature. Generation creates a repository; it does not deploy or validate your finished product.
Plan customer accounts and shared workspaces
Authentication is part of the generated baseline, not another integration
toggle. The bundled starter checked on November 3, 2026 uses Django's built-in
User, a related Profile, and django-allauth configured for email-only
login. A profile is not a workspace or a membership rule.
Choose the next step from the customer action you need:
- Sign up and sign in: start with the generated-app allauth contract, then verify your local email flow.
- Add account fields: inspect the current user model and migration history before replacing identity storage. A newly downloaded starter already has migration files.
- Share records with teammates: there is no teams generator option. You implement workspaces, membership, roles, and resource access. The invitation acceptance guide covers the recipient's verified-account-to-membership handoff, not invitation issuance or a complete teams package.
Before release, use the two-account authorization checklist to check who can act on each record. Neither signing in nor enabling payments grants access to another customer's data.
Core fields
- Project Name / Slug: naming used in generated files and package metadata.
- Repo URL / Description / Author fields: metadata used in templates and defaults.
- CapRover App Name: deployment app name derived from the project slug.
- Project Main Color: controls primary Tailwind color references used in templates.
Integration toggles
Monitoring
- Use the production Django logging guide to define stable event fields, carry correlation into workers, protect sensitive data, and test the records that monitoring integrations consume.
- Use PostHog: product analytics. Backend logs use standard Python logging, so PostHog Logs can read the same structured fields when its handler is attached. Use the Django analytics with PostHog guide to define stable identity, event ownership, verified conversion events, and tests.
- Use Sentry: error monitoring plus breadcrumbs, events, and optional logs from standard Python logging records. Use the Django Sentry production guide to set release identity, privacy filters, web/worker sampling, ownership, canaries, and incident closure.
- Use Healthchecks: outbound scheduled-job heartbeat setup when enabled. The generated project always includes its database-and-Redis readiness route; use the Django health check design guide to wire readiness, liveness, and worker freshness to the right consumers.
- Use Apprise: Apprise-backed admin notification helper, config, deployment docs, and tests.
CX
- Use Chatwoot: customer support/chat integration scaffolding.
- Use MJML: email templating/rendering support. The production Django email guide covers the delivery contract around those templates: durable intent, workers, retries, provider outcomes, suppressions, and tests.
UX
- Use Keyboard Shortcuts: keyboard shortcut helpers, data attributes, and visible shortcut hints for command-oriented UI controls.
Commerce
- Use Stripe: Stripe integration scaffold pieces. Before taking recurring billing live, use the Django Stripe subscriptions production guide to define entitlement policy, webhook idempotency, invoice events, and lifecycle tests.
Storage
- Use S3: storage configuration paths for media assets. Before production, use the Django S3 storage guide to choose public or private access, verify provider settings, and migrate existing media safely. This option does not generate upload forms, validation, malware scanning, or direct-upload endpoints; add those with the Django file upload production pipeline.
- Use Qdrant: authenticated Qdrant client configuration with lazy connection setup. This option does not provision a Qdrant service, create collections, or define vector indexing and query workflows. It is off by default.
AI
- Use AI: AI-related service/config scaffolding.
- Use MCP: includes your generated app's MCP connection and initial
get_user_infotool, not the hosted Djass project-generation tools. Follow the MCP access handoff before adding customer-facing actions; credentials and ownership rules belong to your app. This option is not required to generate a project through hosted Djass MCP.
Content toggles
- Generate Blog: includes the blog content and supporting code under
apps/pages, with templates underfrontend/templates/pages/blog. - Generate Docs: includes Markdown pages under
apps/pages/content/docs, with templates underfrontend/templates/pages/docs.
Delivery toggles
- Use CI: includes GitHub Actions CI workflow.
Recommendation
Keep your first generation conservative. Enable only what you plan to use in the next 2–4 weeks.
It is usually easier to add one integration intentionally later than to maintain several unused integrations from day one.
Changing a generation choice is not an in-place upgrade of an existing app. Treat any newly generated ZIP as a separate repository to inspect and compare; do not overwrite a working project to add one integration.
For contributors: verify the option catalog
Djass keeps the supported starter fields in apps/core/generator_options.py.
The bundled template lives under starter/; starter/cookiecutter.json and the
catalog should change together. In a checkout of the Djass generator itself, run:
python manage.py sync_cookiecutter_options --check
CI runs this check on pull requests. This is a generator-maintenance command, not a setup step for someone who downloaded a generated project.