Hear every user. Close every loop.
A feedback board, public roadmap and changelog in one place. Users post and vote, your AI agent triages, and everyone who asked hears back when it ships.

Run it through the agent you already use.
An MCP server and an HTTP API ship with it. Connect Claude Code, Cursor or Codex from the API keys page, then triage feedback, update the roadmap and draft the changelog from where you already work.
- Ask in plain English
- “What are the five most-voted requests that are still open?”
- Act, not just read
- Move a post to Planned, merge duplicates, reply to a voter.
- Draft the changelog
- Closed posts become a ready-to-edit entry. Followers get an email on publish.
- Your keys, your scope
- One key reaches every workspace you administer, or limit it to one. Hashed, shown once, revoke any time.
● I'll pull this week's shipped posts, draft an entry and show it before publishing.└ hearloop.list_posts status=shipped sort=new → 4 posts└ hearloop.draft_changelog → draft ready, 3 linked posts● Draft: “Dark mode for the widget, merge without losing votes, Slack status alerts.”└ hearloop.publish_changelog → published, 128 followers emailed● Done. Live at acme.hearloop.app/changelog/this-weekPost. Vote. Ship. Tell them.
Four screens. Each one does its job and stays out of the way.
A board users actually use.
Post, vote, comment. Duplicates merge without losing votes. Keyboard first, one accent colour, no clutter.
- Several boards, posts held for approval if you want
- One vote per user, anonymous voting optional
- Tags, search, trending and top sorts

A roadmap that stays honest.
Statuses are data. Drag a card in the dashboard and the public roadmap, the board and the changelog all agree.
- Columns come from your statuses
- Vote counts on every card
- Hide it until you are ready

Close the loop.
Write what shipped, link the posts, publish. People who voted or commented get an email. RSS for the rest.
- Entries link back to the requests
- Followers emailed on publish
- RSS feed, version tags, drafts

An inbox, not a CRM.
Every post in one list with status, board, tags and votes. Filter, pin, merge, add an internal note, move on.
- Quick filters by status, board and tag
- Internal notes and reactions
- CSV import and export

Put the board inside your app.
A widget for feedback, the roadmap and what's new, plus a help center that answers questions before they become posts.
Feedback without leaving your product.
Users vote, post and read the changelog from a panel in the corner. A dot on the launcher tells them something new shipped.
- One script tag, about 6 KB, works on any site
- Theme, accent, launcher, position, corners and tabs
- Limit it to your own sites, sign-in tokens expire in 12 hours

Answer it once.
Write guides in markdown and publish them at /help.
- Collections with icons, search, popular and related
- Readers mark an article helpful or not
- Matching articles show up before someone posts
The export button is cut off on small screens, see the second one.
Show, don't describe.
Screenshots on posts and comments, from the board or the dashboard.
- Paste, drop or pick up to four images
- PNG, JPEG, GIF or WebP, 5 MB each
- Click any image to open it full size
Small tool. Whole loop.
Four things a feedback board has to get right. Nothing else.
Votes that rank the inbox
One vote per user, no anonymous pile-ons unless you allow it. The board sorts itself.
Three shipped requests, 268 votes between them. Linked below.
Close the loop
Publish what shipped, link the posts, and the people who asked get an email. That is the whole point.
A roadmap that stays honest
Statuses are data. Drag a card and the board, the roadmap and the changelog agree.
└ hearloop.list_posts sort=top status=open● 1. Dark mode for the widget · 128● 2. Merge duplicates · 86● 3. GitHub issue sync · 47Ask it from Claude or Cursor
API keys, an HTTP API and an MCP server. Your agent reads the top requests before you plan a sprint.
Feedback tools go quiet after collection.
A user writes an idea, it lands in a dashboard, and that is the last they hear. hearloop treats every post as the start of a loop, not the end of one.
Post, vote or comment and you follow the request. When it moves to Planned, you get an email. When it ships, you get the changelog entry that says so, with your request linked. One click unsubscribes.
Status emails are on by default for verified accounts. Turn the board on and the loop runs the same day.
Post
Whoever posts follows the request from the first minute.
Vote
Voting or commenting follows it too. Status changes reach all of them.
Ship
The changelog entry links the request. Followers get the email.
Return
Changelog subscribers and the RSS feed hear about every release.
It tells people, so you don't have to.
Your team hears about new posts. Your users hear when their idea moves.
Dark mode for the embedded widget
Status changed · by Mara Lindqvist · Planned → In progress · 128 votes
x-hearloop-signature: t=1767225600,v1=9f2c…Alerts in Slack and Discord
New posts, comments, status changes and changelog entries, filtered by board. Or a signed webhook to anything else.
An update from Acme on a post you follow
Dark mode for the embedded widget
Emails when an idea moves
Verified accounts that voted, commented or posted hear when the idea changes status and when it ships. Every email has a one-click unsubscribe.
Your brand, from your website
Paste your homepage. hearloop reads its logo, name, colours and font, and applies the ones you tick.
Free while we are in early access.
Every feature, unlimited users and votes. Paid plans are coming soon, and a free plan stays.
Join now and keep your board. Early users hear about pricing first, before anything changes.
Start for freeFrequently asked, plainly answered.
Anything else, ask us from the feedback board.