Windows Central reported that searches for “Discord alternatives” are up 10,000%. People are clearly looking for somewhere else to go.
Daccord is one of the options. It’s a real-time chat platform with the shape Discord users will find familiar — servers, channels, voice, the lot. The interesting bit isn’t the feature list, though. It’s what’s under the hood.
Daccord runs on a game engine
This is the part that gets a raised eyebrow, so let me defend it.
The conventional stack for a Discord-style client is Electron plus React plus a WebSocket pipe. That gets you a 200MB binary, a Chromium per app, and an animation budget bottlenecked by the DOM.
A game engine flips every one of those numbers. The runtime is designed to keep a frame budget. Animations are free. The UI tree is owned by the engine, not by a browser. The installed size is a fraction of what an Electron app drags around. And the engine already handles every platform you care about with a single build pipeline.
The trade-offs are real but smaller than people expect:
- CSS is gone. You theme via the engine’s own theme system. Less flexible than Tailwind, faster to apply.
- The web ecosystem doesn’t drop in. No
npm install. No React component library. You build your own, or use what the engine community has built. - Hiring is narrower. “Has shipped a chat app in a game engine” is a small candidate pool.
What you get back is a client that doesn’t feel like a browser pretending to be an app. Boot times in fractions of a second. Memory footprint that doesn’t grow with idle channels. Smooth scrolling at high refresh rates because the renderer is built for exactly that.
Why now is the right moment
The Discord exodus is real but not uniform. Some people want a direct clone with different ownership. Some want self-hosting. Some want better moderation tooling. Some just want the app to stop eating their RAM.
Daccord lands in the middle of that. The familiarity is there if you want it. The runtime is different enough that the things that made Discord clunky on lower-end hardware aren’t there.
On building chat on a game engine
I get asked variations of “is that a serious choice” often enough to answer it once, here. A few things worth saying out loud:
- Real-time UI is what game engines do. Chat is a real-time UI. The fit is closer than the framing suggests.
- Voice and video pipelines already exist in the engine. You don’t have to glue WebRTC into a browser shell.
- The same build artifact is your desktop client, your mobile client, and (with some work) your web client. No three separate codebases.
The case against is mainly ecosystem maturity, and the answer to that is the same as for every other engine-built app: someone has to be first.
Try it
daccord.gg is the home page. If you’ve been looking for somewhere to point your community while you wait out whatever Discord is doing this month, it’s worth a look.