The Discord migration that didn't happen

In February 2026, Discord announced that every account would default to a teen-appropriate experience starting in March, with adult features gated behind facial age estimation or a government-ID upload. The announcement landed five months after a third-party verification vendor had been breached and had leaked roughly 70,000 customer IDs and selfies. The combination — surveillance plus demonstrated negligence — produced an immediate backlash, and the headline figure that ran in most coverage was a 10,000% overnight spike in Google searches for "Discord alternatives."

Two months later, that headline number is interesting for a different reason than the one it implied at the time. The spike was real. The migration mostly wasn't.

The cleanest way to read what actually happened is to look at where attention went during the spike and where it stayed afterward. English Wikipedia publishes daily pageview data for every article through a public API; the numbers don't move based on how an alternative is marketed or which Reddit thread an admin happened to read. They move when a person sits down, types a name, and looks the thing up. For the period 2026-01-01 through 2026-04-29 — covering the pre-rollout baseline, the spike, and the tail — the Wikipedia numbers tell a more interesting story than the listicles did.

The spike was real

The announcement landed February 9. Every candidate's Wikipedia article saw an obvious surge within a day or two:

• Element, the reference Matrix client, peaked at 4,284 views on February 9. Its pre-rollout baseline (January 2026 average) was 179 views per day.
• Matrix (the protocol itself) peaked at 3,566 views on February 10, against a 372-per-day baseline.
• Zulip peaked at 1,285 on February 10. Baseline 149.
• Stoat (formerly Revolt) peaked at 1,036 on February 10. Baseline 27.
• Rocket.Chat peaked at 823 on February 10. Baseline 94.
• Mattermost peaked at 536 on February 10. Baseline 223.

The dominant winner during the spike, by a comfortable margin, was Matrix and its main client Element. That tracks with what the listicles were saying at the time: the federated, decentralized, get-out-of-corporate-cloud answer to Discord's surveillance problem. Privacy Guides recommended Matrix. Trade press recommended Matrix. The pageviews say: yes, that's where most of the curiosity went.

It was also where the curiosity left fastest.

What sustained, and what didn't

Pulling the same articles' pageview averages for the most recent two weeks (April 15 through April 29) produces a different picture:

• Stoat: 80 views/day. +196% vs the January baseline. Still elevated.
• Rocket.Chat: 131 views/day. +39%. A modest, durable bump.
• Matrix (protocol): 338 views/day. −9%. Returned to baseline.
• Element: 147 views/day. −18%. Below the pre-rollout baseline.
• Mattermost: 164 views/day. −26%. Below baseline.
• Zulip: 65 views/day. −56%. Well below baseline.

Mainstream messengers — Telegram, Signal, WhatsApp, IRC, XMPP — all show roughly the same pattern: a small spike during the news cycle, then a return to or below their pre-rollout levels. None of them captured the moment.

So: the alternative the listicles pointed to most loudly attracted the most curiosity during the panic and converted it the worst. Element specifically is below its pre-rollout baseline two months later. The only candidate showing a clean, durable elevation is Stoat. The only other candidate showing measurable sustained interest is Rocket.Chat, modestly.

That is not a migration. That is a search spike.

This is a useful framing, because it changes what the article is actually about. The question worth asking is no longer "where is everyone going" — most communities went nowhere. The question is "of the people who did move, why did they end up at Stoat instead of at the federated, principled, well-marketed answer everyone was telling them to choose?" And, as a follow-on: of the alternatives the listicles ranked, which ones are actually competing for Discord's users, and which are sitting in lists for product-category reasons that have nothing to do with what a community admin actually wants?

Why the dominant search winner didn't convert

Matrix is the only federated, openly-specified, multi-implementation chat protocol with current institutional weight behind it. The governance lives at the Matrix.org Foundation. The reference server, Synapse, is developed primarily at Element, the company. Element makes a series of clients — Element web, Element X on iOS and Android — and a commercial enterprise product, the Element Server Suite Pro, which is what gets sold to governments and large organizations. The French government's DINUM joined the Foundation as a Silver member in 2025. The Bundeswehr runs on Matrix. The Swedish government runs on Matrix. There is a real institutional spine here.

There is also a real funding problem.

The Foundation posted in February 2025 that it would have to shut down all its hosted bridges — to Slack, XMPP, OFTC, Snoonet — unless it raised $100,000 by end of March. Element pledged to keep the OFTC bridge alive specifically. The 2024 numbers in that post: $561K revenue, $1.2M operating costs, a $356K deficit closed by liquidating the Foundation's cryptocurrency reserves. By the time the Discord-alternatives spike happened a year later, the situation hadn't really resolved. The April 2026 Governing Board report states it directly: "the Foundation is still struggling from a resources perspective and still can't cover the bare minimum requirements." The Slack bridge was removed entirely in January 2026, listed as unmaintained.

The protocol survives. The institution running the protocol cannot reliably afford to.

