— Use case · feature requests
featurevote.app collects requests in one board so you can see which ideas have the most support. People submit and vote without creating an account, and those who leave an email can hear when a request ships.
— What it is
It gives requests, votes, comments and statuses one shared place. People can see what has already been asked, and your team can see which requests have support.
Requests otherwise sit across support threads, chat channels and spreadsheets, where the next person cannot find them or add a vote. A board keeps them visible and ranked, and it asks for less than an issue tracker: a short description and an email, no account. The feature request form template shows the form people fill in.
— Submitting and voting
People vote without an account or an email. Submitting a request needs a short description and an email for later updates. Both are part of the free plan.
The board shows requests in vote order. You can require an email to vote when follow-up matters more than reach, and the no-login voting page explains the vote controls.
— From request to release
— Three boards that exist today
— Pricing
The free plan is permanent, not a trial, and asks for no card. Your users post requests and vote without limit, and your team manages as many requests as it likes, so an existing backlog fits on day one.
Paid plans let you hide the featurevote badge and add Slack, webhooks, surveys, Hidden boards, a bigger email list, emails from your own domain and private Research. Growth is $9 a month billed yearly as $108, or $12 billed monthly. Pro is $29 a month billed yearly as $348, or $35 billed monthly. Lifetime is one payment of $239 for an email list of up to 1,000 and private Research. Full detail on the pricing page.
— Where it stops
A larger platform such as Canny or Featurebase fits better when prioritisation depends on revenue or CRM data for each voter, or when you need a Jira or Linear sync, single sign-on or audit logs. A chat poll is enough for one question with fixed answers. And when every vote must be tied to one person, anonymous voting is the wrong shape: it keeps everyday duplicate votes out, but it cannot enforce that standard.
Comparing the full workflow? Read featurevote vs Featurebase for capabilities, plan limits and what moving an existing board involves, or the Canny comparison for tracked-user pricing and its trade-offs.
— Questions, answered short
No. Voting needs nothing at all. A request needs a short description and an email, so the person can hear when it ships. Comments ask for an email as well.
Yes. Embed the board on a page, or put a button in your app that opens the request form in a panel. On a paid plan, a Hidden board opens through your embed while its bare link stays closed, which suits a product behind a login.
Import a CSV file or paste a list. Titles, descriptions, statuses and old vote totals come over, and comments and voter names stay behind. A customer’s email can still be recorded as a vote on any request.
The count blocks repeat votes from the same browser, though clearing browser data allows another vote. Requiring an email, or limiting the board to a Patreon campaign or a Discord server, makes it stricter.
Yes. A board can be public, unlisted, hidden behind your embed’s access key, or private to your team. A single request can also be marked private.