Help Scout
Help Scout keeps adding channels — now a portal customers sign into
Comparison · Comms
Fellow vs NanoMQ
A side-by-side editorial comparison of Fellow and NanoMQ — release velocity, themes, recent moves, and the top alternatives to consider.
Fellow vs NanoMQ: at a glance
What is Fellow?
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.
What is NanoMQ?
An edge MQTT broker hardening for vehicles — and dropping the old embedded arches to do it.
NanoMQ closed out the 0.24 line and moved to 0.25 over roughly five months, shipping through a string of pre-releases before 0.25.3 became the first official 0.25 build. The work splits between memory-safety hardening — fuzzing via OSS-Fuzz and ClusterFuzz is now routine after the maintainer noted production use in robotics and vehicles — and protocol-layer restructuring, with QoS acknowledgement handling moved out of the transport layer and configuration reloading rebuilt lock-free. Release notes are candid to a fault: the maintainer publishes AI-drafted changelogs with attribution and openly says he hasn't made up his mind about the SipHash change.
Fellow vs NanoMQ: editorial side-by-side
Fellow
0.0COMMS
Fellow's public changelog has been silent since 2021 — no recent direction is observable here.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
NanoMQ
6.3COMMS
An edge MQTT broker hardening for vehicles — and dropping the old embedded arches to do it.
◆ Current state
NanoMQ closed out the 0.24 line and moved to 0.25 over roughly five months, shipping through a string of pre-releases before 0.25.3 became the first official 0.25 build. The work splits between memory-safety hardening — fuzzing via OSS-Fuzz and ClusterFuzz is now routine after the maintainer noted production use in robotics and vehicles — and protocol-layer restructuring, with QoS acknowledgement handling moved out of the transport layer and configuration reloading rebuilt lock-free. Release notes are candid to a fault: the maintainer publishes AI-drafted changelogs with attribution and openly says he hasn't made up his mind about the SipHash change.
◆ Where it's heading
The project is trading breadth of hardware support for depth of correctness. 0.25.5 drops official MIPS and ARMel binaries because the build toolchain and MsQuic dependency moved on, while the same release adds hazard-pointer reclamation for hot config reload — a broker chasing safety-critical deployments rather than the widest possible router install base. Bridging is the other consistent thread: nng_bridge, then a nolocal parameter for bridge clients, then the earlier anti-loop work.
◆ Prediction
Expect the 0.25 line to keep tightening QoS and session persistence, and a decision on whether SipHash client ID hashing stays given its CPU cost. Whether dropped architectures return through community builds is not addressed in these entries.
Alternatives to Fellow and NanoMQ
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.
Synapse
Synapse alternates release candidates with security patches on a tight two-week cycle
Canary Mail
Canary Mail ships maintenance across four platform lines; features have gone quiet since April.
Bandwidth
Bandwidth is closing the gaps that used to require a support ticket
Beeper
Beeper stopped aggregating apps and started merging the people inside them.
Stalwart
Stalwart is shipping email's next-generation auth stack while the specs are still in draft.
See all Fellow alternatives → · See all NanoMQ alternatives →
Recent activity from Fellow and NanoMQ
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 9d agoNanoMQMIPS and ARMel binaries dropped; lock-free config reload lands ⚡
- 29d agoNanoMQFirst official 0.25 build fixes a last-will memory leak
- 1mo agoNanoMQTemporary build tagged between 0.25.2 and 0.25.3
- 1mo agoNanoMQClient ID hashing moves from DJBHash to SipHash
- 1mo agoNanoMQTrial pre-release opens the 0.25 line
- 2mo agoNanoMQnng_bridge links Nanomsg and MQTT without a proxy process ⚡
- 5y agoFellowAction items in Google Calendar extension 📆
- 5y agoFellowPublic links 🔗
- 5y agoFellowSync multiple calendars 📅
Frequently asked questions
What is the difference between Fellow and NanoMQ?
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.
Is Fellow better than NanoMQ?
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.
What are the best alternatives to Fellow?
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.
What are the best alternatives to NanoMQ?
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.