Getting a language model into the chat apps people already use takes a single self-hosted server running AstrBot, which answers in QQ, Telegram, Discord, Slack, Lark, DingTalk, LINE, and WeCom. The model itself is a setting. OpenAI-compatible endpoints, Anthropic, Google Gemini, DeepSeek, Ollama, and LM Studio all work, with fallback models and retry limits for failed requests, and Dify, Coze, or Alibaba Cloud Bailian can take over a conversation too. A bare model cannot act, so the built-in agent calls MCP servers and Skills, delegates to SubAgents, runs scheduled tasks, and executes code in an isolated sandbox. It cannot read your files either, so a knowledge base takes PDF, Word, Markdown, and EPUB uploads and searches them with hybrid dense and BM25 retrieval. Personas shape each bot's personality, and Whisper or Edge TTS adds speech. When an answer looks wrong, the ChatUI shows thinking, tool calls, token counts, and latency, and a per-message trace timeline shows how the bot got there. Because the panel steers the bot, administrator IDs, session whitelists, optional TOTP login, and HTTPS protect it. Backups live under System Settings, and the plugin market installs any of more than 1,000 extensions in one click. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

A fair-source chatbot and conversational-form builder: Typebot assembles conversations in a visual graph editor. In a visual graph editor you chain blocks from four categories: bubbles display text, images, video, audio, and embeds; inputs collect data through text fields, email, phone, buttons, picture choices, date pickers, file uploads, and Stripe payments; logic blocks handle conditional branching, variables, URL redirects, A/B testing, and custom JavaScript; integration blocks call webhooks, OpenAI, Google Sheets, Google Analytics, Meta Pixel, Zapier, Make, and Chatwoot. Build once, deploy anywhere: custom domains, WhatsApp, or embedded in any site as a container, popup, or chat bubble through a fast native JS library with no iframe and no external dependencies - plus an HTTP API for executing bots programmatically from any language. Theming covers fonts, colors, roundness, and shadows with custom CSS and reusable templates, and results arrive in real time with drop-off and completion analytics plus CSV export. Two Next.js apps (builder and viewer) self-host via Docker under the Functional Source License, which converts to Apache 2.0 after two years.

Build, deploy, and monitor chatbots and LLM-powered agents on one open-source conversational AI platform: Botpress. Its Studio is a visual development environment: a drag-and-drop canvas arranges conversation logic with nodes for messages, questions, choices, and actions, while a built-in emulator simulates conversations for debugging before anything goes live. Agents ground their answers in a knowledge base assembled from uploaded documents, ingested websites, and past conversations via retrieval-augmented generation, and the LLM layer connects to multiple model providers - GPT-4, Claude, Mistral - with a configurable model strategy. An autonomous engine handles reasoning, tool orchestration, persistent memory across sessions, and sandboxed code execution, and custom code actions in TypeScript extend agents past prebuilt workflows. Over 100 integrations deploy the same bot to WhatsApp, Telegram, Slack, Microsoft Teams, and web chat, and connect it to HubSpot, Zendesk, Zapier, and arbitrary APIs and webhooks. Human handoff, conversation analytics, and quality monitoring cover production operation. Originating in 2017 from a Montreal team, the community edition is developed openly on GitHub.

Retrieval-augmented chatbots on your own knowledge base - that is the whole mission of Dialoqbase, an open-source bot-building platform. Feed it content through a broad set of data loaders - web pages and full crawls, sitemaps, PDFs, DOCX, CSV, plain text, GitHub repositories, YouTube videos, and MP3/MP4 audio - and it handles the whole RAG pipeline in one self-contained app: chunking, embedding, vector storage, and LLM querying. The distinguishing architecture choice is PostgreSQL with pgvector for embedding storage and similarity search, which removes the separate vector-database dependency, and Redis-backed Bull queues for ingesting large documents without blocking the API. Model choice is wide open: OpenAI, Anthropic Claude, Google Gemini, Cohere, Fireworks, Hugging Face, local models via Ollama, and any OpenAI-compatible endpoint, with an equally broad list of embedding providers. Finished bots embed on any website with customizable styling or deploy to Telegram, Discord, and WhatsApp, and an API creates and manages bots programmatically. Multi-user support adds registration limits and per-user bot quotas. MIT-licensed and free for commercial use.

