Saw this issue in a GamersNexus video and was surprised to see there wasn't anything to document it in the Github.
Clicking the "Self-hosting guide" hyperlink in the readme takes you to https://docs.fluxer.app/self-hosting which 404's.
See: https://feedback.fluxer.com/p/238
From what I’ve seen the official documentation is still in the works, but folks are tinkering and getting test builds running in the meantime.
I don't have the knowledge necessary to write the self-hosting documentation myself, but I'm planning to submit a PR to update links to the self-hosting documentation to point to the Overview page for self-hosting (so the link(s) work as expected once the documentation is written).
It won't add much value while documentation is still being written, but hopefully it'll make it easier to find the documentation once it's published (and give the core maintainers one less thing to worry about as they're trying to handle the sudden influx of interest in Fluxer).
Edit: I fixed the broken links in my fork of the Fluxer repo, but the maintainers have "limited the ability to open a pull request to users that are collaborators on this repository," preventing me from opening a PR for the changes. I'm going to keep an eye out in case I'm able to submit the PR, but it's possible that the maintainers will fix the broken links themselves as they're writing the self-hosting documentation.
You technically can self host, but be prepared to tinker. A lot. The app is really not set up in its current state for people to do that.
That said, about a week in, I feel I have ironed out the quirks quite nicely, and it works pretty much without issues.
I'm documenting my findings in this discussion, I'm hoping this can serve as a good resource for other early adopters and the eventual docs.
https://feedback.fluxer.com/p/1037
Related to self hosting once that is available, how will desktop and eventually mobile apps work? Element has a nice setup where you can pick the matrix server on login, instead of some other apps where you have to compile it yourself, so will that be possible?
Official self-hosting support lands in 3-4 weeks, by the way!
I replied on a Reddit thread where users voiced concerns that self-hosting was nowhere in sight. This was a very short amount of time after we'd decided on the internal time frame and scope of work needed for "v1.5", so to speak, where we'll be combining the good things that came out of my speculative v2 restructuring of the backend codebase with all the nice things going on in the canary build of Fluxer (https://canary.fluxer.app/download).
Canary includes screensharing with audio, text-in-voice, fixes to DM calling, a revamped and improved system for managing input and output devices and mic processing settings, and bug fixes to hundreds, literally, of bugs, thanks to the help of the people in Fluxer Testers. You too can become a tester by installing the canary desktop client or using the canary web client and joining Fluxer Testers by pressing the in-app banner.
Canary really is streets ahead of stable. We recently crossed build v0.0.200, compared to v0.0.8 of the original stable desktop client. I'm currently finalising the last bug fixes to make sure that screensharing and the other core features all work as they should before promoting canary to stable, and this will happen very soon.
In light of the recent outages, I'm also working on bringing the new backend infrastructure, inspired by the work done on v2, into the existing backend. The goal is to make sure Fluxer always runs silky smooth, without disruptive downtime or performance issues.
So here's what's coming: within 3-4 weeks, official self-hosting support lands. By then I'll have cleaned up and strengthened the codebase, abstracted away sensitive details about our safety system to prevent adversarial misuse, properly documented the entire API, written proper self-hosting guides, published Docker images, built a web-based setup wizard, and created a one-line command for setting up a Fluxer instance from scratch. On top of that, you'll be able to connect to alternative backends and account-switch between them in the desktop app.
That's what you can look forward to!
10 comments
Off-topic comment by @hihi217
Comment by @SaulGoodman1337
Comment by @DopleZZ
Comment by @Gaffers2277
Comment by @Atrophied
Comment by @darkroastcreative
Comment by @mgabor3141
Comment by @d10sfan
Comment by @UnknownLITE
Off-topic comment by @clockwinder
5/16/2026: