Help Scout
Help Scout keeps adding channels — now a portal customers sign into
Comparison · Comms
NanoMQ vs Superhuman
A side-by-side editorial comparison of NanoMQ and Superhuman — release velocity, themes, recent moves, and the top alternatives to consider.
NanoMQ vs Superhuman: at a glance
| Feature | NanoMQ | Superhuman |
|---|---|---|
| Sector | Comms | Comms |
| Velocity score | 6.3 | 7.5 |
| Sparks · 30d | 1 | 2 |
| Top themes | mqtt, iot, edge-broker, bridging | mcp, auto-drafts, agent-native, multi-account |
| Last editorial update | 2d ago | 13d ago |
| Website | Visit → | — |
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.
What is Superhuman?
Superhuman is rebuilding around the assistant: pre-drafted replies and multi-account MCP.
Superhuman ships small and often, and its releases now split cleanly in two. One half is conventional client work — calendar on Android, multi-day views on iPhone and iPad, personalized availability sharing. The other is an aggressive agent surface: Auto Drafts 2.0 pre-drafts a reply to every message that needs one, and the Mail MCP now drives multiple Gmail and Outlook accounts from Claude, ChatGPT and Codex.
NanoMQ vs Superhuman: editorial side-by-side
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.
Superhuman
7.5COMMS
Superhuman is rebuilding around the assistant: pre-drafted replies and multi-account MCP.
◆ Current state
Superhuman ships small and often, and its releases now split cleanly in two. One half is conventional client work — calendar on Android, multi-day views on iPhone and iPad, personalized availability sharing. The other is an aggressive agent surface: Auto Drafts 2.0 pre-drafts a reply to every message that needs one, and the Mail MCP now drives multiple Gmail and Outlook accounts from Claude, ChatGPT and Codex.
◆ Where it's heading
The centre of gravity is moving off Superhuman's own client. Each recent release makes the mailbox more usable from somewhere else — first a Codex plugin with prebuilt workflows, then parallel search across every connected account — while in-app work is mostly mobile parity. Superhuman is positioning as the mail layer assistants call, and it names the single-account limit of the first-party Gmail and Outlook connectors as the reason to switch.
◆ Prediction
Expect the MCP surface to keep absorbing the features that only the client could do — Split Inbox triage, Read Statuses, Smart Send are already listed — with the native apps continuing to trail on platform parity.
Alternatives to NanoMQ and Superhuman
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 NanoMQ or Superhuman.
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 NanoMQ alternatives → · See all Superhuman alternatives →
Recent activity from NanoMQ and Superhuman
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8d agoNanoMQMIPS and ARMel binaries dropped; lock-free config reload lands ⚡
- 13d agoSuperhumanMultiple email accounts in Claude, ChatGPT, and MCP 🤖 ⚡
- 29d agoSuperhumanAuto Drafts 2.0 ✨ ⚡
- 29d agoNanoMQFirst official 0.25 build fixes a last-will memory leak
- 1mo agoSuperhumanMulti-day views on iPhone & iPad 📆
- 1mo agoSuperhumanCalendar on Android 💚
- 1mo agoNanoMQTemporary build tagged between 0.25.2 and 0.25.3
- 1mo agoNanoMQClient ID hashing moves from DJBHash to SipHash
- 1mo agoSuperhumanSuperhuman Mail Codex plugin 🤖
- 1mo agoNanoMQTrial pre-release opens the 0.25 line
- 2mo agoSuperhumanPersonalize share availability ✨
- 2mo agoNanoMQnng_bridge links Nanomsg and MQTT without a proxy process ⚡
Frequently asked questions
What is the difference between NanoMQ and Superhuman?
They serve adjacent needs but don't currently overlap on shipped themes. Superhuman is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is NanoMQ better than Superhuman?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Superhuman is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
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.
What are the best alternatives to Superhuman?
Top Superhuman alternatives in Comms are ranked by recent ship velocity. Browse the "Superhuman alternatives" section above for the current picks, or visit /alternatives/superhuman for the full list with editorial commentary on each.