django/daphne
Django Channels HTTP/WebSocket server observed · 2026-08-28
Health v2 · maintenance only
74/100
- Activity 93
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3906
- days_rel: n/a
- days_push: 43
- n_releases_24m: 0
Adoption not part of the score
2679 stars · 292 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
Daphne is an HTTP, HTTP/2, and WebSocket protocol server for ASGI applications, built to power Django Channels. It automatically negotiates protocols so WebSocket and HTTP endpoints can share the same port without URL prefixing.
Use cases
- serve an ASGI Django application in production
- run websockets alongside HTTP on a single port
- terminate HTTP/2 connections with TLS
- run an ASGI server behind a reverse proxy over unix sockets
- deploy Django Channels realtime apps
When to choose
- you need a production ASGI server for Django Channels or any ASGI app
- you need native WebSocket and HTTP protocol negotiation
- you need HTTP/2 termination with TLS
When to avoid
- you run WSGI-only Django apps without async features
- you prefer uvicorn or hypercorn for a non-Django ASGI stack
Facets
service · maturity stable
http-server websocket web-development backend python cross-platform cli asgi django-channels http2 twisted async real-time
2 sources
- readme: https://github.com/django/daphne · fetched 2026-08-28 · 2c4dd6904f7b
- registry_pypi: https://pypi.org/pypi/daphne/json · fetched 2026-08-29 · 9e3daf6a4d92
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| django/daphne | main | 74 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem