Feature voting that tells requesters when their idea ships
Quackback hosts public boards where customers post requests, vote and comment. The team lays out what is planned on a roadmap and links each changelog entry to the requests it ships, so everyone who voted for them hears about it. Version 0.14.0, released on 5 October 2026, added a shared support inbox for live chat, email and tickets, a help center and a status page, each switched on in settings.
Votes survive merges, and Linear issues drive request status
- Merging keeps the votes: similar ideas show up while a customer is typing, and a merged request hands its votes to the one it joins.
- Tracker links that move requests: a request tied to a Linear or GitHub issue changes status as the issue does. Jira and the other trackers send each change for approval first.
- One embeddable widget carries feedback, chat, help articles and the changelog, with SDKs for iOS and Android.
- An MCP server on every instance at
/api/mcp, with OAuth sign-in, lets Claude or Cursor search and triage feedback and tickets. The REST API has an OpenAPI spec, and webhooks are signed. - Integrations cover issue trackers (Linear, GitLab, Jira, Azure DevOps), chat (Slack, Teams, Discord), support and CRM (Zendesk, Intercom, HubSpot) and automation (Zapier, n8n).
- Portal and widget in more than ten languages, right-to-left scripts included, picked from each visitor's browser.
Postgres with pgvector, an AI endpoint you supply, and no downgrades
The repository describes itself as an open source alternative to Canny, UserVoice and Productboard. Since 0.14 the README reads "customer feedback and support", and the website FAQ covers moving over from Canny or UserVoice. Imports go through a CSV upload in settings, since the command-line importers were removed in 0.14.
Self-hosting gets every feature under AGPL-3.0. The README promises unlimited seats and no license key. Run a modified version as a service and the changes must be published under the AGPL. Contributors sign a CLA that lets Quackback Ltd offer their code under other terms, proprietary licenses included.
PostgreSQL 14 or later with pgvector 0.5 and pg_trgm is required. Realtime features rely on LISTEN/NOTIFY, so the connection must be direct or session-mode; transaction-mode poolers will not work. Redis was dropped in 0.14, and S3-compatible storage is only needed for uploads. Exactly one outbound email provider may be set (SMTP, Amazon SES or Resend), and with two the app will not start. The documented minimum is 1 CPU core, 1 GB of RAM and 10 GB of disk.
AI features stay off until an OpenAI-compatible endpoint is configured. Duplicate detection, summaries, translation and the Quinn support agent all run through a key and base URL that the operator supplies, such as OpenAI or OpenRouter.
Self-hosted installs send one anonymous usage snapshot a day. It carries the version, setup details and banded counts, with no content of any kind. Since 0.14 it goes to PostHog, and DISABLE_TELEMETRY=true turns it off. Outgoing emails also carry a small "Powered by Quackback" footer.
The latest release is 0.14.1, published on 7 October 2026. Ten releases came out between 9 June and 7 October, and the last commit is dated 22 October. The upgrade from 0.13 to 0.14 runs about 140 migrations and cannot be reversed: going back to 0.13 means restoring a backup. Since that release, the widget's identify call only recognizes a visitor when it carries a signed ssoToken.