Quackback is an open-source feedback platform. Voting boards, a public roadmap, changelogs, and 23 integrations. The same workflow that tools like Canny and UserVoice established, but open source and with a built-in MCP server.
Why feedback tools need an open-source option
UserVoice starts at $999 per quarter. Canny has a free tier, but meaningful features require their paid plans. Productboard charges per seat. These tools got the collection model right. But they're closed-source, expensive at scale, and none of them offer self-hosting.
Meanwhile, development workflows have changed. AI agents write code, review pull requests, and ship features. But customer feedback is still a manual loop: triaging, responding, updating statuses, notifying voters when something ships. That work doesn't scale for small teams.
Plausible brought open source to web analytics. Cal.com did it for scheduling. Formbricks did it for surveys. PostHog did it for product analytics. Quackback does it for feedback collection.
Try it locally in under a minute:
git clone https://github.com/QuackbackIO/quackback.git
cd quackback && bun run setup && bun run dev
Agents as part of the feedback loop
Quackback ships with an MCP server. Claude, Cursor, and Windsurf already support the protocol. Connect an agent and it gets read-write access to your feedback data.
An agent connected to Quackback can:
- Search across all feedback posts and changelogs
- Triage posts: update status, assign owners, add tags, write official responses
- Create new posts and changelog entries
- Comment and vote on behalf of your team
Every action is attributed. Every change is auditable. When an agent triages a post, you see which agent did it, when, and what changed.
In practice, this means a team of three can keep up with a feedback volume that would otherwise require dedicated support staff. Posts that would sit unread for weeks get triaged in hours.
Open source. Self-host. Own your data.
Quackback is AGPL-3.0 licensed. You can read every line, audit every dependency, and run it on your own infrastructure.
Self-host with Docker or deploy in one click on Railway. Your feedback data stays in your PostgreSQL database. No vendor lock-in. No per-seat pricing.
What's included
For your users: Public feedback boards with voting, status tracking, nested comments, and official responses. A public roadmap. A changelog that notifies voters when their requested features ship.
For your team: Admin inbox with unified triage, filtering, bulk actions, and deduplication. Two-way sync with your issue tracker. SSO and OIDC for enterprise authentication.
For your stack: Slack, Linear, Jira, GitHub, GitLab, Asana, ClickUp, Intercom, Zendesk, HubSpot, Salesforce, Discord, Teams, Zapier, and Make. Full REST API with OpenAPI 3.0 docs. Webhooks with HMAC-SHA256 signing. The MCP server for agents. Custom branding with your logo, colors, and domain.
Get involved
Quackback is on GitHub at QuackbackIO/quackback.
I'd especially like feedback on the MCP server. Giving agents access to user feedback is new territory, and the interface is shaped by how people actually use it. Follow the MCP setup guide to connect your agent, then tell me what's missing.
Top comments (0)