Customer support decision
WishKit
A technical user should self-host the project's repo rather than pay; the core product is small and reproducible and the vendor repo is available to use as a starting point.
Visit website↗$15/mo
$180/yr
Read off the official pricing page.
$20one-off6 h to build
$25/mo3 h/mo upkeep
On cash alone, building overtakes the subscription at 2 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All WishKit alternatives, with the arithmetic →
What a replacement has to do
- Collect in-app feedback, allow voting and comments, moderate and prioritize requests, notify users of status changes.
What it still won’t have
- Hosted uptime, scaling, and managed backups
- Vendor support & SLAs
- Any proprietary analytics or enterprise-only features offered by the vendor
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 2 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted WishKit replacement: backend in Node.js + Express with Postgres storing projects, feature requests, votes, comments, and user segments; a React admin dashboard (login via simple JWT) to approve/tag/prioritize requests; an iOS integration example showing how to call the API and present an in-app feedback list; deliver email notifications for status changes via SendGrid; include Dockerfiles and a docker-compose for local dev and a simple deployment guide to a $5–$20/mo VPS. Out of scope: multi-tenant enterprise billing, analytics beyond basic counts. Include error handling, input validation, and basic unit/integration tests for API endpoints.
How we checked
How the score was reached
- Self-host verdict base92
- An open-source build was found+5
- 4 cited sources+3
- Price verified on pricing page+3
- 1/1 assessment runs agreed+4
- Evidence score99
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productWishKit — official site
- official pricingWishKit — pricing (homepage)
- open sourceopf/openproject
- open sourcegitlabhq/gitlabhq
Integrity checks
What held up, and what did not.
