Chanty
Chanty's feed is an HR statistics content mill, not a product changelog
A side-by-side editorial comparison of Stalwart and Textellent — release velocity, themes, recent moves, and the top alternatives to consider.
Stalwart is chasing mail RFCs and its own storage layer at the same time
Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.
Textellent leans into franchise SMS compliance with always-on 10DLC monitoring.
One genuine product announcement anchors the feed: always-on compliance monitoring and franchise-wide 10DLC handling, plus a brand-wide Do Not Text control aimed at multi-location systems. The rest of the crawled entries are SEO articles — SMS tax rules, text abbreviations, delivery-status explainers, and a Twilio-alternatives roundup — carrying no product change.
Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.
Two threads run through every release. One is RFC coverage across IMAP, JMAP, CalDAV and WebDAV, implemented close to the specification including drafts. The other is a long tail of protocol-conformance fixes, many of them cases where JMAP and IMAP disagreed about the same state. The newest release adds a third: memory and scheduling limits, which is what a server codebase starts doing when deployments get large enough for defaults to hurt.
Expect continued RFC additions across the JMAP and IMAP surfaces, with more of the storage-tuning work that v0.16.18 started as RocksDB deployments scale.
One genuine product announcement anchors the feed: always-on compliance monitoring and franchise-wide 10DLC handling, plus a brand-wide Do Not Text control aimed at multi-location systems. The rest of the crawled entries are SEO articles — SMS tax rules, text abbreviations, delivery-status explainers, and a Twilio-alternatives roundup — carrying no product change.
Textellent is positioning around the operational pain that carrier 10DLC rules create for franchises: registration bottlenecks and ongoing compliance risk across many locations. Continuous monitoring and network-wide controls suggest a move from point SMS tooling toward compliance infrastructure for multi-location brands.
Expect further franchise-oriented compliance features — centralized registration, network-wide opt-out and reporting — deepening the multi-location wedge.
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 Stalwart or Textellent.
Chanty's feed is an HR statistics content mill, not a product changelog
Proton Bridge spends its first release in ten weeks on crashes, memory bounds and dead code
Every manual control Mux ships now arrives with a Robots workflow that does it for you
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
mailcow's release notes are almost entirely upstream security currency.
Openfire keeps its XMPP server current without changing what it is.
See all Stalwart alternatives → · See all Textellent alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Textellent is currently shipping more aggressively (velocity 6.3 vs 5.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. Textellent is currently shipping more aggressively (velocity 6.3 vs 5.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 Stalwart alternatives in Comms are ranked by recent ship velocity. Browse the "Stalwart alternatives" section above for the current picks, or visit /alternatives/stalwart for the full list with editorial commentary on each.
Top Textellent alternatives in Comms are ranked by recent ship velocity. Browse the "Textellent alternatives" section above for the current picks, or visit /alternatives/textellent for the full list with editorial commentary on each.