fluxer.com now has more than half a million accounts. The Fluxer apps work with self-hosted instances.

Read the post

Fluxer roadmap

This page lists what we're building for Fluxer in priority order, with the dates we expect where we've set one. Every item in the priority list goes into the free and open source Fluxer software (AGPLv3), and self-hosted instances get all of it too.

Last updated

How to read this page

In development
We've started building it.
Planned
We've committed to building it, and the dates are our current estimate.
Planned, no date yet
We've committed to building it, but we haven't set a date.
Considering
We haven't decided whether to build it, and it might not happen.

When two items need the same people, the higher one goes first. Some items lower down are already in development because they're smaller or can be built alongside the ones above. Dates are our current estimates, and when a date or the order changes, we update this page and list what changed at the bottom of the page.

Priorities

  1. Priority 1, Mobile apps on the App Store and Google PlayIn developmentWe expect iOS on the App Store in late November or early December 2026, and Android is on Google Play
  2. Priority 2, A new voice and video system with encrypted callsIn development2026
  3. Priority 3, FederationPlannedExperimental draft in 2026, stable in the first half of 2027
  4. Priority 4, End-to-end encryption for notes, DMs and group DMsPlannedExperimental draft in 2026, stable in the first half of 2027
  5. Priority 5, Threads, forums and publishing to the webIn developmentThreads and forums in early beta now, public forums as an experimental draft in 2026
  6. Priority 6, Slash commands, components and interactions for botsIn development2026
  7. Priority 7, Equip emoji and stickers from communitiesPlanned2026
  8. Priority 8, Creator paymentsPlanned2027 or later
  9. Priority 9, Activity statusIn developmentNo date yet
  10. Priority 10, Soundboard for voice callsPlanned, no date yet
  11. Priority 11, Polls and scheduled eventsPlanned, no date yet
  12. Priority 12, Built-in AutoMod for communitiesPlanned, no date yet
  13. Priority 13, Fluxer "Oxygen" on desktop and Linux phonesIn developmentNo date yet

