Is Fluxer based on Matrix?

No. Fluxer isn't based on Matrix or any other chat protocol, and it has its own API and its own real-time gateway. Our planned federation will be built on polyproto.

Is Fluxer based on Matrix?

No. Fluxer was built as its own platform, and the code is open source if you want to check. Fluxer isn't federated yet, and when federation comes, it will be built on polyproto-core, the base specification of polyproto, with our own extensions on top. It's item 3 on Roadmap 2026, which plans an experimental draft in 2026 and a stable release in 2027.

Why polyproto and not Matrix?

The main reason is where a community's messages are stored. In Matrix, every server with a member in a room keeps its own copy of that room, while in Fluxer, a community will be stored only on the instance that hosts it and on no other instance.

Once federation is out, a message you delete will be deleted on the instance that hosts the community, which will be the only instance with a copy of it. For fluxer.com, the instance we run, section 7.3 of our privacy policy says when a deleted message is also gone from our backups, and for any other instance, that instance's own privacy policy tells you.

A small instance also won't have to store other instances' large communities. The trade-off is that a community will be unavailable while its instance is offline. The roadmap gives all our reasons for choosing polyproto, with links to the Matrix specification for comparison.

Can I bridge Fluxer to Matrix?

Fluxer won't federate with Matrix directly, and there's no official bridge from Fluxer to Matrix or any other network. A third-party bridge could still connect the two networks, the same way bridges already connect Matrix to many other chat platforms.

Third-party bridges aren't made or reviewed by Fluxer. A bridge can do anything the token you give it allows, so only give a token to a bridge you trust.