Stalwart vs Slack
Side-by-side trajectory, velocity, and editorial themes.
Stalwart races to implement the newest email standards across its all-in-one server
Stalwart is an open-source, all-in-one mail and collaboration server (SMTP/IMAP/JMAP/CalDAV) shipping a fast 0.16.x point-release train. Recent releases are dominated by standards implementation and protocol-conformance work, layered over steady security hardening and a long tail of targeted bug fixes.
The product is doubling down on being the most standards-complete self-hosted mail server: early DKIM2 and DMARCbis authentication, IDN support, encryption-at-rest for S/MIME, and a sustained push to pass the JMAP test suite. Security hardening runs alongside — DANE downgrade-attack defenses, auto-ban fixes, binary attestation on every build.
Expect continued rapid 0.16.x releases advancing draft email-authentication standards and JMAP conformance; a larger 0.17 or 1.0 milestone becomes likely once the JMAP suite fully passes and the DKIM2/DMARCbis drafts stabilize.
Slack is quietly rebuilding itself as a runtime for third-party agents.
Slack's developer platform has shifted its center of gravity from bots-that-reply to agents-that-act. The last month is dominated by agent primitives: apps can now receive the context a user is looking at, Slackbot can call external tools over MCP, and a dedicated agent messaging surface ships alongside steady CLI and Block Kit work.
Each release fills in a piece of an agent platform — context in, tools out, and a native place for agents to converse. Block Kit is gaining richer primitives (containers, data visualization) that read as the display layer for agent output. Three CLI releases in a month show the tooling keeping pace with the expanding surface.
Expect the next moves to connect these pieces: agent context feeding MCP tool calls, and Block Kit's new blocks becoming the standard way agents render results in-channel.
See more alternatives to Stalwart →
See more alternatives to Slack →