Most pages in this directory compare two tools that disagree about what to charge for. This one does not.
Features.Vote charges a monthly price, never meters voters, lets people vote without an account and ships a native SwiftUI SDK, and so does VoteFirst. If you are choosing between the two on billing shape, you are choosing between two of the same answer.
The difference is narrower and it is worth being exact about. On their board every vote counts once. Here a vote can carry the money behind the person who cast it.
Everything on their side was read on features.vote on 14 September 2026.
What are the alternatives to Features.Vote?
Features.Vote is nine or twenty nine dollars flat with unlimited voters, which puts it at the cheap end of this table rather than the expensive one. The difference worth comparing here is not the price but what a single vote is allowed to be worth.
| Vendor | From | Billed per | Free plan | Trial |
|---|---|---|---|---|
| Trello | $5/user/mo | user | Yes | – |
| VoteFirst | $7.50/mo | plan | – | 14 days, card |
| Features.Vote | $7.50/mo | project | – | 14 days |
| Jira Product Discovery | $10/creator/mo | creator | 3 creators | – |
| LoopedIn | $12/mo | plan | 1 of each | – |
| WishKit | $12.50/mo | project | 5 requests | – |
| Sleekplan | $13/mo | workspace | 1 admin | 30 days, no card |
| Upvoty | $13.50/mo | project | – | 14 days |
| Noora | $14/mo | workspace | – | 7 days |
| Convas | $15/mo | tracked user | 25 users | – |
| FeedBear | $15/mo | project | – | 14 days |
| Supahub | $15/mo | workspace | 1 board | 10 days |
| ProductLift | $19/mo | workspace | – | 14 days |
| Productboard | $19/maker/mo | maker | 500 notes | – |
| Roadmunk | $19/creator/mo | creator | – | 14 days |
| Ducalis | $20/mo | changelog subscriber | 500 subs | – |
| Frill | $22/mo | workspace | – | 14 days |
| Fider | $25/mo | workspace | 250 items | – |
| Featurebase | $29/seat/mo | seat | 1 seat | – |
| Headway | $29/mo | plan | Yes | – |
| Nolt | $29/mo | board | – | – |
| UserJot | $29/mo | workspace | 2 boards | 14 days |
| Aha! Ideas | $39/user/mo | user | – | Yes |
| Savio | $39/mo | paid user | – | 14 days |
| Beamer | $49/mo | monthly active user | 1,000 MAU | – |
| Feature Upvote | $49/board/mo | board | – | 30 days |
| Rapidr | $49/mo | workspace | – | 14 days |
| Suggested | $49/mo | plan | – | 15 days |
| Gleap | $49/mo | plan | – | 14 days |
| FeatureOS | $50/mo | plan | – | 30 days, no card |
| Olvy | $60/mo | plan | 25 items | – |
| AnnounceKit | $39/mo | module | – | 15 days, no card |
| Canny | $79/mo | tracked user | 25 users | – |
| LaunchNotes | $249/mo | plan | – | 14 days |
| Pendo | Not published | monthly active user | Beta | – |
| ProdPad | Not published | module | – | 7 days |
| UserVoice | Not published | quoted | – | 30 days |
| airfocus | Not published | quoted | – | – |
| ProductPlan | Not published | quoted | – | – |
| Productroad | $9/mo | plan | 50 users | 14 days, no card |
| Quackback | $29/mo | plan | 1 board, 50 posts | 14 days, no card |
| ProdCamp | $99/mo | plan | 2 admins, 1 product | – |
| Harvestr | $65/editor/mo | editor | – | 14 days |
| Productlane | $29/user/mo | user | – | Yes |
| Ideanote | $6/user/mo | user | 10 users, 250 ideas | – |
| Craft.io | $19/editor/mo | editor | – | 14 days, no card |
| HYPE Boards | €79/mo | plan | – | 14 days, no card |
| Noticeable | $24/mo | plan | 1 project, watermarked | 14 days, no card |
Read on each vendor's own pricing page, with the billing switch on the yearly side wherever one is published. From is the cheapest paid rate per month. What each one includes, as well as what it costs, is on one page.
What does Features.Vote cost?
Two plans, flat, with two months free on annual billing.
| Plan | Paid monthly | Paid yearly |
|---|---|---|
| Lite | $9 | $90 |
| Growth | $29 | $290 |
- Lite lists 1 project, public voting board, public roadmap, email notifications, moderation tools, basic customization, no interaction limit.
- Growth lists unlimited projects, activity log, analytics, unlimited comments, user segmentation, hiding the powered by tag, private boards, public changelog, advanced customization, team management, custom domain, priority support.
Their trial is fourteen days and their page says it asks for no card. They also publish a one time setup service starting at ninety nine dollars for people who would rather not do the installation themselves.
Their own words on the unit are worth quoting, because so few vendors in this category will write them down. "Pricing never scales with votes, voters or tracked users." Both plans and that sentence are set out on the pricing page for them.
If you want the other side of the comparison rather than another page about it, a trial here runs 14 days and asks for a card at signup, and it is $9 or $39 a month after that.
What is Features.Vote?
Features.Vote is a feature voting board with a public roadmap and changelog, embedded in a website or a web app, with a native SwiftUI SDK for iOS, iPadOS and macOS alongside it.
Their own description of the voting model is the part worth reading twice, because voters click once, with no signup, no email and no SSO. VoteFirst does the same thing with an anonymous cookie, which is why the two feel so similar to a visitor.
Where is Features.Vote cheaper?
At the top of their ladder, and it is not close.
Features.Vote puts a public changelog on Growth, at twenty nine dollars a month, alongside unlimited projects, private boards, a custom domain and team management. The nearest plan here is thirty nine dollars and carries the same four things.
So a team that needs several boards and a custom domain pays ten dollars a month less over there, which is a hundred and twenty dollars a year.
At the bottom the two are the same number. Nine dollars against nine dollars, one project each.
Nothing here counts the people who vote, so a busy board costs the same.
What does the weighting change?
The order of the board, without anybody re sorting it.
A vote here is multiplied by the tier the voter is on, and the tier comes from Stripe, Paddle or a CSV rather than from a person typing it.
Four votes from four Enterprise accounts can outrank thirty from a free tier, and the board shows both numbers side by side so nobody has to trust the arithmetic.
Nothing on the Features.Vote pages read on 14 September 2026 mentions vote weight, MRR or a customer tier. They do sell user segmentation on Growth, which filters who you are looking at rather than changing what a vote is worth. The mechanism here is written out with the formula and the code.
Do both of them work inside an iOS application?
Yes, and this is the one part of the category where that question has two good answers.
Their page describes a Swift SDK giving SwiftUI board, roadmap and changelog views for iOS 16, iPadOS and macOS with no dependencies. VoteFirst publishes a Swift package on GitHub with drop in views for iOS and macOS, and it is one of the integrations listed on its own page.
If you are shipping an Apple application, the third name to look at is WishKit, which is native SwiftUI as well and priced at fifteen dollars a month. The WishKit comparison is written up separately.
Where do the public roadmap and single sign on sit?
One is on the cheaper plan and the other is deliberately absent.
Features.Vote carries a public roadmap on the nine dollar Lite plan, alongside the public voting board, email notifications and moderation tools. Nothing on either Features.Vote plan names SSO, and their own FAQ explains why, because voters click once with no signup and no email.
VoteFirst's public roadmap is on the nine dollar plan too, and voting needs no account, but single sign on for voters comes with the thirty nine dollar plan, through a token from your own application; the dashboard keeps its own login.
Does Features.Vote have a free plan?
No. Their page publishes a fourteen day trial that asks for no card, and two paid plans after it.
Neither does VoteFirst, and its trial does ask for a card at signup. If a free tier is the requirement, the category page names the tools that publish one and neither of these two is on that list.
What this costs
Lite
$9 /mo
Pro
$39 /mo
Lifetime
$999 once
Fourteen day trial of Pro, card asked for at signup. Nothing here counts the people who vote, so the bill does not move when the board starts working. The long version, with what happens if you stop paying.
Is there a free Features.Vote alternative?
Fider is the one to know about. It is open source, so hosting it yourself costs a server and nothing else. UserJot publishes a free tier with two boards, and Supahub and Featurebase each publish one with a single board. All three were read on their own pages on 14 September 2026.
Is Features.Vote worth it?
At nine dollars for one project, on the same terms VoteFirst charges nine dollars for, yes.
That is an unusual sentence to write about a competitor, and it is true. Their price never moves with voters, their trial asks for no card, and their SDK is real.
The question is not whether it is worth the money. It is whether you need a vote that carries the money behind the person casting it, because that is the one thing their published pages do not describe.
What does VoteFirst cost, and when is theirs the better answer?
Nine dollars a month for one project, thirty nine for unlimited projects, the API, a custom domain and a team.
Theirs is the better answer if you need several boards and a custom domain and you do not need the weighting, because twenty nine beats thirty nine and the feature lists at that tier are close.
It is also the better answer if a trial without a card is what gets the decision made this week.
VoteFirst is the better answer if the question you actually have is which of these requests comes from the accounts that pay you. That is the whole reason VoteFirst exists, and it is on the nine dollar plan rather than the top one.
14 days, a card at signup, then $9 or $39 a month.
What moving actually involves
There is no importer for Features.Vote on VoteFirst's side; the board import reads only Canny and Featurebase.
Voters and the revenue behind them come in from a CSV or from a billing connection, which is the part the weighting needs. The requests themselves are rebuilt by hand or by a script against the API, and the vote counts start again.
The five steps, with the endpoint each one uses, are written out in full, and they are the same five whatever you are leaving.
Features.Vote against the others, one at a time
One page here puts Features.Vote against a single rival and works out which bill is smaller at each size.