#discord #discord-api #twilight


Discord Gateway implementation for the Twilight ecosystem

54 releases (12 breaking)

Uses new Rust 2021

0.12.1 Jul 26, 2022
0.11.1 Jul 7, 2022
0.10.1 Mar 20, 2022
0.8.2 Dec 27, 2021
0.2.5 Nov 29, 2020

#407 in Web programming

Download history 443/week @ 2022-04-20 823/week @ 2022-04-27 572/week @ 2022-05-04 1075/week @ 2022-05-11 667/week @ 2022-05-18 534/week @ 2022-05-25 842/week @ 2022-06-01 561/week @ 2022-06-08 521/week @ 2022-06-15 643/week @ 2022-06-22 430/week @ 2022-06-29 341/week @ 2022-07-06 609/week @ 2022-07-13 777/week @ 2022-07-20 725/week @ 2022-07-27 674/week @ 2022-08-03

2,855 downloads per month
Used in 4 crates

ISC license

52K SLoC


codecov badge discord badge github badge license badge rust badge

twilight-gateway is an implementation of Discord's sharding gateway sessions. This is responsible for receiving stateful events in real-time from Discord and sending some stateful information.

It includes two primary types: the Shard and Cluster.

The Shard handles a single websocket connection and can manage up to 2500 guilds. If you manage a small bot in under about 2000 guilds, then this is what you use. See the Discord Docs/Sharding for more information on sharding.

The Cluster is an interface which manages the health of the shards it manages and proxies all of their events under one unified stream. This is useful to use if you have a large bot in over 1000 or 2000 guilds.


There are a few usage examples located in the root of the twilight repository.



twilight-gateway supports serde_json and simd-json for deserializing and serializing events.


The simd-json feature enables simd-json support to use simd features of modern cpus to deserialize responses faster. It is not enabled by default.

To use this feature you need to also add these lines to <project root>/.cargo/config:

rustflags = ["-C", "target-cpu=native"]

you can also use this environment variable RUSTFLAGS="-C target-cpu=native".

twilight-gateway = { default-features = false, features = ["rustls-native-roots", "simd-json"], version = "0.2" }


Note: not enabling any TLS feature is support for use behind a proxy; Discord's API is HTTPS only.

twilight-gateway has features to enable tokio-tungstenite and twilight-http's TLS features. These features are mutually exclusive. rustls-native-roots is enabled by default.


The native feature enables tokio-tungstenite's native-tls feature as well as twilight-http's native feature which is mostly equivalent to using native-tls.

To enable native, do something like this in your Cargo.toml:

twilight-gateway = { default-features = false, features = ["native"], version = "0.2" }


The rustls-native-roots feature enables tokio-tungstenite's rustls-tls-native-roots feature and twilight-http's rustls-native-roots feature, which use rustls as the TLS backend and rustls-native-certs for root certificates.

This is enabled by default.


The rustls-webpki-roots feature enables tokio-tungstenite's rustls-tls-webpki-roots feature and twilight-http's rustls-webpki-roots feature, which use rustls as the TLS backend and webpki-roots for root certificates.

This should be preferred over rustls-native-roots in Docker containers based on scratch.


zlib compression is enabled with one of the two zlib features described below.

There are 2 zlib features zlib-stock and zlib-simd, if both are enabled it will use zlib-simd.

zlib-stock is enabled by default.

Enabling zlib-simd will make the library use zlib-ng which is a modern fork of zlib that is faster and more efficient, but it needs cmake to compile.


The metrics feature provides metrics information via the metrics crate. Some of the metrics logged are counters about received event counts and their types and gauges about the capacity and efficiency of the inflater of each shard.

This is disabled by default.


~395K SLoC