Skip to content
Stack0

Find out what your users want built.

Open FeedbackRead the setup guide

Feedback gives your product a public board. Requests arrive from inside your app, your users vote on them, and the roadmap and changelog come off the same board.

The Feedback inbox for Forma: 39 requests sorted by votes, each with its status, tags, comments, and votes.
Any app
One script tag, or POST from your backend. Pylon is not required.
One board, three pages
Requests, the roadmap, and the changelog stay in step because they share a source.
Readable by agents
The public board answers over HTTP with no key, and no private field in the payload.
Included
Covered by the Stack0 subscription. Runs at feedback.stack0.app.

From a request to a shipped change

Each step happens on the board, so nothing is copied between a tracker and a spreadsheet.

Collect from inside your app

A script tag puts a feedback button on your pages. Each request records the page it came from.

The Feedback widget open on Forma's class schedule, listing requests members can vote on.

Catch duplicates as they are typed

Matching requests appear while someone writes a title, so they vote on the one that exists instead of filing a sixth copy.

While a member types a title, the widget lists two matching requests to vote on instead.

Triage with your team

Set a status, tag it, and leave notes your team can read. Internal notes never reach the public board.

A request in the dashboard with its status, board, and tag, two member comments, and an internal team note.

Share the roadmap

Planned, in progress, and completed, drawn from the statuses you already set. Untriaged requests stay off it.

Forma's public roadmap with planned, in-progress, and completed requests and their vote counts.

Publish the changelog

Draft release notes against the requests they close. Publishing notifies everyone who voted.

A draft changelog entry linked to the request it closes.

Let agents and your backend use it

Connect Claude Code through the Stack0 MCP server, or give your backend a project API key. Both read requests and post, vote, or comment for your users.

The project's API settings: keys and the HTTP endpoints an agent or backend can call.

What the board holds

One board per product, with the surfaces the screenshots above come from.

  • Requests and boards

    Separate boards for features and bugs, each with its own posting rules.

  • Votes

    One vote per person, from an account or a guest session. No sign-up wall to read.

  • Merge duplicates

    Fold a copy into the real request. Votes combine, and the old link still resolves.

  • Roadmap

    Planned, in progress, and completed, in vote order, on a public page.

  • Changelog

    Drafts your team can see, published entries linked to the requests they close.

  • Internal notes

    Comments marked internal stay with your team and never enter a public payload.

  • Notifications

    Voters follow a request and hear when its status changes or it ships.

  • Agent access

    A guide at /llms.txt, public reads over HTTP, and submissions on a user's behalf.

Part of the suite

Feedback holds what users asked for; the rest of Stack0 acts on it.

  1. 01

    Add the script tag to an app from Build, a Pylon project on Cloud, or any site you already run.

  2. 02

    Ask an Agent what the top requests are. It reads the same board your users do.

  3. 03

    One subscription covers it, alongside Build, Cloud, Agents, Analytics, and the APIs.

Open FeedbackRead the setup guide

Put your roadmap where your users can vote on it

Create a board, add one script tag, and the first requests arrive the same day.

Open Feedback