FeedbackKit vs Upvoty: In-App Voting or Hosted Boards

Upvoty and FeedbackKit agree on more than most pairs in this series. Both let users post and vote on requests, both can sort those requests by the revenue of the people behind them, and both sync with Linear. The real difference is where the board lives. Upvoty is a hosted web portal with a widget, a public roadmap and a changelog. FeedbackKit is a set of native SDKs that put the board inside your app.

We make FeedbackKit, so read this with that in mind. Every Upvoty fact below comes from Upvoty's own pricing, feature and integration pages, checked on 17 October 2026, and is linked where it is used. The side-by-side table is on our FeedbackKit vs Upvoty compare page, and this post goes into the detail behind it.

The short version

• Upvoty is a web feedback platform: public or private boards, a widget for websites and web apps, a public roadmap on every plan, a changelog from Super, revenue segments from SSO, the API or HubSpot, and Jira and Linear sync. It has no free plan.
• FeedbackKit is in-app feedback and feature voting for app teams, with native screens on Apple platforms, Android, Flutter and React Native, MRR ranking on every plan, and a free plan.
• If your users are on the web and you want a public roadmap and changelog, Upvoty fits well. If your users are in a native app, FeedbackKit fits better.

Getting feedback in

Upvoty: a web widget

Upvoty's feedback widget appears as a floating bubble, a button or a link, on your website or inside your product. Users can file feature requests, bug reports and other feedback, and bug reports can carry screenshots, annotations and console logs. Its llms.txt describes boards with tags, filters, moderation and AI duplicate detection. Upvoty does not list a native iOS, Android, Flutter or React Native SDK. For developers there is an API, webhooks and an MCP server, which the pricing page puts on the Hyper plan.

FeedbackKit: native SDKs

FeedbackKit has SDKs for Swift and SwiftUI (iOS, macOS and visionOS), Kotlin with Jetpack Compose (Android), Flutter and React Native. Each ships ready-made screens: a request list, a submit form, a detail view with comments, and vote buttons, in your app's own UI. The JavaScript SDK is a headless client for the web with no screens. There is also a Vapor SDK for server-side Swift and a REST API, but no outgoing webhooks.

The honest caveat: the Swift SDK needs iOS 26, macOS 26 or visionOS 26 or later, with no watchOS or tvOS. If you support older iOS versions, it is not an option for you yet. Docs: Swift, Kotlin, Flutter, React Native.

For your website, 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 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. 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.

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

Managing feedback

Upvoty's feedback boards page describes public or private boards, comments on each request, statuses that match your workflow, a custom domain and branding, and merging overlapping requests so that votes and comments stay on the main post. Private boards suit internal planning next to an external customer board.

FeedbackKit has six built-in statuses on every plan: Pending, Approved, In Progress, TestFlight, Completed and Rejected. Pro and up choose which ones a project uses; there are no custom statuses. A new request starts with its submitter's vote, voting stops at Completed and Rejected, and merging duplicates counts each voter once. A rejected request can carry a reason. You work from the web dashboard or the native admin apps for iPhone, iPad and Mac. Your team gets email for new requests on every plan, and push for new requests and new comments in the FeedbackKit app. New-comment email to the team needs Pro.

Revenue behind each request

This is where the two are closest. Upvoty's segments page says your backend signs an SSO token with attributes such as plan and MRR, and the API can update them between logins. Upvoty can then add up the MRR or ARR of every voter on a post and sort by it. The HubSpot integration syncs contacts, companies and deals, so each request shows the MRR, plan and open pipeline behind it, and votes from one company can be grouped as one account. On the pricing page, Custom SSO is on Hyper.

FeedbackKit gets the same answer from a different input. Your app passes each user's MRR through the SDK, on every plan, and requests can be sorted by the total MRR of the users behind them. There is no SSO token to sign and no CRM sync to set up for it, which suits apps where revenue comes from in-app subscriptions. Upvoty goes further for B2B sales teams, with pipeline value and company rollups.

Integrations

Upvoty's column is from its integrations page, as of 17 October 2026.

Upvoty says Jira and Linear tickets are created when a feature moves to in progress, and the ticket's status syncs back to Upvoty as engineering works on it. ClickUp, Trello, Asana and Salesforce appear as logos without a description. Upvoty's pages differ on plans: the pricing page lists all integrations on Super and Hyper, while the integrations FAQ says the connectors are in every paid plan, with some plans capping how many are active. Check with Upvoty if an integration decides your plan.

FeedbackKit creates and links tickets in nine trackers with status sync, on Pro and up. GitHub has no comment sync, and GitHub, Linear, Trello and Basecamp have no vote-count sync; the full matrix is on the integrations page. FeedbackKit has no Jira, Azure DevOps, Zapier, Make, Microsoft Teams or Discord integration.

Closing the loop

Upvoty updates users when a post's status changes, and its changelog notifies voters when the feature they asked for is released. Its email digests send scheduled summaries of top votes, status changes and new posts to people you choose, such as sales and customer success.

FeedbackKit closes the loop with status email. The person who submitted a request is emailed on every plan when the new status is on the project's list, which starts as Approved, In Progress, Completed and Rejected. Choosing that list needs Pro, and emailing voters who opted in needs Team. Your app's users get status email, never push. FeedbackKit has no changelog for them. See our post on status emails.

Pricing

From Upvoty's pricing page (shown in dollars) and our pricing page, checked on 17 October 2026. Upvoty's annual prices are per month, billed yearly.

Every Upvoty plan has unlimited boards and tracked users, and a 14-day free trial with no card; yearly billing saves 10%. Upvoty's tiers differ by project count and features, not by how many people vote. FeedbackKit's yearly billing saves about 17%, with no limit on voters. Past the Free cap of 10, new items are saved and left off the board. More in Upvoty pricing and Upvoty alternatives.

So which one

Choose Upvoty if you want a public roadmap and changelog that customers can follow on the web, linked to their votes. Choose it if your engineers use Jira, if your sales team lives in HubSpot and wants pipeline beside each request, or if your team chats in Microsoft Teams or Discord. It is a well-rounded web board at a modest price.

Choose FeedbackKit if your product is a native iOS, macOS, Android, Flutter or React Native app and you want voting and comments in native UI inside it. Choose it if you want MRR ranking on every plan straight from your app, with no SSO token or CRM to wire up, if your team plans in GitHub, Notion, Monday.com, Airtable or Basecamp, or if you would rather start on a free plan than a trial.

Try both with real users. Start free with FeedbackKit, add the SDK to a test build, and compare it with Upvoty's widget side by side.