Apache RocketMQ
The RocksDB migration reaches native code as the legacy DLedger broker mode is marked for removal
A side-by-side editorial comparison of Fellow and NanoMQ — release velocity, themes, recent moves, and the top alternatives to consider.
Fellow's public changelog has been silent since 2021 — no recent direction is observable here.
The visible signal stops in spring 2021. The last few releases were calendar-extension touch-ups: action items appearing directly in the Google Calendar extension, public view-only meeting links for external attendees, and multi-calendar sync within a single Google or Office account. Nothing in this dataset reflects the past several years of Fellow's actual work.
A protocol-layer correctness pass, delivered largely by first-time contributors
0.25.6 is a bug-fix release the maintainer recommends to every user on an earlier tag, and its weight sits in NanoNNG rather than the broker: unsuccessful CONNACK negotiation is now rejected, Session Expiry Interval is accepted in CONNACK, pipes closed during the unlocked auth window are no longer registered, receive pipes unlink on session handoff, and a strict property checker guards against malformed input. Two potential security issues are patched, SCRAM handling hardened, and a workaround added for an NNG TLS idle bug. Four of the contributors are making their first commit to the project.
The visible signal stops in spring 2021. The last few releases were calendar-extension touch-ups: action items appearing directly in the Google Calendar extension, public view-only meeting links for external attendees, and multi-calendar sync within a single Google or Office account. Nothing in this dataset reflects the past several years of Fellow's actual work.
From the entries alone, no current trajectory can be inferred — the data is years stale. Whether Fellow has shifted to AI-meeting-notes or remained focused on the original meeting-management surface is not visible here and would be guesswork to assert.
Predictions can't be grounded in this data. The most useful next step is to refresh Fellow's changelog source so that present-day moves are captured.
0.25.6 is a bug-fix release the maintainer recommends to every user on an earlier tag, and its weight sits in NanoNNG rather than the broker: unsuccessful CONNACK negotiation is now rejected, Session Expiry Interval is accepted in CONNACK, pipes closed during the unlocked auth window are no longer registered, receive pipes unlink on session handoff, and a strict property checker guards against malformed input. Two potential security issues are patched, SCRAM handling hardened, and a workaround added for an NNG TLS idle bug. Four of the contributors are making their first commit to the project.
The hardening campaign that began with fuzzing on the 0.24 line has moved up into MQTT protocol conformance — this release is dense with spec-edge handling and lifecycle races rather than crashes. The more interesting shift is social: after 0.25.5 traded architecture breadth for correctness depth, the protocol layer is now attracting outside contributors, with four newcomers landing fixes in NanoNNG in a single release. That is a different growth mode than the maintainer-driven cadence of the 0.24 line.
The 0.25 line looks set to continue on protocol conformance and session lifecycle correctness rather than new features. The SipHash client ID hashing question the maintainer raised in 0.25.2 is still open in these entries, with no resolution either way.
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 Fellow or NanoMQ.
The RocksDB migration reaches native code as the legacy DLedger broker mode is marked for removal
Cliq 7.0 stops being a destination app and becomes a layer across Zoho
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
Element Web is opening an extension surface while rebuilding its timeline underneath.
Signal's beta train keeps trickling small comfort settings between maintenance drops
respond.io is widening what a conversation can hold - more channels, and now more than one owner.
See all Fellow alternatives → · See all NanoMQ alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NanoMQ is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. NanoMQ is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Fellow alternatives in Comms are ranked by recent ship velocity. Browse the "Fellow alternatives" section above for the current picks, or visit /alternatives/fellow for the full list with editorial commentary on each.
Top NanoMQ alternatives in Comms are ranked by recent ship velocity. Browse the "NanoMQ alternatives" section above for the current picks, or visit /alternatives/nanomq for the full list with editorial commentary on each.