That's the funding side. The product side is similar. Element, the company, pivoted in 2024 to AGPLv3 plus a "Build" commercial license, explicitly to make money from organizations that want to ship proprietary products on top of Matrix. The growth markets are governments and enterprises buying Element Server Suite Pro. None of that is wrong — open-source maintainers have to eat — but it's worth noticing what it means for a Discord refugee. The people building the most prominent Matrix client are, by their own roadmap, optimizing for a buyer who looks like the German federal government, not for a 5,000-person Minecraft community.

The federation paradigm itself also carries a tax that listicles tend to soft-pedal. Joining a Matrix homeserver is not joining a Discord server; it's federating an account on one homeserver into a room hosted by another. Bridges break. Identity-server churn produces lost contacts. Voice and video on Matrix are meaningfully better than they were three years ago, with Element Call and MatrixRTC, but the role hierarchies, server-level moderation tooling, and admin workflows that a Discord community actually relies on lag what people are used to.

The pageview tail is consistent with this. Matrix and Element attracted the most curiosity during the spike; the people who looked into it most enthusiastically were also, apparently, the most likely to look back at their Discord and decide it was good enough.

The Slack-shape options were never really the answer

Mattermost, Rocket.Chat, and Zulip showed up on every Discord-alternatives list published in February. They are all real, well-engineered products with active maintainers, and they are all built for company team chat, not for communities.

Mattermost is US-based, headquartered in Palo Alto. The free Team Edition is MIT-licensed and supports up to 250 users without single sign-on. Above that, or if you need LDAP, SAML, MFA enforcement, retention policies, or compliance exports, you're on the paid tiers. It's an excellent Slack replacement, sold to governments and regulated industries, and it's what you stand up if your security team needs to keep team chat off US cloud providers. None of that is what a community admin wants.

Rocket.Chat is Brazilian-headquartered — a jurisdictional fact that's genuinely under-discussed. The self-hostable Community Edition is mature; there's also a "Starter" perpetual-free tier capped at 50 users. The +39% sustained pageview bump was bigger than I would have predicted, and probably reflects the fact that Rocket.Chat fits both a company team-chat use case and a smaller-community use case better than its peers. If any of these mature options is being adopted in real numbers by ex-Discord communities, it's most plausibly Rocket.Chat.

Zulip has the cleanest funding story in this group. Zulip Cloud subsidizes self-host development; the project is licensed Apache 2.0 with no enterprise pivot pressure. The catch is that Zulip's threaded-conversation paradigm is the most foreign to anyone migrating from Discord. Communities don't want threads-as-a-religion; they want channels they already know how to use.

The pageview tail says all three of these had a small February spike and have since cooled to or below their baselines. They were never really being seriously evaluated as Discord replacements; they were being looked up because every "Discord alternatives" listicle includes them.

Stoat: the only candidate that stuck

Stoat is the only candidate whose pageviews stayed elevated. The project is the same one that was called Revolt until October 2025, when a trademark cease-and-desist forced the rebrand. Most users, servers, and core values carried over.

The legal entity behind Stoat is a UK-incorporated company about a year old, with one director — Paul Makles, the project's longtime maintainer. The company hasn't filed accounts yet, so the financial picture is genuinely unknown; anyone citing specific turnover numbers for Stoat is guessing.

This sounds, on its face, like exactly the kind of structurally fragile project you should not bet a 5,000-person community on. One person controls the company. The company has been around for a year. Trademark issues forced a rebrand that, for an organization with legal counsel on retainer, would have been resolved before incorporation. The code-side bus factor is healthier — the GitHub org has multiple active maintainers — but the legal entity has one director.

It's worth saying directly that this is more sustainable than it looks, because of a fact that doesn't show up in Companies House filings.

Makles also works at FUTO, the foundation Eron Wolf set up to underwrite anti–Big-Tech open-source work — the same outfit funding GrayJay, Immich, and a number of other projects in this category. Whatever else is uncertain about Stoat's financial trajectory, the person controlling its legal entity is not a starving solo developer dependent on Ko-fi to eat. He has a day job at a foundation whose entire purpose is to keep work like this going.

That doesn't fully neutralize the bus-factor-of-1, but it changes its character. A solo maintainer who quits because they can't pay rent is one failure mode. A solo maintainer who keeps the company alive on the side because his rent is covered elsewhere is a different one.

The other thing that distinguishes Stoat — and the most plausible explanation for why its pageview tail is the only sustained one — is that it looks and feels like Discord. Servers, text channels, voice channels, roles, permissions. Voice chat shipped in Q1 2026; video calling is the most-requested feature and is in active development. There's a docker-compose deployment for self-hosting. Donations run through Ko-fi. The whole thing is AGPLv3.

For a community admin who wants a Discord-shape replacement and not a federated-protocol experience or a corporate team-chat tool, Stoat is the only candidate in the field that even tries to be that. The pageview data suggests that's exactly what the people who actually migrated were looking for.

What Fluxer is, and why I'd watch it instead of recommending it

