Introducing Quackback

Quackback is an open-source feedback platform. It gives you voting boards, a public roadmap, changelogs, and 23 integrations, the same workflow that tools like Canny and UserVoice established, but open source and with AI agent access built in.

Why feedback tools need an open-source alternative

UserVoice starts at $16,000 per year with annual billing. Canny's free plan caps at 25 tracked users, and meaningful features like PM integrations require their paid plans. Productboard is similar. These tools got the collection model right. But they're all closed-source, expensive at scale, and there's no option to self-host. No way to extend them. No path to complete data sovereignty for those who need it.

At the same time, development workflows are accelerating. AI agents help write code, review pull requests, and ship faster than ever. But customer feedback is still stuck in a manual loop. Triaging, responding, updating status, notifying voters when something ships. For most teams, that work doesn't scale.

Plausible brought open source to web analytics. Cal.com did it for scheduling. Formbricks did it for surveys. PostHog did it for product analytics. Feedback collection hasn't had an equivalent. Until now.

You can 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

This is the part of Quackback that doesn't exist anywhere else.

Quackback ships with an MCP server, the same Model Context Protocol that Claude, Cursor, and Windsurf already support. Connect an agent and it gets real access to your feedback data. Not read-only. Not a summary. Actual ability to act.

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 decision is auditable. When an agent triages a post, you see which agent did it, when, and what it changed. You stay in control. The agent handles the volume.

The practical effect: a solo founder or a team of three can respond to feedback like a team of ten. Posts that would sit unread for weeks get triaged in hours. Users who report bugs get a response the same day.

Open source. Self-host. Own your data.

Quackback is AGPL-3.0 licensed. The code is public. 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. Not on my servers. Not behind an API you don't control.

No vendor lock-in. No per-seat pricing. No feature gates.

What ships today

For your users: Public feedback boards with voting, status tracking, nested comments, and official responses. A public roadmap so they can see what's planned, in progress, and shipped. A changelog that links back to the posts that requested each feature.

For your team: An admin inbox with unified triage, filtering, bulk actions, and automatic deduplication. Two-way sync with your issue tracker so status stays current across tools. SSO and OIDC for enterprise authentication.

For your stack: 23 integrations including Slack, Linear, Jira, GitHub, GitLab, Asana, ClickUp, Intercom, Zendesk, HubSpot, Freshdesk, Salesforce, Discord, Teams, Notion, Monday, Trello, Shortcut, Azure DevOps, Zapier, Make, n8n, and Stripe. Full API access, webhooks, and the MCP server for agents. Custom branding with your logo, colors, and domain.

Pricing

The self-hosted version of Quackback is free and includes the core platform: feedback boards, roadmap, changelog, integrations, API, and MCP server. Everything you need to run your feedback loop.

Over time, I plan to introduce enterprise-specific features (things like audit logs, advanced SSO configurations, and team management controls) as part of a paid tier. I want to be upfront about that. Keeping Quackback sustainable means some features built for larger organizations will help fund development for everyone.

I'm also building a managed cloud version for teams that don't want to run their own infrastructure. Cloud will include a free plan for small projects, with paid tiers for teams that need more. Automatic updates, backups, and uptime monitoring, without managing your own servers.

Cloud pricing will be competitive with existing tools. If you're interested, join the waitlist and you'll be the first to know when it's ready.

What's next

• Import tools: Migrate from Canny and UserVoice with your data intact
• Agent workflows: Automated triage, AI-powered deduplication, and feedback summarization so every post gets a response without manual effort

Learn more

If you want to see how Quackback stacks up against existing tools, start with our best customer feedback tools in 2026 roundup or the side-by-side comparison pages. For teams interested in self-hosting and data ownership, see our guide to open source feedback tools.

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 I'm shaping the interface based on how people actually use it. Follow the MCP setup guide to connect your agent, then tell me what's missing.