// the find
Bytedesk/bytedesk
Open Souce IM with AI powered live-chat, email, ticket support, omni-channel customer service，alternative to slack + zendesk/intercom/hubspot/ada/decagon/sierra
Bytedesk is a Java/Spring Boot monorepo that bundles team IM, omnichannel customer service, ticketing, a knowledge base with RAG, and even a FreeSwitch-based call center into one self-hosted platform — basically an open-source stab at Zendesk + Intercom + a PBX. It's aimed at teams who want to self-host the whole support stack rather than piece together SaaS tools, and who are comfortable running a Java/Maven deployment with multiple middleware services.
The scope is genuinely broad and coherent: chat, tickets, knowledge base, and an AI/RAG module that supports Ollama, DeepSeek, and ZhipuAI (plus function calling and MCP) rather than locking you into one LLM vendor. It ships Docker Compose profiles for different DB/MQ combos (MySQL/Postgres/Oracle, Artemis/RabbitMQ) so you can pick your stack at deploy time. It also comes with a real observability setup out of the box — Grafana, Prometheus, OpenTelemetry, and an ELK stack with provisioned dashboards — which most self-hosted projects at this star count skip entirely.
The licensing is a real problem, not a nitpick: the file header asserts Business Source License 1.1 with explicit anti-hosting/resale restrictions, the License section at the bottom of the same README says AGPL v3, and a separate Terms of Use section adds a third, different commercial/no-resale clause. These three statements contradict each other, so you cannot tell from the README alone what you're actually allowed to do — get this in writing from the maintainer before deploying commercially. The deploy/freeswitch/conf directory vendors the entire stock FreeSwitch config tree (thousands of default XML files, including test extensions 1100-1149), which bloats the repo and makes it hard to tell what's been customized versus left as FreeSwitch defaults. It's a large, loosely-documented Maven monorepo (channels/, enterprise/, modules/, plugins/, demos/, projects/, starter/) with no module/dependency diagram in-repo — understanding the architecture means reading an external docs site rather than the README. Primary documentation and community activity are Chinese-first (weiyuai.cn is the canonical docs/demo domain), so English-speaking adopters should expect translated docs and slower English support.