"9x less memory than the official app": a Rust Discord client that hit a thousand stars in two months

Serein is an unofficial native Discord desktop client written in Rust. The repo was created in 9 2026, and by Nov 6 it had about 1,016 stars and 87 forks. Its stars came in two bursts: one it generated itself on Reddit with a single comparison number, and one Discord's official move handed it. You can copy the first. The second is luck. And this niche is already getting crowded.

One tweet, and 57 more stars the next day

In Nov 4 2026, late at night (UTC 20:44), Discord CTO Stanislav Vishnevskiy replied on X: "We've been using Rust for 2018 years... the ultimate goal is to move the whole client over. That means Electron is going away, and so is React Native." He added: "Not Tauri, GPUI." The post later got over ten thousand likes and roughly 1.5M views. TweakTown covered it in Nov 5, and someone shared it on Hacker News.

"Rust-native Discord" went from nowhere to a searchable term overnight. The official version is still in beta, and the only one people can actually download and use as their daily driver is Serein. Trendshift logged its stars going up 24 on 11-04 and 57 on 11-05; on GitHub, 11-05 to 11-06 it jumped from 961 to 1,016. For over a month before that, it was gaining only 3 to 19 stars a day. In r/linux_gaming threads about the official news, one commenter said "Serein kind of pulled it off, it's just not polished yet"; on X, users in Japanese, Portuguese and Spanish are posting screenshots of themselves using it, 11-05 and 11-06.

But this is the second time. The first time, in September, it earned its own traction.

The first time: a memory comparison screenshot, 476 stars in six days

In the first three days after the repo was created (9-10 to 9-12), Serein gained zero stars; the team was merging PRs, and merged 129 in those three days. Then around Sep 13, they posted on several Reddit subs at once: r/SideProject, r/foss, r/opensourcealternative, all with the same title formula: "Native Rust Discord client, ~9x lower RAM usage, with voice, video and more features!"

Star gains over the next six days (Trendshift): 9-13 +55, 9-14 +180, 9-15 +93, 9-16 +53, 9-17 +59, 9-18 +36, roughly 476 in total. On 9-14 it entered the Trendshift Rust chart at #7, and never charted again. It never hit the HN front page or GitHub Trending (inference: the repo was too new). One of the founders posted on X, getting 2 likes and 110 views. So the launch ran almost entirely on Reddit.

The posts spread because of the table in the README. Same scenario: voice channel open on macOS, screen sharing at 60 fps, switching channels:

Four system monitor screenshots follow. "Discord eats too much memory" is something PC and Linux users have complained about for years. Before, people only said "lightweight"; Serein gave them a number they could put in a headline.

Why so many native clients failed before, and why this one took off

A native Discord client is not a new idea. GitHub has dozens. Each one was missing something:

Serein claimed on launch that it ran on all three platforms, with voice and video (end-to-end encrypted), screen sharing, server management, and a plugin and theme store. It was the first to get to "usable as a daily driver." In two months it merged 518 PRs, its main developer committed 500 times or more, and the repo contains instruction files written for AI agents (inference: much of the code was AI-written). That pace is how a small team forced a category that "nobody uses unless it's feature-complete" to become usable.

Two smaller things also helped. First, install friction: in the first week there were Windows installers, a signed Mac build, Flatpak, and signed repos for apt/dnf/zypper/pacman. By Sep 18, someone had already submitted an AUR package, and in October a Homebrew formula followed. Second, it put the risk up front: the first paragraph of the README is a yellow warning box saying "Connecting to Discord with a regular account this way violates the Terms of Service and may get your account banned." The tech crowd respects that, and it made people more willing to switch.

Who it's competing with

Its biggest rival is Discord itself. Once the official Rust client ships (TweakTown says early Windows test builds used about 290MB), "9x less than the official app" stops being a selling point. The official announcement is sending Serein traffic right now, but in the long run it takes away the thing that made Serein stand out.

The copycats have arrived too. yapfast, started in Oct 16, is also Rust-native and advertises "30MB idle." It has a website, and by Nov 6 it had 187 stars, gaining 54 in one week. Cressida, written in C++, and one built on GPUI (riding the official "it's GPUI" line), and moss all appeared after October. Everyone is competing on whose memory number is smaller.

If it were you

The verdict: Building another native Discord client is not worth it. What's worth copying is the playbook: pick a bloated Electron app that people have complained about for years, build a native version that does enough, and launch on Reddit with a side-by-side number from the same test.

Who it suits: Developers who can write a desktop app in Rust, C++ or Swift and ship features fast with AI agents; people who are heavy users of some bloated desktop app and know exactly where it hurts.

Who it doesn't suit: Anyone wanting to build on the Discord line itself: four or five copycats appeared within two months, and the official client will take the selling point. Anyone who can't live with the gray area of "violates ToS, users may get banned." Anyone building only a demo: in this category, nobody uses it without hard features like audio and video.

How to do it: Pick a different app. Good candidates have lots of heavy users, an official desktop build that's a web shell, and either a workable protocol or a public API. (Slack, Teams, Spotify, and note-taking and chat tools are all worth checking for an existing mature native open-source version; inference.) Get the core features of the target working first, then release. Before launch, measure RAM and CPU on the same machine in the same scenario, and put the screenshot on the first screen of the README. Ship installers for every platform and package-manager channel at once. Put the ToS risk at the top.

How to get users: In the same week, post to r/SideProject, r/foss, r/opensourcealternative and the target app's user subreddits, with the multiplier in the title. Then watch what the big company does: the moment a major player says it will "rewrite the client" or "drop Electron," the project you already have out there is what people will search for.

How early you need to be: The playbook has no inherent window. But if you're betting on a company that is about to announce a native rewrite, you need to be shipping before that announcement. For Discord specifically, the window probably closes when the official Rust client goes public beta.

Signs you've misread this: ① After the official Rust client's public beta, Serein still gains 10+ stars a day. That would mean the differentiators (plugins, themes, zero telemetry) hold users on their own, and the Discord line isn't dead. ② The reverse: if a copycat like yapfast also hits thousands of stars within a month, this track has more traffic than expected, and latecomers can still win. ③ Discord starts broadly banning third-party client users or sending legal letters. Then the overall risk for projects that "build a native client for a big company" needs to be reassessed.

Data and sources

• Stars, forks and daily gains: GitHub repo page (as of 11-06). Day-by-day star gains and Rust chart rank come from Trendshift (trendshift.io/repositories/234457). Third-party records: gitnova 9-25 put it at 570 stars and judged the growth organic; Hysen Labs 9-21 at 551 stars.
• Memory and CPU comparison, warning box, feature list, install channels: Serein's README (read 11-06).
• Reddit posts: launch posts on r/foss, r/SideProject, r/opensourcealternative. Reddit blocks scraping of exact post dates and vote counts, so the match to star gains is inference.
• Official Discord news: @svishnevskiy tweet at 2026-11-04 20:44 UTC; TweakTown 2026-11-05 coverage; Hacker News "Native Discord desktop client in Rust" (11-04).
• Competitor and copycat star counts: each one's GitHub page (early November); yapfast at yapfast.com.
• No public data on downloads or active users, so this article doesn't estimate them.