What we're building

  1. Priority 1, Mobile apps on the App Store and Google Play

    Status
    In development
    When
    We expect iOS on the App Store in late November or early December 2026, and Android is on Google Play

    The iOS and Android apps have been open source on GitHub since 15 June 2026, and the first stable release of the Android app came out on 8 November 2026. You can download it from Google Play, and we keep putting out new beta versions of it.

    The iOS beta on TestFlight is on hold after a technical issue at Apple. Once the iOS app is on the App Store, anyone will be able to install it without a TestFlight invite or a free slot.

    We're also working on publishing the Android app on F-Droid and Accrescent, and we're looking into notifications that work without a separate app for Android phones that don't come with Google Play services. We haven't set a date for either of these yet.

  2. Priority 2, A new voice and video system with encrypted calls

    Status
    In development
    When
    2026

    We're replacing LiveKit, the software Fluxer uses for calls today, with our own voice server and new call code written in Rust, for the desktop, web and mobile apps.

    • Every call will be end-to-end encrypted with DAVE, an open protocol from Discord built on the MLS standard, and there will be no way to turn it off and no unencrypted fallback. You'll be able to check that a call is encrypted with a verification code.
    • Calls will send audio and video over QUIC and stop using WebRTC, and in a browser you'll need a recent version with WebTransport and WebCodecs to join a call. Joining will be faster, lost packets will be resent or filled in and the bitrate will adapt.
    • On Windows, macOS and Linux, the desktop app will encode and decode video on your graphics card wherever it can and use several CPU threads when it can't. Today's single-threaded software encoder is a known cause of choppy screen shares.
    • Each stream will get its own connection, and a stream will be able to handle far more viewers without slowing the call down for anyone else who is in it.
    • When network packets get lost on their way to you, the audio codec will be able to fill in much of the lost speech from the packets that did arrive.
    • Self-hosted instances without a voice server will be able to run peer-to-peer calls in the desktop app, with relays they run themselves or no relays at all.

    We also plan to let you invite people into a voice channel as guests without them needing an account, and Fluxer will remember the volume and mute setting you choose for each person's stream for the next time they stream. Neither of these has a date yet.

    Posts on Fluxer Feedback

  3. Priority 3, Federation

    Status
    Planned
    When
    Experimental draft in 2026, stable in the first half of 2027

    Federation lets people on different instances talk to each other, the same way email works between providers. It will always be optional, and every instance can keep running without it. We'll build it on polyproto-core, the base specification of the polyproto federation protocols that the Polyphony project maintains, and add our own extensions.

    The instance with your account will give you an identity like name@domain that you can use to sign in to communities on other instances, and your device will sign every message you send. polyproto-core also lets you move your account to a different instance.

    We'll use polyproto mainly for identity and moving accounts, and everything else stays Fluxer's own protocol. If a use case ever needs more than this model, we'll set limits and keep one copy of each community, so Fluxer doesn't turn into a "Matrix 2.0".

    The desktop app already keeps your accounts on several instances connected, and switching between them usually doesn't need a reconnect. Next, we'll combine them into one view, and you'll still be able to use a separate account on each instance once federation is out.

    The experimental draft will be a pull request that you can try and give feedback on. We're discussing federation in Fluxer Labs, our community on Fluxer, and you're welcome to join.

    Why polyproto and not Matrix

    Our main reason for choosing polyproto over Matrix is where a community's messages are stored. Every Matrix server that has a member in a room keeps its own full copy of that room, while each Fluxer community will be stored only on the one instance that hosts it.

    Storing a community in one place keeps an instance admin responsible only for content they chose to host, and it keeps self-hosting cheap for small instances with no copies to keep in sync. A community is unavailable whenever the instance that hosts it is offline, though. polyproto also lets us keep Fluxer's own API and permission system.

    A bridge can connect Fluxer and Matrix, the same way bridges already connect Matrix to many other chat platforms, and Fluxer won't federate with Matrix directly.

  4. Priority 4, End-to-end encryption for notes, DMs and group DMs

    Status
    Planned
    When
    Experimental draft in 2026, stable in the first half of 2027

    End-to-end encryption (E2EE) means only the sender and the people a message is meant for can read it, and the service in between can't. Today, Fluxer encrypts messages in transit between your device and our servers, and the servers can decrypt them once they arrive.

    AliceHello Bob!
    Encrypted with Bob's public key
    What the server sees6EB69570 08E03CE4
    Decrypted with Bob's private key
    BobHello Bob!
    Public-key encryption is the building block of end-to-end encryption. Alice encrypts a message with Bob's public key, and only Bob's private key can decrypt it. The server in between sees only unreadable data.

    We'll add end-to-end encryption to personal notes, DMs and group DMs, with no setting to turn it off, and we're building it on MLS, an open IETF standard. The first design leaves some details visible to the server, such as who is in a conversation and when each message is sent, and we'll look into encrypting more of this metadata in a later version.

    Group DMs will grow from 50 to 250 members on the same timeline. We plan to let you tie an encrypted group DM to a community, but we haven't set a date yet. Voice and video calls will get end-to-end encryption before all of this, with the new voice and video system.

    We're starting with DMs and group DMs because they're simpler to get right. Each one has a known set of members, with no moderators, roles, channel permissions or search across a large community. Communities also keep getting new members who expect to read what was posted before they joined, and that's much harder to do with end-to-end encryption.

    Once encrypted DMs and group DMs have matured, we'll look into end-to-end encryption for communities, such as smaller communities or specific channels in a community. Large public communities with moderation and search are the hardest fit for end-to-end encryption.

  5. Priority 5, Threads, forums and publishing to the web

    Status
    In development
    When
    Threads and forums in early beta now, public forums as an experimental draft in 2026

    Threads and forums are in early beta for everyone on web, desktop, iOS and Android, and a community will be able to give a new forum channel an optional public web mode.

    Anyone will be able to read the posts in a public forum without having an account, find them in search engines, save them in archives and follow them with RSS or Atom feeds.

    A community will decide whether a forum channel is public when it creates the channel, and a private forum channel won't be able to become public later. Everyone who posts in a public forum will be able to see that it's public before they write anything.

    Announcement channels will also be able to get a public page with RSS and Atom feeds, but only if the community turns that on for that specific channel. Messages in regular chat channels, DMs and group DMs will never be published on the web.

    Fluxer won't use AI or LLMs to write, summarise or choose anything on a public forum, and a public page will show only what people wrote. Our automated safety checks, listed in section 5 of our privacy policy, include a small image classifier that flags explicit images so they're hidden from people who don't want to see them and from anyone under 18.

    We also plan to add a view of every thread in a community in one place and a feed layout for media channels, and we haven't set a date for either of them yet.

  6. Priority 6, Slash commands, components and interactions for bots

    Status
    In development
    When
    2026

    Bots and integrations will get slash commands, interactions and components like modals and buttons, and we've started with letting bots register their own commands.

    We also plan to add a way to discover bots and to let bots use custom emoji from the other communities they're in, but we haven't set a date for either of them yet.

  7. Priority 7, Equip emoji and stickers from communities

    Status
    Planned
    When
    2026

    You'll be able to equip emoji and stickers from a community you're in and keep them on your account after you leave that community. On many chat platforms, you have to stay in a community to keep using its emoji and stickers elsewhere.

    On fluxer.com, equipping will be part of Plutonium, the same way using custom emoji and stickers across communities is today. Inside a community, everyone can use its emoji and stickers for free, animated ones included. Each community can have up to 500 emoji and 500 stickers, and on self-hosted instances, the instance sets the limits.

    We'd also like to let people without Plutonium equip at least a few of their favourite emoji and stickers to use across communities. Plutonium helps fund the cost of running fluxer.com, and we're still working out how much of this we can offer for free.

    We also plan to add emoji packs that group emoji together and to let you upload emoji for DMs and group DMs without adding them to a community, though neither has a date yet.

  8. Priority 8, Creator payments

    Status
    Planned
    When
    2027 or later

    We plan to let fans pay to unlock roles and exclusive content in a creator's community, for good or for a limited time, with a one-time purchase or a recurring subscription.

    Creators will also be able to sell tickets for events, where a ticket or a temporary role opens specific text and voice channels in the community for the whole length of the event.

    Creators on fluxer.com will be able to run their community and take payments in one place. fluxer.com will handle the payments and take a fee of most likely 5 to 10% of each payment, to help pay for hosting fluxer.com and developing the open source software behind it.

    Like the rest of the roadmap, creator payments will come to self-hosted instances too. Those instances are run by separate people and organisations, and Fluxer won't take any cut of the money that creators on them receive from their fans and supporters.

  9. Priority 11, Polls and scheduled events

    Status
    Planned, no date yet

    We plan to add polls and scheduled events to communities. Until they're out, communities can post events in an announcement channel and use bots for reminders.

    Posts on Fluxer Feedback

  10. Priority 13, Fluxer "Oxygen" on desktop and Linux phones

    Status
    In development
    When
    No date yet

    Our iOS and Android app is built with Flutter, and Fluxer "Oxygen" is its codename for now. We've started building a desktop version of it for Windows, macOS and Linux as a separate download, and our Electron desktop app will stay and keep getting updates.

    We also plan to make Fluxer "Oxygen" work on Linux phones, and we'll look for people to test it in Fluxer Labs, our community on Fluxer, when it's ready to try.

