Roadmap 2026 | Fluxer← Back to blog
Updated 24 May 2026: this roadmap has changed a lot since the January beta. Fluxer is now operating at a much larger scale, the canary client is far ahead of the original stable release, native mobile is in testing, and the backend reliability work is no longer theoretical.
Discord will require a face scan or ID for full access next month<br>Age verification for all.<br>The VergeStevie Bonifield
Fluxer is still in public beta, but it has changed a lot since January. The hosted instance had to grow up quickly after Discord's age-verification announcement, and the roadmap now puts reliability, safety, self-hosting, and fewer incidents alongside new features.
I've also updated the longer release post that explains how Fluxer got here, the architecture, and the reasoning behind it:
How I built Fluxer, a Discord-like chat app<br>Fluxer is a free and open source instant messaging and VoIP chat app built for friends, groups, and communities.<br>Fluxer BlogHampus Kraft
Fluxer already covers a lot of what people expect from a modern chat app. The next phase is about making it steadier: fewer client bugs, self-hosting that is easy to set up, safer infrastructure, better moderation tools, and fewer incidents.
#1: Canary to stable, and native mobile
The canary client is now the best way to use Fluxer. It has moved well past build v0.0.200, compared with v0.0.8 for the original stable desktop client, and it includes hundreds of fixes plus major voice and video improvements: screen sharing with audio, text in voice, better DM calls, a stronger device selector, more mic processing controls, noise suppression through DeepFilterNet3, and LiveKit-backed E2EE for voice and video in enrolled testing communities.
You can try it today through the canary desktop build at canary.fluxer.app/download, or in the browser at web.canary.fluxer.app. Canary moves to stable after the last serious bugs are fixed. Voice and video E2EE rolls out more broadly soon, then becomes enforced as supported clients catch up.
The launch PWA had rough edges, but the web platform let Fluxer ship across web, desktop, and mobile from day one. It will keep improving while the native app moves through testing.
Native mobile is happening in parallel. The iOS and Android app is built with Flutter, and as of 20 May 2026 it is being tested with Visionaries. The rollout is staged: Visionaries first, then a Plutonium beta, then a public release. The app code will be open source too.
Flutter also gives us an interesting desktop path later. Mobile comes first, and Flutter can become an alternative to Electron.
#2: Self-hosting and the backend cleanup
Official self-hosting support is the next major release after canary stabilisation. The target is early to mid June 2026. That release includes Docker images, documentation, a web-based setup flow, and a simple setup for a typical instance: API, Gateway, Worker, Media Proxy, database, an in-memory store, and NATS.
The current docs are pretty mediocre, and I am sorry about that. Brand new API docs and self-hosting docs are coming with that release.
The hosted Fluxer.app deployment is much larger than a normal self-hosted instance will ever need to be. It now includes the TypeScript API and Worker, the clustered Erlang Gateway, the Rust Media Proxy, NATS, and new Rust data services for caching and read-heavy data paths. Self-hosting needs the benefits of that work without requiring people to understand the whole hosted setup.
The Gateway clustering work is a recent example. Fluxer started with one Gateway node because the original design was built for a much smaller user base. After the growth spike, that design became a reliability problem. We rolled out Erlang Gateway clustering, then split the gateway into specialised tiers: stateless websocket pods for client connections, and separate stateful clusters for sessions, guilds, presence, calls, and push notifications. All tiers discover one another through Erlang distributed clustering. A guild pod failure now only affects guilds on that pod instead of every connected user, and we can scale each tier on its own.
Scheduled maintenance - Incident details - Fluxer - Status<br>Scheduled maintenance window on 24 May 2026 for the Gateway role-split deployment and associated reliability improvements.<br>Fluxer Status
Those Rust data services belong to the same self-hosting and reliability work. They sit in front of Cassandra to cut repeated reads through request coalescing and caching, so a flood of identical lookups for the same hot key collapses into one database hit. The Gateway keeps presence, member lists, and the rest of its hot real-time state in Erlang, which is what Erlang is good at.
At launch, the Electron desktop app will support connecting to custom backends through in-app account switching. You will be able to point the regular desktop client at your own instance without waiting for full federation.
The Operator Pass comes...