Quackback
Quackback unifies customer feedback boards, feature voting, public roadmaps, release changelogs, help centers, status pages, and a multi-channel support inbox into a single self-hosted workspace that replaces Canny, Productboard, and Intercom. Product teams use its branded boards to collect feature requests and bug reports, merge duplicate submissions, and rank demand by user votes or customer segments. When a request moves into development, two-way integrations with Linear, GitHub, and Jira automatically update the card across customizable Kanban status columns or quarterly timeline views on your public roadmap. Support agents work out of a shared inbox that brings real-time Messenger web chat, inbound email threads, and durable support tickets together under one roof, complete with SLA timers, office hours, saved macros, and CSAT surveys. Conversations that uncover a feature gap convert directly into votes on existing feedback posts without losing thread context. Quinn, the built-in AI assistant, answers common questions from your Help Center articles, drafts agent replies, and exposes a Model Context Protocol server so external AI tools can triage posts or manage tickets. Once features ship, publishing a scheduled changelog entry automatically notifies every voter via email and in-app alerts. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.
Astuto
Feature requests, bug reports, upvotes, and a public roadmap: Astuto (Ruby on Rails backend, React frontend) gives users a Canny-style feedback portal so product decisions rest on visible demand rather than the loudest voice in the room. Feedback organizes into as many boards as you want (features, bugs, integrations), each post carrying a custom status you define - "planned," "in progress," "shipped," or whatever matches your process - and those statuses feed a public roadmap view showing users what is actually being worked on. Participation friction is adjustable at both ends: sign-in works with plain email or any OAuth2 provider, anonymous feedback can be enabled for unregistered users, and a moderation queue lets you approve posts before they appear when spam is a concern. Integration hooks are practical rather than sprawling - webhooks fire on events to connect Jira, Trello, or Slack, and a REST API manages the whole feedback space programmatically. Brand customization, an invitation system, private-site settings, and recap emails for administrators complete a deliberately minimal tool: it collects, organizes, and prioritizes feedback well, for free, forever.