← Back to home
Comparison · Comms

Botpress vs Slack

A side-by-side editorial comparison of Botpress and Slack — release velocity, themes, recent moves, and the top alternatives to consider.

Botpress vs Slack: at a glance

FeatureBotpressSlack
SectorCommsComms, Collab
Velocity score0.06.3
Sparks · 30d01
Top themesagent authoring, knowledge bases, integrations, studioagents, mcp, developer-platform, marketplace
Last editorial update1mo ago14d ago
WebsiteVisit →

What is Botpress?

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.

Read the full Botpress trajectory →

What is Slack?

Slack raises the Marketplace bar back to ten installs while the agent platform consolidates.

Slack's developer platform runs two tracks. The agent build-out has produced a spark roughly every two weeks since June — MCP client, a skills plugin targeting Claude Code and Cursor, and Slack Code — and now has a consolidation date attached: assistant_view is deprecated in February 2027, replaced by an Agent Sessions API. The second track is platform administration and tooling, and this window belongs to it: Marketplace submissions again require at least ten installed active workspaces, held throughout the review, after a period at a lower temporary threshold. The CLI has shipped three times since late July.

Read the full Slack trajectory →

Botpress vs Slack: editorial side-by-side

B0.0

Botpress spent its last visible releases on the agent authoring seat — then went quiet in April.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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 logo
Slack
COMMSCOLLAB
6.3

Slack raises the Marketplace bar back to ten installs while the agent platform consolidates.

◆ Current state

Slack's developer platform runs two tracks. The agent build-out has produced a spark roughly every two weeks since June — MCP client, a skills plugin targeting Claude Code and Cursor, and Slack Code — and now has a consolidation date attached: assistant_view is deprecated in February 2027, replaced by an Agent Sessions API. The second track is platform administration and tooling, and this window belongs to it: Marketplace submissions again require at least ten installed active workspaces, held throughout the review, after a period at a lower temporary threshold. The CLI has shipped three times since late July.

◆ Where it's heading

The install requirement moving back up is a distribution decision arriving in the middle of a platform push, and the two point the same way. Slack is making it easier to build agents and harder to list one, which favours developers who already have distribution — existing workspace tools and vendors — over a new app hoping the Marketplace supplies its first users. Combined with the assistant deprecation and the Agent Sessions API, the platform is narrowing on one agent surface and one class of builder rather than widening the funnel.

◆ Prediction

The threshold is described as a return from a temporary lower bar rather than a new policy, so the open question is what replaces the Marketplace as the discovery path for an app that cannot reach ten workspaces on its own. These entries do not answer it.

Alternatives to Botpress and Slack

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.

See all Botpress alternatives → · See all Slack alternatives →

Recent activity from Botpress and Slack

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 15d agoSlackUpdated installation requirement for Slack Marketplace apps
  2. 16d agoSlackCLI adds app-approval status checks and custom app icons
  3. 27d agoSlackAnnouncing Slack Code
  4. 27d agoSlackAgent Sessions API replaces assistant_view, deprecated Feb 2027
  5. 1mo agoSlackAnnouncing the Slack MCP and Skills Plugin
  6. 1mo agoSlackCLI adds manifest diff and a Block Kit preview command
  7. 5mo agoBotpress​ Revamped Autonomous Node
  8. 5mo agoBotpress​Revamped Autonomous Node
  9. 5mo agoBotpress​ Redesigned integrations Hub
  10. 5mo agoBotpress​Redesigned integrations Hub
  11. 5mo agoBotpress​ Studio
  12. 5mo agoBotpress​Studio

Frequently asked questions

What is the difference between Botpress and Slack?

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.

Is Botpress better than Slack?

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.

What are the best alternatives to Botpress?

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.

What are the best alternatives to Slack?

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.