Fluxer is the project that's grown fastest by sheer GitHub-stars metrics — over 8,000 — and shows up most often in 2026 "best Discord alternative" coverage. Made in Sweden, registered as Fluxer Platform AB. The founder is Hampus Kraft, 23, finishing a CS degree at KTH, and was working solo until recently. The project's 2026 roadmap confirms what the public information already suggested: the company sold around 1,000 lifetime "Visionary" supporter packages at $299 each in February, raising roughly $299,000, and has hired one additional person. There's a $4.99/month consumer subscription called Plutonium that mirrors Discord Nitro's cosmetic perks. There are also unpaid Flutter-developer volunteers building the native mobile clients.

Fluxer is an interesting project to watch. It is not a project I'd recommend committing a community to in 2026. The text protocol does not have end-to-end encryption — the roadmap explicitly says text E2EE is deferred in favor of feature parity with Discord. There are no native mobile apps yet, only a progressive web app. Federation is in development with no completion date. Self-hosting is "coming very soon" but not actually shipped at the time of this writing.

The concern isn't whether Hampus can ship features fast enough — he obviously can, and the AI-assisted development tools available in 2026 make that velocity plausible at the team size he has. The concern is the maintenance, customer-support, abuse-handling, security-disclosure, and incident-response burden that comes with running an actively-used Discord competitor. That work doesn't compress with LLM-assisted velocity the way feature development does. A two-person team running a chat platform that markets itself as a Discord replacement is taking on a workload that, historically, has required full-time trust-and-safety operations, full-time platform-abuse review, and a security-disclosure policy with an actual on-call rotation. The Visionary round buys maybe 18-24 months of one Stockholm engineer's salary. After that the math has to change.

Fluxer is the strongest single case study for a separate question: how AI-accelerated development changes the lifecycle of small open-source projects. The interesting outcome is not whether the product gets to feature parity with Discord. It's whether a project shipping at LLM-assisted velocity can survive the operational scale that follows from being adopted at LLM-assisted velocity.

If you're a community admin reading this in April 2026, my honest read is: don't move yet. If you're going to move, Stoat is the only candidate the data supports as a sustained landing spot. If you're going to watch something, watch Fluxer for what it tells you about how the next generation of small chat platforms scales — or doesn't.

Why most communities stayed on Discord

The pageview data also has to be interpreted alongside Discord's actual response to the panic, which was more substantive than "we delayed the rollout."

The H2 2026 plan that Discord announced after the backlash added credit-card verification as an alternative to facial estimation and ID upload. It committed to documenting every verification vendor publicly with the practices each one uses. It set a new requirement that any partner offering facial age estimation must perform it entirely on-device — directly addressing the third-party-vendor breach concern that triggered the panic in the first place. It introduced a new "spoiler channel" type, distinct from NSFW channels, recognizing that the communities Discord was about to break are the ones using age-restricted channels for spoilers and political conversations rather than for adult content. Age-assurance data will be included in transparency reports.

You can argue these concessions are sufficient or insufficient. The thing you can't really argue is that they didn't happen. Discord made specific product changes in response to specific user objections, and the news cycle around the panic was largely satisfied by them. Switching costs to leave Discord are very high; the friction of re-creating a 5,000-person server somewhere else with retained history and bot integrations and member identity is enormous; and Discord absorbed the impact by changing what it had announced.

That is the answer to "why did most communities stay." The follow-on question, the one this article exists to address, is what's worth paying attention to next.

What's actually worth watching

Discord's age-verification rollout was the wrong reason to be alarmed about Discord, in the sense that the regulatory pressure that produced it isn't going away regardless of which platform you migrate to. UK, EU, and US-state-level age verification requirements affect every chat platform large enough to matter. Stoat at scale would face the same regulatory framework.

The right reason to be alarmed about Discord, if there is one, is the monetization arc. While the age-verification narrative dominated the cycle in February, Discord shipped a redesign of its Quest advertising surface in April that Discord's own internal Business Newsletter described as a "Full-screen Takeover," using the brand name Hero Ads. That description got pushback in r/discordapp, and an account claiming to be on Discord's ads team replied in-thread saying the description was overstated and the placement is just a banner takeover within Quest Home. Worth knowing: that account has no Reddit verification flag, no distinguished tag, and a comment history dominated by hockey and woodworking. The clarification may be accurate; Discord has not officially clarified anything.

Around the same time, Discord cut the per-quest Orb reward from 700 to 200 — the in-app currency users earn from the opt-in ad system — and bundled Nitro with what looks like a cut-down version of Xbox Game Pass. Server boost prices increased meaningfully at checkout. There's a pattern here, and unlike the age-verification story, Discord isn't walking it back.

If you're a community admin tracking when to actually move, the signal isn't going to come from regulation. Regulation Discord can engineer around, as it just did. The signal will come from monetization decisions like Hero Ads, where Discord is making the product progressively worse for people who don't pay and progressively more expensive for the people who do, and where there isn't a regulator to negotiate with. That arc isn't going to reverse.

The migration that didn't happen this year is probably going to happen anyway. The data won't show a 10,000% spike when it does. It'll show up the way real migrations always do: slowly, in pageview tails, in Discord servers that quietly add a Stoat link to their pinned messages, in admin posts on r/selfhosted that nobody upvotes, in subscriber numbers on a Ko-fi that doesn't make the news.

Watch Stoat. Watch what Discord ships next month, not what it rolled back last month. Don't move yet.