Smaller changes without a date

Moving fluxer.com to Sweden

Status
In development
When
By the end of 2026, if all goes well

We're moving fluxer.com's stored data from US hosting to our own hardware in Sweden, with space, power and network from 31173 Services AB, a Swedish data centre and network provider. We expect having our own hardware and network to make fluxer.com more stable.

Suggest a feature or vote

If something you want isn't here, post it on Fluxer Feedback or vote for a post that already asks for it. You sign in there with your Fluxer account, and people on our team read the posts.

Votes and comments help us decide what to plan next, and we set the order ourselves after weighing how much work something takes and what it needs first. When we mark a post as "Planned" on Fluxer Feedback, we add it here, in an item or with the smaller changes.

You can talk about the roadmap with our team and others who use Fluxer in Fluxer Labs. Please email security issues to security@fluxer.com and don't post them on Fluxer Feedback.

Help fund Fluxer

The work on this page is paid for by the people who use Fluxer and choose to support it, and Fluxer doesn't have venture capital or any outside investors.

  • Subscribe to Plutonium if you use fluxer.com and want higher limits and extras on your own account, such as using a community's emoji and stickers in other communities. Communities, messages, voice and video calls and screen sharing work without it. You can also give Plutonium to someone as a gift that never renews.
  • Get an Operator Pass, an optional one-time purchase that supports Fluxer. It comes with a numbered Operator certificate, the Operator badge and a spot on the Operators' wall, and you don't need one to use Fluxer or to run your own instance.
  • Donate once, every month or every year, as an individual or on behalf of an organisation. A donation is a gift to Fluxer that comes with nothing in return.

You never need to pay to use Fluxer or to self-host it, and paying doesn't move an item up this list or give your posts on Fluxer Feedback more weight. Plutonium, the Operator Pass and donations pay for running fluxer.com and building the open source software.

You can also help without paying by translating Fluxer into your own language or contributing code on GitHub, and telling your friends and followers about Fluxer helps too.

Recently released

  1. 8 November 2026 The first stable release of the Android app came out on Google Play.
  2. 1 November 2026 Role icons came to the web and desktop apps.
  3. 16 October 2026 Threads and forums came out in early beta on web, desktop, iOS and Android.
  4. 16 October 2026 The new version of our Electron desktop app became stable on Windows, macOS and Linux.
  5. 15 June 2026 The iOS and Android apps became open source on GitHub.
Changes to this page
  1. 16 November 2026 We moved the roadmap from the blog to this page. We added priorities 9 to 13 and the smaller changes from posts marked "Planned" on Fluxer Feedback, along with the move to Sweden.
  2. 26 January 2026 We published the roadmap as the Roadmap 2026 blog post, and we updated that post as our plans changed until it moved here.