// the find
abhinavxd/libredesk
Open-source, self-hosted customer support desk in a single binary. A lightweight alternative to Intercom, Zendesk, Chatwoot.
LibreDesk is a self-hosted helpdesk with a Go backend and a Vue 3 frontend, shipped as a single binary. It puts email, live chat, and WhatsApp conversations in one shared inbox, with help center, automations, and SLA tracking included. It is aimed at small and mid-sized support teams that want Zendesk or Intercom-style workflows without a SaaS subscription or third-party data hosting.
- Shipping one Go binary means there is no separate Node or Ruby runtime to keep running in production, and the README documents three install paths: Docker, Railway, and plain binary.
- Email, live chat, and WhatsApp conversations land in one queue, and the README says teams, tags, SLAs, and automation rules apply across all three. Cross-channel routing is usually the part that gets bolted on badly, so it is worth checking first.
- The tree has Go tests next to the commands, frontend unit tests next to form schemas and editor extensions, and separate CI workflows for backend, frontend, and i18n. That is more test scaffolding than I'd expect at this stage of a project.
- Per-action roles and OIDC SSO are listed as features rather than afterthoughts, which matters once more than a few agents share an instance.
- The README is a one-line-per-feature list that defers depth to libredesk.io and the docs site. Whether the email channel handles threading, bounces, and reply parsing well can't be judged from the README alone.
- The AI assistant and agent copilot send conversation content to an LLM, but the README doesn't say which providers are supported, whether a local model works, or what leaves the server. For a tool that holds customer email, that is the first question a buyer will ask.
- The operational story is thin. The Railway template provisions Redis, but the README doesn't say what uses it. Upgrades, backups, and scaling aren't covered, even though the tree includes an upgrade command.
- The README gives no version, stability statement, or release cadence. The VERSION file is the only signal, so an adopter has to read the releases page to decide whether this is ready for production.