FeedbackKit vs Feature Upvote: In-App Voting or a Web Board

Feature Upvote does one job and keeps it simple: a feedback board where people suggest ideas and upvote each other's. Its homepage talks to video game studios and SaaS teams, and its price is set per board. FeedbackKit covers the same core job for app teams, but the board lives inside your app rather than on a web page.

We make FeedbackKit, so read this with that in mind. Every Feature Upvote fact below comes from featureupvote.com and its help centre, checked on 17 October 2026 and linked where used. Both sites block scripted fetches, so we read them in a browser. The side-by-side table is on our FeedbackKit vs Feature Upvote comparison page.

The short version

• Feature Upvote is a hosted web board, public or private, where anyone can upvote without an account. It has custom statuses, status emails to the people who posted or commented (and to voters, if you turn that on), Slack and Discord on every plan, and Jira, Linear, Zendesk and Zapier links.
• FeedbackKit puts voting and comments into native screens in your iOS, macOS, Android, Flutter or React Native app, ranks requests by the MRR of the users behind them, and syncs status with nine issue trackers on Pro and up.
• Price: Feature Upvote is priced per board per month, from $49 billed yearly, with a 30-day trial and no free plan. FeedbackKit has a free plan, and Pro is $15 a month for 2 projects.

Where users give feedback

Feature Upvote's home is the board itself, at a featureupvote.com address or your own domain. Its homepage says there is "nothing to install": you create a branded board, make it public or private, and share the link.

To put the board inside a product, the help centre describes two routes. An iframe embed, which you enable for your own domains, and which needs a matching custom domain to work in Safari. And a JavaScript snippet for signed-in web apps, which Feature Upvote itself calls a proof of concept with limited features, and which needs a user ID, name and email for each user. There is no native SDK for iOS, Android, Flutter or React Native.

FeedbackKit starts in the app. You add an SDK and show its ready-made screens: a request list, a submit form, a detail view with comments, and vote buttons. There are SDKs for Swift and SwiftUI (iOS, macOS and visionOS 26 or later), Kotlin with Jetpack Compose, Flutter and React Native. The JavaScript SDK is a headless client with no screens, and there is a REST API.

For a website, FeedbackKit has embeds too. FeedbackKit can show a project's roadmap and its board of requests on your own website through an iframe, and it has a feedback form page you can embed the same way. The roadmap lists the feature requests and improvements you mark for it, grouped by target month, with requests that have no date under "On our radar". The board shows open requests in status columns with their vote counts, and visitors can vote on it when you turn voting on. A visitor is counted by an anonymous ID kept in their browser, with no sign-in. The form takes a title, a category, a description and an optional name and email. You turn embedding on per project in the web dashboard, which gives you the iframe code and a direct link for each page. Embeds are on every plan, in light or dark. There is no changelog for your users, and no hosted roadmap site on your own domain.

Voting and comments

On Feature Upvote, anyone can upvote a suggestion or add a comment, and moderators can see the date, IP address, browser and device of each vote. Moderators can vote on behalf of customers, merge and split suggestions, and filter spam. By default each vote counts as 1 for good, but you can switch on weighted scores, where a vote's value halves every 365 days, so the board reflects what people want now.

In FeedbackKit, users vote and comment inside your app, and a new request starts with its submitter's vote. Voting stops once a request is Completed or Rejected. Merging moves votes and comments to the request you keep, counting each voter once. Votes are not weighted by age; sorting by newest or by revenue gives a second view.

Here is how that looks in FeedbackKit, with sample data from a fictional hiking app:

Statuses, revenue and closing the loop

Feature Upvote is more flexible on statuses. A board starts with five default statuses, including under consideration, done and a private archived status, and you can add your own with colours and descriptions, make a status private, or remove the defaults. When you move a suggestion to a public status, Feature Upvote emails the person who posted it and anyone who commented, and voters who opt in when you offer them that, batched to one email a day. Those emails are sent for paid, active accounts, not during a trial.

FeedbackKit has six fixed statuses on every plan: Pending, Approved, In Progress, TestFlight, Completed and Rejected. Pro and up choose which ones a project uses, and there are no custom statuses. The submitter is emailed on every plan when a request moves to a status on the project's list. Choosing that list needs Pro, and emailing voters who opted in needs Team. A rejected request can carry a reason that goes into the email. More in closing the loop with status emails.

The bigger difference is revenue. On every FeedbackKit plan, your app passes each user's MRR through the SDK, and requests can be sorted by the total MRR of the users behind them. Feature Upvote ranks by votes, with the optional weighting above, and does not list revenue ranking. For Trailmate, the sample hiking app, Offline maps leads with 248 votes; sorting by MRR shows whether paying hikers agree.

Here is the triage view in the FeedbackKit admin app, with the same sample data:

Integrations

The Feature Upvote column comes from its pricing page and its help pages for Jira, Linear, Zendesk and the REST API.

Feature Upvote reaches Jira, Discord, Microsoft Teams, Zendesk and Zapier, which FeedbackKit does not. FeedbackKit keeps a request's status in step with the ticket in nine trackers, which differ in what else they sync: GitHub has no comment sync, and GitHub, Linear, Trello and Basecamp have no vote-count sync. The full matrix is on the integrations page.

Pricing

Feature Upvote charges per feedback board, per month, and its pricing page switches between US dollars, euros and pounds, and between monthly and yearly billing ("save 20%"). It typically expects one board per product. These are the figures it showed on 17 October 2026, per board per month:

Enterprise is for more than 10 boards, security audits, custom terms or payment through a reseller. Indie leaves out custom CSS, the Microsoft Teams, Jira and Zapier integrations, SAML single sign-on and hiding the "Powered by Feature Upvote" line. Every plan has unlimited contributors, team members, suggestions and votes. There is no free plan; the trial lasts 30 days with no card.

FeedbackKit's prices, from our pricing page, are in US dollars:

The scaling works differently. With Feature Upvote, three games on Indie billed monthly come to three boards at $59, or $177 a month, with the whole team included. With FeedbackKit, three apps need Team at $39 a month, and team members are on Team alone. Neither price grows with the number of people who vote.

So which one

Choose Feature Upvote if your players or customers reach you on the web or through a community such as Discord, and a public board they can vote on without an account suits them. Choose it if you want custom statuses, alerts in Discord or Microsoft Teams, Jira or Zendesk links, or a REST API with a webhook and Zapier to reach other tools.

Choose FeedbackKit if your users are in a native iOS, macOS, Android, Flutter or React Native app and you want voting in native screens rather than a web board. Choose it if you want requests ranked by the MRR of the users behind them, a free plan to start on, native admin apps for iPhone, iPad and Mac, or status sync with GitHub, Linear, Notion, ClickUp, Monday.com, Trello, Airtable, Asana or Basecamp.

For more options, see our round-up of feature request tools. To put FeedbackKit in a test build, start free.