Skip to content

Discover what Django can do.

Real products, open-source apps, and side projects. Find your next source of inspiration.

Submit a project

Want code you can study? Start with a guided code-reading path, Browse open-source Django projects or follow a practical Django guide.

355 projects

Featured projects appear first.

Djass screenshot

Djass

Featured

Generate a production-ready Django SaaS repo.

Keep your favorites.

Sign in to like projects and show the builders your support.

Audio AI Studio screenshot

An all-in-one browser studio where an AI voice generator, music maker, vocal remover and transcriber share one credit balance.

Keep your favorites.

Sign in to like projects and show the builders your support.

Magula FlightTracker screenshot

A Django-based spatiotemporal web application that ingests, filters, and renders real-time aviation telemetry on interactive geospatial maps.

Keep your favorites.

Sign in to like projects and show the builders your support.

FetchNode screenshot

FetchNode puts your Django errors, traffic analytics and imported Search Console data in one dashboard, so you see which site needs you first.

Keep your favorites.

Sign in to like projects and show the builders your support.

TheLoops screenshot

Stream pre-recorded video 24/7 to YouTube, Twitch and Kick from the cloud.

Keep your favorites.

Sign in to like projects and show the builders your support.

QR TIGER QR Code Generator screenshot

QR TIGER is widely recognized as one of the most reliable QR code generators worldwide, well-loved by more than 850,000 brands in 147 countries.

Keep your favorites.

Sign in to like projects and show the builders your support.

Blik360 screenshot

Open-source 360-degree Performance Reviews

Keep your favorites.

Sign in to like projects and show the builders your support.

DALOPI screenshot

a complete restaurant management system

Keep your favorites.

Sign in to like projects and show the builders your support.

Radyo Mabyal FM screenshot

Plateforme web complète pour station de radio avec streaming en direct, podcasts/replays, gestion d'émissions et programmation horaire.

Keep your favorites.

Sign in to like projects and show the builders your support.

Learn from a real Django project

Use this directory to explore what people build with Django, then pick one small feature to understand. A live product shows the result; an open-source repository lets you study the implementation.

  1. Choose a familiar problem. Search for a product you understand, such as a blog, shop, or monitoring tool. You do not need to understand the entire codebase.
  2. Check the repository before running it. Where a listing has a GitHub link, read its README, license, supported versions, and setup instructions. Check recent activity; being listed here is not a maintenance or security guarantee.
  3. Trace one feature. Follow a request through its URL, view, model, and template or API response. Read the related tests, then try a small change locally using test data, not production credentials.

Four Django source-code reading paths

Start with one feature, not the repository root. Trace API permissions in Pinry, class-based views in Baby Buddy, a monitoring state change in Healthchecks, or configuration-dependent document ingestion in Paperless-ngx.

Pinry: who can see a board?

Explore Pinry's project listing, then trace how its image-board API selects boards for the current user.

  1. Open core/views.py. Find the boards router registration and BoardViewSet.get_queryset().
  2. Follow filter_private_board() into core/serializers.py. Compare the authenticated and anonymous branches. Which boards does each exclude?
  3. Read the private-board cases in core/tests/api.py. Check the signed-in user and assertions, not just each test's name.

Baby Buddy: follow a note request

Explore Baby Buddy's project listing, then follow its note list and add pages through familiar Django building blocks.

  1. Find notes/ and notes/add/ in core/urls.py.
  2. Open core/views.py at NoteList and NoteAdd. Follow their base classes; compare the model, form, permission, and success URL settings.
  3. Read test_note_views() in core/tests/tests_views.py. Which requests and responses does it check?

Healthchecks: can HTTP 200 mean a failed job?

In Healthchecks' explicit failure-ping test, HTTP 200 acknowledges the request while the check becomes down. Explore Healthchecks' project listing, then trace that distinction in the code. No live monitoring endpoint is needed.

  1. Find uuid_urls in hc/api/urls.py. The empty path and fail both call views.ping; what extra argument does the failure route supply?
  2. Read ping() in hc/api/views.py, then Check.ping() in hc/api/models.py. Follow action to the model's status change, then return to the view's HTTP response.
  3. Compare the response-code and check-status assertions in test_fail_endpoint_works() in hc/api/tests/test_ping.py: the response is 200, but the check is down. Why would checking only the response code miss the behavior?

Reading challenge: identify the recorded ping kind and status-flip reason in that same test. These assertions cover the explicit failure request; they do not prove an alert was delivered or cover every check configuration.

Paperless-ngx: must a duplicate import fail?

In this source snapshot, matching file content triggers a warning; the duplicate-deletion setting decides whether ingestion stops. Explore Paperless-ngx's project listing, then follow the branch without uploading a document.

  1. Open src/documents/consumer.py at ConsumerPreflightPlugin.run() and pre_check_duplicate(). Follow the checksum query's two Q conditions: does it check only the original file, or the archive too?
  2. Stay in that method and find CONSUMER_DELETE_DUPLICATES. Identify which operations are inside the conditional. Does detecting a match always raise an error? Use the snapshot's duplicate-document documentation to check your interpretation.
  3. Compare test_no_delete_duplicate() with test_delete_duplicate() in src/documents/tests/test_consumer.py. Read each settings override, then the document-count and failure assertions. The same input does not imply the same configured behavior.

Reading challenge: why does the query use Document.global_objects? Follow test_delete_duplicate_in_trash() to see how a trashed document still participates. This is a code-reading exercise, not a cleanup recipe: do not change deletion settings or use personal documents to try it.

Source links use snapshots checked on October 21, 2026 (Pinry and Baby Buddy), October 30, 2026 (Healthchecks), and November 4, 2026 (Paperless-ngx), so the reading paths stay reproducible as the projects change. These are source-reading exercises, not setup tests or security audits. Check each project's current README and license before running or reusing code; use fictional data in a local environment.