Netcore Cloud
Netcore is selling marketing agents and privacy-safe personalization, mostly through blog posts.
A side-by-side editorial comparison of Openfire and Dendrite — release velocity, themes, recent moves, and the top alternatives to consider.
Openfire's 5.1 line pairs XMPP channel binding with a steady cleanup of its own crypto
Six releases across the 5.0 and 5.1 lines, each a long list of numbered improvements and bug fixes. The 5.1.0 release is the substantive one: support for channel binding, an admin console page for reviewing failed server-to-server connection attempts, visible S2S ports, and removal of a hardcoded initialization vector and a weak SHA-1-derived Blowfish key. The rest is multi-user chat correctness, pubsub behaviour and dependency currency.
A forked, relicensed Dendrite spent its first year catching up on Matrix protocol and security debt
The window opens with the first release after forking from matrix-org/dendrite under AGPLv3, which fixed long-standing state-reset bugs and added I2P and Onion listening. What follows is a security release closing a server-side request forgery vulnerability, then a release adding room version 12 support and two MSC implementations, and finally two quick patches for unresponsiveness, v12 room joins and malformed PDUs blocking whole transactions.
Six releases across the 5.0 and 5.1 lines, each a long list of numbered improvements and bug fixes. The 5.1.0 release is the substantive one: support for channel binding, an admin console page for reviewing failed server-to-server connection attempts, visible S2S ports, and removal of a hardcoded initialization vector and a weak SHA-1-derived Blowfish key. The rest is multi-user chat correctness, pubsub behaviour and dependency currency.
Two consistent threads run through the window: replacing the older cryptographic shortcuts still sitting in the codebase, and making federation failures diagnosable rather than silent. Multi-user chat and pubsub keep generating the highest volume of fixes, which is a fair map of where a working XMPP server actually spends its time.
Expect the 5.1 line to continue with MUC and pubsub fixes plus further dependency upgrades, with any remaining legacy crypto paths the most likely target for the next round of hardening.
The window opens with the first release after forking from matrix-org/dendrite under AGPLv3, which fixed long-standing state-reset bugs and added I2P and Onion listening. What follows is a security release closing a server-side request forgery vulnerability, then a release adding room version 12 support and two MSC implementations, and finally two quick patches for unresponsiveness, v12 room joins and malformed PDUs blocking whole transactions.
This is a fork proving it can carry a homeserver. The order is telling: license and state correctness first, then a CVE, then protocol currency with room version 12, then the operational bugs that surface once people actually run it. Several fixes carry outside contributor credits, which is the fork's clearest sign of life.
Expect continued protocol catch-up on newer MSCs and room versions plus operational fixes, since federation compatibility is the constraint that sets this project's agenda.
Other Comms products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Openfire or Dendrite.
Netcore is selling marketing agents and privacy-safe personalization, mostly through blog posts.
Krisp turned noise cancellation into a contact-center AI stack — and now defends it against deepfakes.
Signal is quietly rebuilding group governance while polls and pins push into everyday chats
Trumpia publishes SMS marketing explainers where its release notes should be.
Bandwidth is finishing PSTN replacement country by country while opening the network to AI voice agents.
Adding email to the stack so voice, SMS, WhatsApp and inference all bill as one API
See all Openfire alternatives → · See all Dendrite alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — federation — within Comms. Openfire is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Openfire is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top Openfire alternatives in Comms are ranked by recent ship velocity. Browse the "Openfire alternatives" section above for the current picks, or visit /alternatives/openfire for the full list with editorial commentary on each.
Top Dendrite alternatives in Comms are ranked by recent ship velocity. Browse the "Dendrite alternatives" section above for the current picks, or visit /alternatives/dendrite for the full list with editorial commentary on each.