For indie developers and teams of 1–5

Stop reading app reviews one tab at a time.

Heednest pulls your App Store reviews, support email and GitHub issues into one place (Google Play and Chrome Web Store next). It groups duplicates, flags the bugs that actually matter, opens the GitHub issues, and drafts the replies. You approve with one click.

Join the waitlist See founding pricing

Private beta in early 2027. Reserving a founding seat costs nothing today.

Monday digest · 47 new items → 6 threadsauto-grouped
Sync stops after the iOS 26.1 update
bug12 reportsApp Store ×9 · email ×3
✓ issue #142 opened
Export projects to CSV
feature request7 reportsGoogle Play ×4 · GitHub ×3
Open issue
Does it work offline?
question3 reportsemail ×3
Approve reply
Dark mode is great, thank you
praise23 reportsApp Store ×21 · Chrome ×2
Add to changelog

How it works

Collect, triage, act. In that order, every morning.

1 · Collect

Every channel, one inbox

  • App Store reviews, with replies through App Store Connect
  • Support email (forward to your inbox address)
  • GitHub issues and discussions
  • Hacker News mentions
  • Next: Google Play, Chrome Web Store, Linear
2 · Triage

Grouped, labelled, ranked

  • Duplicates merged into one thread with a count
  • Labelled bug / feature / question / praise
  • Severity scored by how many users and how blocking
  • Trend alerts when a new complaint spikes
3 · Act

Issues, replies, changelog

  • Opens GitHub or Linear issues with the evidence attached
  • Drafts review and email replies in your voice, queued for approval
  • Writes the changelog from issues you closed this week
  • Nothing is published without your click

MCP server included

Ask your coding agent what users are saying.

The same inbox is exposed as an MCP server for Claude Code, Cursor and any MCP client. Triage from the terminal, open issues in the repo you already have open, and let the agent fix the bug while the report is fresh.

// in Claude Code, with the MCP server connected
> What were users complaining about this week?
  Open GitHub issues for the top 3.

Using list_feedback(since="7d", kind="bug")…
  1. Sync stops after iOS 26.1       (12 reports)
  2. Crash when importing large CSV   (5 reports)
  3. Login loop on Safari             (4 reports)

Using create_issue ×3 → #142, #143, #144
Done. Want me to start on #142?

Founding pricing

Reserve a founding seat. Pay nothing until launch.

We are building this with the first 50 founding members. Reserve a seat now, pay when the beta opens, and keep the founding rate below for as long as you stay subscribed.

Indie
$19/month · founding rate

Launch price $29/month · or $149/year

  • 1 app, App Store reviews
  • Support email inbox
  • GitHub issues in and out
  • 500 triaged items / month
  • MCP server access
Team · most popular
$49/month · founding rate

Launch price $79/month · or $390/year

  • 3 apps, every review source we ship
  • GitHub + Linear, up to 5 seats
  • Reply drafts in your voice
  • Weekly changelog generator
  • 2,500 triaged items / month
Lifetime
$299 once · 50 seats only

Team plan, no renewal, 2,500 items / month

  • Everything in Team, for life
  • Direct line to the founder
  • Your feature requests triaged first
  • Refundable any time before you get access

Nothing is charged today. Reserving adds you to the founding list; you get a payment link when the beta opens and can walk away at any point.

Get access

Join the waitlist

Where does your feedback come from today?

One email when we launch, one or two progress notes before that. No spam, unsubscribe any time.

FAQ

Questions we get asked

Is it built yet?

Not yet. We are collecting founding members first to decide which review sources ship first and to fund the store integrations. Reserving a seat costs nothing; when the beta opens you get a payment link, and anything you pay is refundable until the day you get access.

Will it post replies or open issues without asking me?

No. Every reply sits in an approval queue until you click. Opening issues can be set to automatic per label (for example, auto-open bugs with 3+ reports) but it is off by default.

Which sources work at launch?

App Store reviews (public feed, with replies through the App Store Connect API), a forwarding address for support email, GitHub issues, and Hacker News mentions. Google Play, Chrome Web Store and Linear follow based on what founding members ask for. Reddit and X are not planned: their API terms do not allow it at indie prices.

Does it need access to my store developer account?

Reading App Store reviews works from the public feed with no login. To reply from the inbox you add an App Store Connect API key with the narrowest role Apple allows. Google Play will need a service account the same way when it ships.

How is this different from Canny or AppFollow?

Those tools collect and organise. Heednest is built around the next step: opening the issue, drafting the reply, writing the changelog, and doing it from your terminal through MCP. It is also priced for one person, not a product team.

Where does my data go?

Reviews and emails are stored in our database to build threads and counts. Classification runs on a hosted language model with no training on your data. You can delete everything from settings at any time.