useopendesk/opendesk

A credible small-team helpdesk: one Go binary plus Postgres, with self-hosting that runs the same code as the hosted service. The AI assistant and mobile apps are promising but only lightly specified.

The problem

When a team answers customer questions from a shared mailbox and a chat widget, work scatters: one person replies by email, another sees an unread chat, and a resolved question never becomes a help-center article. The usual fix is a commercial helpdesk that bills per agent and keeps the data on the vendor's servers. opendesk instead puts email, live chat and a knowledge base into one inbox where ticket status, assignee, notes, tags and SLA are shared state, and every change reaches the rest of the team live. After migrating the support address, a teammate sees the same ticket and conversation without forwarding threads or asking who is handling it.

What's different

The architectural choice is the transaction-bound event relay. Every change another person should see is written as an event in the same database transaction as the change itself, then published through NATS and pushed to browsers and webhooks. In practice, two people looking at the same ticket are unlikely to diverge silently, and internal machinery stays small: no Redis and no Kafka. Self-hosted, NATS is embedded in the opendesk binary and the stack sits behind Caddy on a single domain. The cost is a heterogeneous codebase: Go for the API and workers, an Elixir realtime gateway with no database connection, Postgres, and Node/pnpm for the web frontend, so contributors need several toolchains. The second differentiator is Ollie, the built-in AI, which drafts, triages, translates and answers from the knowledge base using any Anthropic- or OpenAI-compatible provider, including local models — a useful path for teams that must keep customer text close, though the introduction gives little detail on evaluating its answer quality. A REST API, signed webhooks, a realtime socket and MCP integration cover extensibility; the desktop app for macOS, Windows and Linux and a native iPhone app extend it to agents outside the browser.

Who should try it

Good fit: a small support or success team that already runs a Linux server, wants email and live chat under one roof, and values the option to host the data itself. The self-host quickstart describes Docker Compose on any Linux server with one install command that generates secrets and pins a release. A poor fit: a team without Docker or Linux experience, or one that mainly needs a polished managed product, since running the stack becomes the team's upkeep. Teams that would rather not operate anything can use the hosted service, which the README says runs the same code, but that is a different trade-off than self-hosting.

Requirements and limitations

Self-hosting needs a Linux server, a domain and Docker; the installer asks for the domain and a TLS email. Development from source is heavier: Go, Node with pnpm, Elixir and Docker for Postgres, with separate processes for API, realtime gateway and web app. Ongoing care is ordinary for a self-hosted stack: Postgres backups, release upgrades, running the Caddy front door, and TLS renewal. Email is the main integration to check before committing: replying from the support address depends on Google, Microsoft or SMTP credentials, and until a mail driver is configured, verification and invitation mail only appears in the API log. The README notes that larger teams can buy migration help or support agreements, which is not part of the open-source install.

HotRepo's take

HotRepo began tracking on 2026-10-24 and recorded the project at #7 on the NEW-REPOSITORY board (新项目榜, not the overall Trending board) on 2026-10-25, with 443 total stars — a snapshot, not daily growth. The repository was created on 2026-10-11, so comparable trend history cannot yet be judged. Before adopting, check the self-hosting docs for the supported email-provider configuration and the upgrade path between pinned releases; those two details will shape day-to-day operation more than the feature list.