Tools tagged "chat" provide real-time messaging: team chat, customer support widgets, in-app messaging between users, or chatbot interfaces. Open source chat tools range from full team communication platforms (channels, direct messages, threads) to embeddable customer-facing chat widgets and headless chat APIs for building messaging into a product.
Common use cases include internal team communication as a Slack alternative, customer support live chat embedded on a website, in-app messaging for marketplaces or social products (buyer-seller chat, community chat), and chatbot or AI assistant interfaces where a chat UI wraps an LLM backend. Some tools are complete standalone applications, while others are UI components and backend infrastructure (message storage, presence, typing indicators) meant to be embedded into an existing product.
When choosing one, check the real-time delivery mechanism (WebSockets vs. polling) and how it scales with concurrent users, message persistence and search across chat history, support for rich content (file attachments, reactions, threads, markdown), whether it offers a full pre-built UI or just backend APIs and SDKs for a custom frontend, and moderation tools if the chat is customer-facing or public (rate limiting, banned words, reporting). For team chat specifically, integration with existing tools (calendar, file storage, video calls) matters for adoption.
Self-hosted chat tools typically replace Slack, Intercom's chat widget, and Twilio Conversations. Teams self-host team chat to avoid per-user monthly fees and to keep internal communication off a third party's servers, and embed self-hosted chat infrastructure into products to avoid per-message or per-active-user pricing from chat APIs while keeping full control over the UI and data. The tradeoff is handling real-time infrastructure scaling (WebSocket connections at volume) yourself instead of relying on a managed provider.