Self-hosted alternatives to Canny

openheard

Feedback board, public roadmap and changelog for your product, in one Worker with D1, KV and R2

What a Canny user would miss

User segments, revenue-based prioritization and connectors that pull feedback from support and sales tools. Email needs a domain onboarded for Cloudflare Email Sending, and the project started in September 2026.

What it adds

Runs as one Worker with D1, KV and R2 in your own Cloudflare account. It imports a CSV export from Canny, can sit behind Cloudflare Access, and has an MCP server and an HTTP API with per-workspace keys.

• Yes Public feedback boards with voting and comments. Public board with voting, comments, reactions, anonymous voting and an optional approval queue.
• Yes Tags and categories for organizing requests. Tags and boards in the schema.
• Yes Duplicate detection and merging. Similar posts are suggested before posting, and admins can merge posts.
• No Segmenting and prioritizing requests by user group or revenue. No user segments or revenue fields found.
• Yes Status updates emailed to voters. Voters, commenters and authors get an email on status changes, with opt-out links; needs a sending domain.
• Yes Public or private roadmap. Roadmap with drag between columns that follow custom statuses; the tab can be hidden under access settings.
• Yes Changelog with an in-product widget. Changelog with linked posts, RSS and email subscriptions, plus a widget tab with a new-release badge.
• Partly Capturing feedback from support and sales tools. HTTP API creates posts and comments; Slack, Discord and webhook alerts only go out; no inbound connectors.

Sources:github.com/heilonng23/openheard/blob/main/README.mdgithub.com/heilonng23/openheard/blob/main/packages/db/src/schema/feedback.tsgithub.com/heilonng23/openheard/blob/main/docs/widget.mdopenheard.com

FeedLog

Self-hosted Canny alternative with voting boards, a public roadmap, changelogs and an in-app support widget

What a Canny user would miss

Tags, user segments, revenue-based prioritization, connectors that pull feedback from support and sales tools, and an in-product changelog. It needs an external PostgreSQL 17 or newer database with pgvector, and duplicate detection and AI drafting need an OpenAI-compatible API key.

What it adds

Also has a help center and an in-app support widget with an AI agent and a human handoff inbox. The same codebase deploys to Cloudflare Workers, Vercel or Docker, and the data lives in your own PostgreSQL database and R2 bucket.

• Yes Public feedback boards with voting and comments. Boards, posts, votes and Markdown comment threads, with a guest posting setting.
• Partly Tags and categories for organizing requests. Boards group posts; no tags in the schema.
• Yes Duplicate detection and merging. Vector embeddings flag similar posts, and admins can merge and unmerge posts.
• No Segmenting and prioritizing requests by user group or revenue. Posts sort by votes; no user segments or revenue fields found.
• Yes Status updates emailed to voters. Upvoters are subscribed and the admin can notify them after a status change; needs an email provider.
• Yes Public or private roadmap. Drag-and-drop roadmap page with planned, in progress and done columns.
• Partly Changelog with an in-product widget. Changelog with drafts, categories, reactions and AI drafting; the widget docs list no changelog tab.
• No Capturing feedback from support and sales tools. No connectors to outside tools found; the widget Agent can open a post from its own chat.

Sources:github.com/linkcraftstudio/feedlog/blob/main/README.mdgithub.com/linkcraftstudio/feedlog/blob/main/server/db/schemas/index.tsgithub.com/linkcraftstudio/feedlog/blob/main/docs/widget.mdfeedlog.ai