Tiledesk lets you build AI-powered conversational agents with a visual drag-and-drop designer, then deploy them simultaneously across web chat, WhatsApp, Telegram, Facebook Messenger, Instagram, email, and Slack without rebuilding per channel. The no-code Design Studio combines LLM-powered conversations with conditional logic, external API calls, and branching dialogue trees that work identically everywhere. Multi-RAG knowledge management separates content into isolated repositories with hybrid search combining traditional full-text retrieval and semantic understanding via Qdrant vector embeddings, enabling accurate answers even when users phrase queries in unexpected ways. LLM integration supports GPT-4, GPT-4o, Anthropic Claude, and any model exposing an OpenAI-compatible API including locally hosted models via Ollama for complete data sovereignty. The human-in-the-loop system provides seamless escalation from AI agents to live support staff with full conversation context preserved, while multi-agent workflows enable complex orchestration where specialized bots collaborate on different aspects of a customer interaction. REST and MQTT APIs power integration with external systems and webhook-triggered automations, and pre-designed templates accelerate common scenarios. Docker Compose deployment starts the full stack including server, dashboard, messaging engine, and widget. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Unleash the power of Chatwoot, the open-source superhero in the world of customer experience! This platform is perfect for businesses craving to connect with their customers across a multitude of channels without breaking the bank. Wave goodbye to the high-and-mighty likes of Intercom, Zendesk, and Salesforce Service Cloud, and say hello to a wallet-friendly powerhouse. Chatwoot turns your agents into customer service ninjas, armed with the latest in workload management, performance tracking reports that refresh themselves (because who has time for that?), and automations that work smarter, not harder. Zap through conversations with lightning-fast responses and manage your social media and email interactions in a single bound. Plus, with Chatwoot, you get to be the Sherlock of customer satisfaction, deducing your CSAT scores on autopilot. All this hosted on RepoCloud, where the cost is as tiny as the effort you'll need to switch over. Get ready to engage, enlighten, and entertain your customers with Chatwoot!

Add a live support desk to any website with Live Helper Chat, where visitors talk to operators or bots and you own every transcript. Site owners paste a generated embed snippet into any page, and the start-chat fields are customizable. Chats are routed by department, language, location, or custom attributes, wait in a priority queue, and move between agents. Operators, departments, and simultaneous chats are unlimited. Agents watch a visitor type before the message is sent, read pages visited and time on site in the online visitors list, and send proactive invitations to people who linger. Voice, video, and screen sharing run through Jitsi or Agora, and a screenshot shows what the visitor sees. Bot designers chain triggers and actions in a visual builder, call ChatGPT, Gemini, Ollama, Rasa, or any REST API, and hand the conversation to a person when needed. Incoming email becomes tickets beside chats, and extensions connect Telegram, WhatsApp, Facebook Messenger, and Twilio SMS. Staff answer from the browser, a desktop app, a Chrome extension, or iOS and Android apps. Management tools include roles, groups, statistics, transcripts, and an archive, and extensions add two-factor login, LDAP, and single sign-on. It suits banks, healthcare teams, universities, and game studios that must keep chat data in house. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache-2.0 licensed.

Companies with privacy and security concerns about piping customer conversations through Intercom or Zendesk run Papercups - open-source live customer chat. The stack is a deliberate strength: an Elixir/Phoenix API over PostgreSQL, with real-time messaging powered by Phoenix Channels and Presence - the same BEAM foundation trusted by Discord and PagerDuty for fault-tolerant, low-latency messaging. Customers see a customizable chat widget that embeds in any site as an HTML snippet, a React component, or even inside React Native apps, with configurable colors, greetings, and away messages. Your team sees a dashboard for managing conversations - close, assign, and prioritize - with Markdown and emoji in replies. The killer workflow is the reply-channel integration: connect Slack or Mattermost and every customer conversation becomes a synced thread your team answers without leaving the tool they already live in, with two-way message syncing handled by webhooks. Email and SMS channels extend intake beyond the widget, an analytics dashboard tracks communication patterns, and the Storytime feature adds real-time screen sharing to watch users navigate while you help them. A documented API supports fully custom chat UIs in Svelte, Flutter, or Vue. MIT-licensed and GDPR-conscious - customer data stays in your PostgreSQL.

