Tinode vs Slack
Side-by-side trajectory, velocity, and editorial themes.
Self-hosted chat platform shipping steady catch-up features and ops cleanup.
Tinode is an open-source, self-hosted messaging server with maintained Web, Android (Tindroid), and iOS (Tinodios) clients. The release cadence is regular (multiple tags per month), and the recent body of work is split between small bug fixes, infrastructure tuning (CORS, MySQL/Postgres DSN handling, Docker image fixes, healthchecks), and feature catch-up that brings the UX nearer to commercial chat apps — pinned chats, dark mode, subscriber counts, send-on-Enter, in-call messaging. An alpha for message reactions is in flight.
The project is in steady-state maintenance with one visible directional push: catching up on the UX features that mainstream chat apps have had for years. Reactions are the next concrete step. Bug fixes and ops touchups dominate the in-between releases, which is healthy for an open-source server that runs in self-hosted production deployments.
v0.26.0 will ship reactions as the headline feature. Threads, richer notifications, or moderation tooling are the natural next catch-ups — anything that further closes the gap with Slack/Matrix/Element on the UX surface without expanding the protocol surface too aggressively.
Slack rebuilds its developer platform around shipping in-channel AI agents.
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.
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.
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 Tinode →
See more alternatives to Slack →