Let customers vote. Not email.

A public page where customers post ideas, vote and follow them without an account. Link an idea to a card: once that card ships, everyone who asked for it gets an email.

From request to “shipped”.

1. A customer asks for something: On your feedback page, without an account. Others vote and follow the idea.
2. You link a card: Review ideas, merge duplicates and attach them to the work that solves them.
3. Shipped, and everyone knows: When the card lands in a release or in the changelog, the idea is marked shipped and its followers get an email.

What the feedback portal includes.

• No account needed. Visitors post ideas and vote. Whoever wants updates leaves an email address.
• Public roadmap. Planned, in progress and shipped, on a page of its own.
• Review first. New ideas can wait until someone on the team approves them.
• Merging. The same idea twice? Merge them.
• Replies. Add a public reply to an idea, so nobody has to guess why it hasn’t happened yet.
• Shipped by itself. The status follows the card: once it’s in a release or the changelog, the idea is marked shipped.
• Through the API and MCP. Ideas from your support tool or an AI assistant land there too.

Frequently asked questions

Which tools does the feedback portal replace?

A voting portal such as Canny, Featurebase or UserVoice.

Do customers need an account?

No. Posting and voting work without an account. Whoever wants to hear when the idea ships leaves an email address.

Does every idea go public right away?

Only if you want it to. You can review new ideas first.

Which plan includes the feedback portal?

The feedback portal is part of Premium. That is one fixed price per workspace, however many members you have.

Changelog · Releases and test runs · Status pages

devbord · Pricing: one flat price per team · News · API documentation · Support: help and contact · Privacy: what we can and cannot see · Terms of service · Privacy policy · Error tracking for dev teams, Sentry-compatible · Time tracking and invoicing for dev teams · Status pages with uptime monitoring and incidents · Changelog and release notes from done cards · Incident management and on-call for dev teams · Release management, test runs and DORA metrics for dev teams · Meeting agendas, async stand-ups and retros for dev teams · Automation, a REST API, webhooks and an MCP server for dev teams · Sprint planning with burndown, a roadmap and OKRs · A Trello alternative for dev teams · A Sentry alternative that keeps your SDKs · A Linear alternative with error and time tracking · A Jira alternative for small dev teams · An Asana alternative for software teams · A ClickUp alternative with error tracking and invoicing · A Toggl alternative with a board and invoicing · A Harvest alternative with a kanban board · A Statuspage alternative with monitoring built in