Feedback boards with voting
A customer-facing portal where users post requests and vote on the ones they want most.
Compare · Tore vs Canny
Canny tracks what users ask for.Tore also fixes what breaks.
Canny is a strong feedback tool: boards, voting, a roadmap, a changelog and updates when a request moves. Tore keeps a feedback board and roadmap too, and also answers support and takes bugs to a fix for your engineer to approve.
Tore opens soon. Join the waitlist and we'll email you the day you can start.
Same bug, two ways · Acme Corp reports
Example dataWith Cannyfeedback board + roadmap
Priya · Acme Corp · feedbackScheduled reports stopped arriving in my inbox last week.
AI agentAutopilot merged it with a similar request.
Next step: an engineer picks it upoutside the board
With Toresupport + engineering, one thread
Priya · Acme Corp · feedbackScheduled reports stopped arriving in my inbox last week.
Tore AIThanks, Priya. This looks like a bug, not a request. Looking into it now.
Root cause foundreports/schedule.ts:73 · cron skips after DST
Fix written, tests pass+2 −2 · 16 tests
Pull request preppedwaiting for Alex, your engineer
Approved by Alex · Priya told it is fixedsame thread
Where Canny is strong,and when to pick it instead.
Canny is built around one job: collecting feedback, deciding what to build and telling people when it ships. If that is the job, it does it well.
Updates as requests move
Customers get automated updates as their request moves forward, and you announce what shipped in a changelog.
Autopilot finds the requests
Autopilot reads call transcripts, tickets and reviews, pulls out feature requests and merges duplicates.
Linked to your tools
Integrations with Intercom, Zendesk, Slack, Jira, HubSpot, Salesforce and Gong, plus an MCP server.
Pick Canny when
You want a feedback board and roadmap on its own.
- Deciding what to build next is the job you need help with.
- You already run support in a tool you like.
- You want feedback pulled from calls, tickets and reviews automatically.
- Bugs are rare, or your engineers handle them from the tracker.
Tore vs Canny,across the support to fix loop.
Both keep a feedback board and tell people when something ships. The difference is bugs: Tore also answers the report, works in your code and preps the fix.
Tore
- Support inbox: yes
- In-app bug capture: yes
- Starts from your error stream: yes
- Investigates your code: yes
- Opens the pull request: yes
- Feedback board and roadmap: yes
- Tells the reporter it shipped: yes
Canny
- Support inbox: no
- In-app bug capture: no
- Starts from your error stream: no
- Investigates your code: no
- Opens the pull request: no
- Feedback board and roadmap: yes
- Tells the reporter it shipped: yes
| Step | Canny | Tore |
|---|---|---|
| Answers customers | Not part of it | Answers from your help center with the article cited, across email, chat widget and Slack. |
| Hands over to a person | Not part of it | Hands over with the full conversation when it is not confident. Anyone can take over at any moment. |
| Bug capturereplay, console, network | Not part of it | Reports from the chat widget arrive with replay, console and network attached. Bug capture |
| Investigation in your code | Not part of it | Reads the repository you connect and finds the root cause, down to the file and line. |
| Fix and tests | Not part of it | Writes the fix and runs your tests. Your engineer can request changes in plain words. |
| Pull request for approval | Not part of it | Preps the pull request. By default it waits for your engineer's approval. |
| Customers told it is fixed | Automated updates as a request moves forward. | Everyone who reported it is told automatically when the fix is live. |
| Model choice | Autopilot extracts and merges requests. | The right model for each job, from Claude, Codex, Gemini, Grok and more. You can set it per task. |
| Proactive errors | Not part of it | Errors from your error tracker are grouped by fingerprint and can open an investigation before anyone writes in. |
Based on Canny public pages (canny.io), checked 2026-10-30. Products change: if we have something wrong, tell us and we will correct it. For plans and pricing, see Tore pricing.
Desks answer but don't fix.Coding agents fix but never talk.
Most teams keep feedback in one tool, support in another and the code in a third. A request board is great for what to build next, but a broken feature is not a request.
Support desk
Talks to the customer
Intercom, Zendesk and help desks like them. Great at the conversation, then the bug leaves the thread.
- Answers and hands over
- Reads your code
- Writes the fix
Tore
One thread, both sides
The conversation, the investigation and the reply live together, so nothing is retyped.
- Answers and hands over
- Reads your code
- Writes the fix
Coding agent
Works in your code
AI engineers that start from an issue. Strong at the fix, but the customer never hears from them.
- Answers and hands over
- Reads your code
- Writes the fix
Where Canny fits: neither side. It sits next to support as the place for requests and the roadmap, and it closes the loop on those requests well.
Closing the loop
Told it is fixed, for bugs too.
Tore keeps the conversation, the investigation and the fix in one thread. When the fix is live, everyone who reported the bug is told, on the channel they used.
- Repeat reports grouped into one ticket
- Replies drafted from what actually changed
- Anyone on your team can step in at any moment
app.tore.ai/acme/inbox
Example dataFix approved by Alexdeployed to production
Live3 reports linked to this fixchat widget, email and Slack
Priya told it is fixedAcme Corp · same thread
Ticket closed2 more reporters updated
Questions people askbefore switching.
Is Canny better for product feedback?
If feedback and the roadmap are the whole job, Canny is built for it, with Autopilot pulling requests out of calls, tickets and reviews. Tore has a feedback board and roadmap too, next to support and the fix loop.
Can Tore replace our feedback board?
Tore includes a feedback board and roadmap, so requests and bugs live next to the conversations they came from. If you rely on Canny-specific features, compare them side by side before you switch.
Does Tore change our code without asking?
By default it waits for your engineer's approval. Your engineer can request changes in plain words, and Tore revises the fix and re-runs the tests. You set how much it does on its own, per repository, in AI controls.
Which AI models does Tore use?
The right model for each job: a fast model for quick answers, deep reasoning for root causes, a coding model for fixes. You can let Tore choose or set it per task. During early access, you can also bring your own AI keys.
How does the price compare?
Plans, what is included and how the AI is billed are on the pricing page.
Keep comparing.
Track the request.Fix the bug too.
Tore keeps your feedback board, answers support and takes every bug all the way to a fix for your engineer to approve.