# Add Granian to “How to deploy” docs (ASGI & WSGI support)

**URL:** <https://forum.djangoproject.com/t/add-granian-to-how-to-deploy-docs-asgi-wsgi-support/43386>\
**Category:** Django Internals\
**Created:** [November 12, 2025, 1:30am UTC](https://forum.djangoproject.com/t/add-granian-to-how-to-deploy-docs-asgi-wsgi-support/43386 "2025-11-12T01:30:05Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![saJaeHyukc](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/sajaehyukc/32/31592_2.png) [@saJaeHyukc](https://forum.djangoproject.com/u/saJaeHyukc)\
**Post date:** [November 12, 2025, 1:30am UTC](https://forum.djangoproject.com/t/add-granian-to-how-to-deploy-docs-asgi-wsgi-support/43386/1 "2025-11-12T01:30:05Z")

</div>

Hi everyone,

Django’s deployment docs currently mention **Daphne** , **Uvicorn** , and **Hypercorn** for ASGI,  
and **Gunicorn** for WSGI.

I’d like to suggest adding **[Granian](https://github.com/emmett-framework/granian)**, a **Rust-based high-performance server** that can run Django using **both ASGI and WSGI interfaces**.

**Example:**

```auto
# ASGI
granian --interface asgi config.asgi:application

# WSGI
granian --interface wsgi config.wsgi:application

```

Granian is fast, simple, and works well for running Django applications.  
Even a short note like

> “Other servers such as Granian can also be used.”

would help keep the docs current.

Discussion: [Deploy Django with Granian · emmett-framework/granian · Discussion #187 · GitHub](https://github.com/emmett-framework/granian/discussions/187)

Thanks!

---

<div class="post-metadata">

**Author:** ![adamchainz](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/adamchainz/32/26_2.png) [@adamchainz](https://forum.djangoproject.com/u/adamchainz)\
**Post date:** [November 12, 2025, 7:17am UTC](https://forum.djangoproject.com/t/add-granian-to-how-to-deploy-docs-asgi-wsgi-support/43386/2 "2025-11-12T07:17:31Z")

</div>

It’s a +1 from me! Granian is cool.

---

<div class="post-metadata">

**Author:** ![jacobtylerwalls](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/jacobtylerwalls/32/30603_2.png) [@jacobtylerwalls](https://forum.djangoproject.com/u/jacobtylerwalls)\
**Post date:** [December 5, 2025, 10:36pm UTC](https://forum.djangoproject.com/t/add-granian-to-how-to-deploy-docs-asgi-wsgi-support/43386/3 "2025-12-05T22:36:07Z")

</div>

+1 for me also. Do you have a Trac ticket yet?

---

<div class="post-metadata">

**Author:** ![saJaeHyukc](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/sajaehyukc/32/31592_2.png) [@saJaeHyukc](https://forum.djangoproject.com/u/saJaeHyukc)\
**Post date:** [December 7, 2025, 1:11pm UTC](https://forum.djangoproject.com/t/add-granian-to-how-to-deploy-docs-asgi-wsgi-support/43386/4 "2025-12-07T13:11:43Z")

</div>

@jacobtylerwalls I’ve just created the corresponding ticket here: [#36781 (Add Granian to Django deployment documentation (ASGI & WSGI support)) – Django](https://code.djangoproject.com/ticket/36781).