Netcore Cloud
Netcore's blog is selling six production AI agents; the feed never shows them shipping.
A side-by-side editorial comparison of Maddy and Zoho Mail — release velocity, themes, recent moves, and the top alternatives to consider.
A one-binary mail server learning to behave like production infrastructure.
maddy is an all-in-one SMTP and IMAP server written in Go, aimed at people who want a working mail host without assembling Postfix, Dovecot and a policy daemon themselves. The 0.9 line moved quickly — 0.9.0 through 0.9.5 between late March and late May — with the sequence following a recognisable shape: a feature release, an immediate patch for a broken integration, a security release, then cleanup. Configuration is directive-based, and much of the changelog concerns the behaviour of individual modules like auth.ldap, check.rspamd and check.dnsbl.
Zoho Mail is annexing the workday around the inbox: web tabs, tasks, and an MCP endpoint.
Zoho Mail's feed is mostly explainer and positioning content, but the product moves inside it all point one direction: the inbox as a container for the rest of the workday. Web Tabs pins third-party sites beside the mailbox, Zoho ToDo carries tasks, and an MCP endpoint opens the mailbox to agents. The enterprise layer around it — admin console, journaling, admin reports — is being documented and rounded out rather than rebuilt.
maddy is an all-in-one SMTP and IMAP server written in Go, aimed at people who want a working mail host without assembling Postfix, Dovecot and a policy daemon themselves. The 0.9 line moved quickly — 0.9.0 through 0.9.5 between late March and late May — with the sequence following a recognisable shape: a feature release, an immediate patch for a broken integration, a security release, then cleanup. Configuration is directive-based, and much of the changelog concerns the behaviour of individual modules like auth.ldap, check.rspamd and check.dnsbl.
The project is systematically removing the compromises that made early versions convenient. Obsolete SASL LOGIN was disabled by default, the STARTTLS plaintext fallback was dropped, the maddyctl symlink behaviour and the implicit run command were deleted after four years of deprecation warnings, and libdns providers that have not kept up with 1.x are being cut. Running the other way is operational maturity: no-downtime config reload, queue-length metrics, OpenMetrics fixes, systemd readiness reporting, and SLSA build attestations on release artifacts. This is a project moving from hobbyist-friendly to operator-friendly, and accepting breakage to get there.
0.10.0 is already scoped by the deprecations announced in 0.9.1 — expect the flagged libdns providers to be removed and gandi to require Bearer tokens. Given the 0.9.x pattern, a feature release followed quickly by an integration fix is the likely shape.
Zoho Mail's feed is mostly explainer and positioning content, but the product moves inside it all point one direction: the inbox as a container for the rest of the workday. Web Tabs pins third-party sites beside the mailbox, Zoho ToDo carries tasks, and an MCP endpoint opens the mailbox to agents. The enterprise layer around it — admin console, journaling, admin reports — is being documented and rounded out rather than rebuilt.
The arc is consolidation rather than depth: instead of making email itself better, Zoho is absorbing the surfaces users leave the mailbox for. Two access paths are advancing in parallel — a human one through Web Tabs and ToDo, and a programmatic one through MCP and Client Scripting. The compliance and admin material signals who this is aimed at, and Microsoft's EWS retirement is being worked as a migration opening for displaced Exchange Online tenants.
Expect both paths to extend — more embeddable surfaces inside the mail UI, and more of the mailbox reachable through MCP and Client Scripting. The entries show no pricing or packaging changes, so which of these land in the paid enterprise tiers is unclear from this window.
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 Maddy or Zoho Mail.
Netcore's blog is selling six production AI agents; the feed never shows them shipping.
Rocket.Chat bundled semantic AI search, FIPS mode and air-gapped licensing into one regulated-buyer release.
Chatwoot added voice, then turned its AI agent loose on the conversations it already resolved.
Converse.js 14 lands OMEMO:2 — the browser XMPP client catches up on modern encryption.
Stalwart keeps chasing standards nobody has implemented yet — DKIM2, DMARCbis, now JMAP email push.
Friendica keeps betting on being the fediverse node that speaks everyone else's protocols.
See all Maddy alternatives → · See all Zoho Mail alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Zoho Mail 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. Zoho Mail 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 Maddy alternatives in Comms are ranked by recent ship velocity. Browse the "Maddy alternatives" section above for the current picks, or visit /alternatives/maddy for the full list with editorial commentary on each.
Top Zoho Mail alternatives in Comms are ranked by recent ship velocity. Browse the "Zoho Mail alternatives" section above for the current picks, or visit /alternatives/zoho-mail for the full list with editorial commentary on each.