Comment sections at the Washington Post, the Wall Street Journal, and newsrooms across 30 countries run on Coral (also known as Talk) - the platform built by journalists' technologists, started under the Mozilla Foundation and now stewarded by Vox Media as an Apache-2.0 project serving 23 languages. Its founding premise is that online comments are broken and moderation is the fix. Moderators get a full queue system - reported comments, system-held pending comments, and configurable pre-moderation - backed by AI toxicity scoring that warns commenters before posting and holds high-scoring comments for review, Akismet spam detection, banned and suspect word lists, and automatic repeat-offender handling that pre-moderates users whose rejection rate crosses a threshold. Readers get features designed for healthier conversation: journalist badges in threads, muting of annoying voices, notifications, instant new-comment alerts, and timeouts rather than just bans. For publishers the economics are the point - no ads, no trackers, no hidden pixels anywhere in the code, full ownership of audience data, and GDPR compliance beyond requirements. Integration is one embedded script; SSO connects existing registration, and a GraphQL API supports customization and extension.

When Commento's original maintainer went quiet, Commento++ bundled the community's bug fixes and stalled merge requests into a batteries-included release of the beloved Go-based Disqus alternative - and kept building. The core promise is unchanged: an embeddable comments box that is orders of magnitude lighter and faster than Disqus, with no ads, tracking, or data sales - two lines of HTML and a PostgreSQL database. On top of Markdown comments, voting, Disqus import, OAuth login (Google, GitHub, Twitter) plus SSO, sticky comments, thread locking, and email notifications, the fork's additions are substantial: WebSocket-powered live comment updates with permalinks and highlight animations for new arrivals, guest commenting with a name, a cross-domain moderation dashboard for approving and deleting comments in one place, MathJax rendering support, wildcard domain matching, a reInit hook that makes single-page-application integration clean, and Perspective API spam scoring alongside the existing Akismet integration. Optional page-view logging graphs traffic on the dashboard, native SSL termination works without a proxy, and script-tag data attributes control fonts, CSS overrides, deleted-comment visibility, and polling-versus-WebSocket behavior.

One REST call, 130+ notification services: Apprise API wraps the well-known Apprise library in a lightweight Django/Gunicorn microservice, so "send an alert" works the same whether it goes to Slack, Discord, Telegram, Teams, email, SMS, Pushover, or PagerDuty - each addressed by a simple URL scheme. It solves the credential-sprawl problem cleanly: instead of embedding provider tokens in every app, cron job, and CI pipeline, you centralize them here and everything else just POSTs a body and title. Two modes cover every workflow. Stateless calls to /notify carry target URLs in the payload (or fall back to a default set via APPRISE_STATELESS_URLS); stateful mode stores named configurations server-side under keys, so /notify/{KEY} fans out to everything registered - with tag-based routing (comma for OR, space for AND) selecting which endpoints fire per message. Messages take info, success, warning, or failure types in text, Markdown, or HTML, with attachments up to a configurable size. A built-in web UI manages and tests configurations, APPRISE_CONFIG_LOCK makes the store read-only, service allow/deny lists restrict which schemes work, webhook remapping adapts third-party payloads, and a Prometheus /metrics endpoint watches the gateway itself.

Real-time alerts from your own infrastructure to your phone, with no Firebase, Pushover, or third-party push service in the path: Gotify is a simple, self-hosted notification server written in Go. The model is deliberately minimal: senders push messages with a single HTTP POST to the REST API, receivers subscribe over a WebSocket stream, and a clean React web UI manages the pieces. Senders are namespaced as "applications," each with its own token, so your backup script, Uptime Kuma, CI pipeline, and cron jobs each get an identity, an icon, and independently revocable credentials - centralized alerting from many services with per-source management. Messages carry a title, body, and priority level that maps to notification importance on the client. The official Android app (on both F-Droid and Google Play, notable for working entirely without Google Play Services) shows push notifications for new messages; the web UI itself supports Web Push in the browser; and gotify/cli pushes messages from shell scripts with one command. A server-side plugin system adds custom behavior, and the whole thing runs as a single small binary with SQLite by default - near-zero resource footprint. Because dozens of tools (and Apprise) speak Gotify natively, it slots in as the notification hub for an entire homelab or ops stack.