← Back to home
Comparison · Comms

Element vs Slack

Side-by-side trajectory, velocity, and editorial themes.

E
Element
COMMS
0.8

Element is going all-in on Europe's sovereign-comms thesis, with both customers and rhetoric to back it.

◆ Current state

Element has narrowed its public posture almost entirely to one buyer: European governments and regulated organisations that want a Matrix-based, self-hostable alternative to US consumer messengers. The last two months blend concrete shipping work — Spaces on Element X, an ESS Community migration tool, MatrixRTC progress — with a steady drumbeat of policy commentary on CRA, the Digital Omnibus, and Signal/WhatsApp targeting incidents. The Meedio deal anchors the strategy with a real customer building a sovereign comms platform on ESS Pro.

◆ Where it's heading

Product work and policy work are now reinforcing each other rather than running in parallel: every shipped feature is framed as evidence that decentralised, federated comms can meet government-grade requirements. The migration tooling and Spaces in Element X point at a concerted push to make ESS deployable enough that procurement teams will sign. Expect Element's editorial output to keep using competitor security incidents to harden the case for Matrix in regulated markets.

◆ Prediction

Look for another EU-government deployment announcement within a quarter, alongside continued Element X feature work aimed at making the client feel competitive with WhatsApp for everyday users — Spaces was the precondition, threads and call quality are the obvious next slabs.

Slack logo
Slack
COMMSCOLLAB
5.0

Slack rebuilds its developer platform around shipping in-channel AI agents.

◆ Current state

Slack is well into a platform pivot, restructuring its CLI, Block Kit, and APIs around AI agent use cases. The 4.0.0 release in April formalized this with an agent-scaffolding command, sample agent apps, and a live-reloading dev workflow. Recent additions — streaming chat APIs, Card/Carousel/Alert blocks, and continued MCP server expansion — show the surface area for in-Slack agents widening fast.

◆ Where it's heading

The platform is shifting from 'agents can post messages' to 'agents are first-class UI citizens'. The new chat.startStream / chat.appendStream / chat.stopStream methods change what an agent reply looks like, and the Card and Carousel blocks hint at richer multi-turn agent flows. Security work on PKCE and optional scopes is keeping pace, which tells you third-party agent developers are the audience, not just first-party features.

◆ Prediction

Expect Slack to publish reference agents and likely a discovery or marketplace surface for agent apps within the next minor cycle, with streaming Block Kit becoming the canonical pattern shown in the docs.

See more alternatives to Element
See more alternatives to Slack