A user hits a broken screen after your latest deploy.
They send a short note from that page. You get the URL, browser, device, and optional screenshot automatically.
Find what users need.Show what you fixed.
Add one feedback button to your app. Users send a short note without leaving the page, and you receive the page, browser, device, and optional screenshot with it.
Free to startUnder 20KB gzipInstall in under 10 minutes
01 / Install
One copy-paste. Your app is connected.
app/layout.tsxCopied
<div data-feedbacks-host="your-project-key"></div>
<script
src="https://app.feedbacks.dev/widget/latest.js"
data-project="your-project-key"
defer
></script>Widget connected in 2.1s
Install it once. See the first report arrive.
Paste the snippet, send a test from your app, then shape the form from your dashboard - without touching the installed code again.
app/layout.tsxCopied
<div data-feedbacks-host="your-project-key"></div>
<script
src="https://app.feedbacks.dev/widget/latest.js"
data-project="your-project-key"
defer
></script>Widget connectedReady for a test report
Private credentials stay server-sideNo rebuild after customization
See the setup happen
From pasted code to useful feedback in minutes.
See the report. Fix it. Tell the user.
Every report stays connected to its page and technical details. When the fix ships, publish a short update inside the same app.
A user gets stuck
They tell you without leaving your app.
The message comes with the page, browser, rating, and screenshot. Your team sees where the problem happened.
Orbit / Deployment #8421production
BUILD STALLED
Build logs stop updating after the deploy reaches 80%.
/deployments/8421 · Edge 128 Screenshot
One clear path from problem to fix
When a user says “it does not work,” get the details you need.
The user writes a short note. feedbacks.dev adds the page and browser details that make the report useful.
Someone testing your vibe-coded app says, “it does not work.”
Open one report with the screen and technical context attached instead of guessing what happened.
Three customers ask for the same small feature.
Keep their requests together, decide if it is worth building, and reply when it ships.
A client reports a bug in the app you built for them.
Keep that project separate and send the useful report to GitHub, Slack, Discord, or a webhook.
Send important feedback to the tools you already use.
Forward a report to Slack, Discord, GitHub, or a webhook. Use the API or MCP when your coding agent needs the same backlog.
New feedback
Checkout fails after I add a coupon
Safari 18 · /checkout · screenshot added
Send it where work happens
SlackTell the product channel
GitHubOpen an issue
DiscordPost to your server
WebhookSend it anywhere
Choose what gets sent. Check delivery history and replay a failed send from the dashboard.
Let coding agents use the feedback
Connect trusted tools with the API or MCP.
agent list unread bugs for checkout
3 bugs found · only this project · your secret stays private
Give users a public ideas page
They can post, vote, follow, and read your reply.
24Add saved report viewsPlanned
11Faster CSV exportsShipped
Your public project key cannot open your inbox.
The widget uses a browser-safe key. Private API keys are separate, integration secrets are encrypted, and screenshots require an authenticated owner.
Separate key types
Browser-safe publishable keys and scoped private API credentials have different formats and permissions.
Private feedback media
Screenshots are sanitized, stripped of metadata, and served only after an owner check.
Secrets stay server-side
Stored integration tokens are encrypted and returned to the browser only as redacted destination hints.
Minimal install
One lightweight embed, no payment script, and no private credential in customer code.
What you need to know before installing.
Will the widget slow down my app?
The production widget is under 20KB gzip, loads asynchronously, and is guarded by a CI size budget.
What data is collected automatically?
The current page URL and browser context can accompany feedback. Screenshot capture is optional and visible to the user.
Can a visitor use the project key to read my inbox?
No. The embed key is publishable and is rejected by private REST and MCP endpoints.
How do I handle spam?
Start with project- and board-scoped rate limits. Add CAPTCHA or origin restrictions only when your traffic needs them.
Do I have to reinstall after changing the form?
No. The snippet stays the same; saved form and Product Update changes load remotely.
What happens if I cancel Pro?
Pro stays active through the date you already paid for. We warn you during the final three days, then Free limits return. Your 2 most recently active projects stay live, extra projects are frozen, and nothing is deleted.
Can I leave the Free plan?
Yes. Free includes 2 projects and 500 feedback items per month. Pro adds more capacity, history, routing, scheduling, and branding controls.