A list of projects and apps built with Django.
This site is meant to showcase the awesome work the Django community is doing. I wanted to create a place for people to have their work recognized, especially if it is open source (proprietary projects definitely welcome though!), and stand as examples for those who are new to the language.
You can submit your project here -> https://builtwithdjango.com/projects/new/
If you have any ideas, please open up an issue, and I'll try to implement it when I can.
Run the default test suite with Docker:
make testPass pytest arguments with ARGS:
make test ARGS="api/tests.py -v"To run against an isolated Postgres database from pgsandbox-mcp, create a sandbox database, then pass its connection string as DATABASE_URL:
DATABASE_URL="postgresql://..." make test-pgsandboxThe test-pgsandbox target rewrites localhost and 127.0.0.1 database hosts to host.docker.internal for the backend container, uses builtwithdjango.test_settings, and runs pytest with --reuse-db because sandbox roles do not create separate Django test databases.
Production Sentry is enabled when SENTRY_DSN is set and SENTRY_ENABLED is true. SENTRY_ENABLED defaults to true only when ENV=prod. The default backend config captures all errors, warning-and-above logs, sampled traces, trace-lifecycle profiles, application metrics, and AI spans for Pydantic AI.
Browser Sentry defaults to the same DSN through SENTRY_BROWSER_DSN and adds JavaScript error monitoring, browser tracing, structured browser logs, and Session Replay. Replay masks text, inputs, and media by default. The most useful frontend knobs are SENTRY_BROWSER_TRACES_SAMPLE_RATE, SENTRY_BROWSER_REPLAY_SESSION_SAMPLE_RATE, and SENTRY_BROWSER_REPLAY_ERROR_SAMPLE_RATE.
For a free-plan project, keep the defaults in .env.example unless volume requires tuning. The most useful backend knobs are SENTRY_TRACES_SAMPLE_RATE, SENTRY_PROFILE_SESSION_SAMPLE_RATE, SENTRY_LOG_LEVEL, and SENTRY_INCLUDE_AI_PROMPTS. Prompts, browser user PII, and local variables are disabled by default to avoid accidentally sending submitted project content or secrets to Sentry.
Production webpack builds emit hidden source maps. If SENTRY_AUTH_TOKEN, SENTRY_ORG, and SENTRY_PROJECT are present during the build, the Sentry webpack plugin uploads them and deletes local .map files after upload. Sentry Size Analysis is for mobile builds, so source-map upload is the relevant web equivalent for this Django site.