Skip to content
FeedFast
Get started

Feedback

A roadmap you didn't have to guess at.

Feature requests arrive in five places (email, a support chat, a DM, a call, your own head) and none of them tell you how many other people want the same thing. A public board with votes does, and it does it without asking anyone to make an account.
Start freeSee a live board
Scroll the stack. These are live posts from the demo board.

Why people actually post

Every extra step halves the submissions

Most feedback tools are empty because using them costs the user more than the request is worth to them.
  • No account, no login, no password: a title and a category is enough
  • Email is optional, and only used to let a vote follow someone between devices
  • Anonymous votes are keyed to a hash, never a stored IP address
  • A honeypot field and a per-IP rate limit instead of a captcha
  • Works embedded on your own site, so nobody has to go somewhere else
  • A button on your 404 or 500 opens the form already written: the category chosen, the message started, the page it happened on attached
  • Every filter lives in the URL, so a board view is a link you can send

Structure

It still reads at a hundred posts

One long list stops being useful almost immediately. The board is two-dimensional from the start: categories across, statuses down.

  1. Categories you define

    New projects are seeded with Feature request, Bug and Improvement: rename them, reorder them, give each a colour, or add your own. One is marked default so the submit form is never blank. Free covers three categories; Pro is unlimited.

  2. Five statuses, and a dropdown to move things

    Open, Planned, In progress, Done and Declined. Declined is there on purpose. A clear no with a reason is worth more to the person who asked than silence.

  3. Three sorts, including one for momentum

    Top votes, Newest, and Trending, votes cast in the last seven days, so an old post that just caught fire surfaces instead of staying buried under all-time winners.

  4. Bulk re-categorise when it drifts

    Select posts from the list and move them in one go, because the categories you invent on day one are never quite the ones you need on day sixty.

Closing the loop

The part every other tool leaves to you

Collecting feedback is easy. Telling people what happened to it is the part that decides whether they ever post again.
  • You hear about it the moment it lands. An email with the whole idea in it and a link straight to the reply box, because a request answered the same day is the one that gets posted again. Switch it off per project when the board is busy enough that the weekly digest is the better cadence.
  • Comments with an Owner badge. Your replies are visibly yours, so the board reads as a conversation rather than a suggestion box.
  • Done becomes a changelog entry in a click. Pre-filled with the title, linked back to the request, and tagged from the category: a bug becomes Fixed, a request becomes New.
  • Or one call from your coding agent. The MCP server resolves a post, posts the public reply and publishes the entry in a single step.
  • Empty states per category. “No bugs reported yet: nice.” beats a grey box.

Verified identity, when you want it

Embed the feedback button inside your own app and pass the user’s id or email, and posts arrive attributed automatically. Nobody types their name. Sign the identity with your project secret and it renders with a verified badge, so you can tell an assertion from a fact. Unsigned identities still work; they just don’t get the badge.

Find out what your users actually want

Free for one project, board included. Embed the button in your app and the first request usually arrives the same day.

Start freeSee a live board