Rspamd
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
A side-by-side editorial comparison of Botpress and Slack — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Botpress | Slack |
|---|---|---|
| Sector | Comms | Comms, Collab |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | agent authoring, knowledge bases, integrations, studio | agents, a2a, mcp, slackbot-skills |
| Last editorial update | 3mo ago | 3d ago |
| Website | — | Visit → |
Botpress spent its last visible releases on the agent authoring seat — then went quiet in April.
Three releases account for all six entries; every one appears twice, once from the marketing changelog and once from the docs mirror. The Autonomous Node got a real prompt editor with a macro menu for referencing knowledge bases and variables plus a raw Markdown mode; Studio multiplayer was rebuilt for latency; the integrations Hub was redesigned; Knowledge Bases gained Linear, GitHub, Confluence, Google Drive and Notion as sources; and Studio picked up model selection for the Vision Agent and a --url flag on CLI deploys. The newest entry is from mid-April.
Slack now hosts any A2A agent without Slack-specific code.
Slack's developer channel is almost all agent plumbing. On 10 November Slack became an A2A (Agent2Agent) client: a team hosts its own agent, publishes an Agent Card, and Slack calls it when people talk to it, with no request URL, event handling or Slack-specific logic. This follows Slackbot skills managed through Web API methods, a Slack CLI that points coding agents to the Slack MCP server, and a new requirement that Work Objects embeds allow the slack-mcps.com frame ancestor.
Three releases account for all six entries; every one appears twice, once from the marketing changelog and once from the docs mirror. The Autonomous Node got a real prompt editor with a macro menu for referencing knowledge bases and variables plus a raw Markdown mode; Studio multiplayer was rebuilt for latency; the integrations Hub was redesigned; Knowledge Bases gained Linear, GitHub, Confluence, Google Drive and Notion as sources; and Studio picked up model selection for the Vision Agent and a --url flag on CLI deploys. The newest entry is from mid-April.
The work concentrates on two things: making the agent's prompt directly editable and inspectable rather than buried in UI, and widening the set of systems an agent can be grounded in. Both are builder-facing rather than end-user-facing, which fits a platform competing on how fast a team can get an agent into production. What comes after April is not visible in this feed.
On the visible pattern the next moves are more knowledge-source connectors and further Studio editor work; the three-month gap since the last entry makes anything beyond that unsupported.
Slack's developer channel is almost all agent plumbing. On 10 November Slack became an A2A (Agent2Agent) client: a team hosts its own agent, publishes an Agent Card, and Slack calls it when people talk to it, with no request URL, event handling or Slack-specific logic. This follows Slackbot skills managed through Web API methods, a Slack CLI that points coding agents to the Slack MCP server, and a new requirement that Work Objects embeds allow the slack-mcps.com frame ancestor.
Slack is lowering the cost of putting outside agents in front of its users: first skills as code, then MCP pointers for coding agents, now a standard protocol in place of the Slack app model for agents. The platform is positioning itself as the place where agents built anywhere meet the people who use them.
Expect more A2A follow-ups, such as agents appearing in Slackbot or skills surfaces and richer Agent Card features, given how fast the agent releases have stacked up since October.
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 Botpress or Slack.
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
Twilio's voice AI stops cutting callers off mid-sentence, using its own turn-taking model.
Salesmsg adds call-back requests and a one-click Emergency Stop for all outbound texts.
Element 1.12.35 follows the call picture-in-picture release with one desktop storage fix.
Krisp moves call transcripts and live captions to cloud transcription in KrispCX 2.84.4.
Misskey 2026.11 ships: a leaner start script, and Node.js 22 no longer boots.
See all Botpress alternatives → · See all Slack alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Slack 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. Slack 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 Botpress alternatives in Comms are ranked by recent ship velocity. Browse the "Botpress alternatives" section above for the current picks, or visit /alternatives/botpress for the full list with editorial commentary on each.
Top Slack alternatives in Comms are ranked by recent ship velocity. Browse the "Slack alternatives" section above for the current picks, or visit /alternatives/slack for the full list with editorial commentary on each.