UserFeedChat
Feedchat is an open-source Web Component that captures user feedback — sentiment, message, images and page context — and hands it to your app as a single typed
If you already have somewhere to send feedback events, Feedchat is close to zero-risk: MIT licensed, dependency-free, no monthly bill, and no hosted infrastructure touching your users' data. The typed feedchat:submit payload with File-object images and automatic page context (URL, title, user agent, ISO timestamp, viewport) is more than most free widgets hand you. The catch is that the widget stops exactly where hosted tools begin — no dashboard, no AI summarization, no triage. Compare it to hosted feedback SaaS like Canny or Featurebase, which charge monthly precisely for the inbox and reporting layer you'll be building yourself. Budget an afternoon for the event handler before you commit.
Verified 6d ago · liveness 61/100 · cite: rightaichoice.com/tools/userfeedchat
- Developers who want a self-contained feedback widget and full ownership of the data flow
- Product teams that already run a backend, analytics pipeline, or webhook to receive events
- Sites needing lightweight sentiment plus image feedback without a monthly SaaS bill
- Open-source projects that want a permissively licensed capture component they can fork
- Non-technical teams expecting a hosted dashboard, inbox, or reporting out of the box
- Buyers who need AI summarization, auto-tagging, or sentiment analytics built in
- Teams wanting plug-and-play install with zero code — you must write the event handler
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Feedchat if you want a hosted inbox with AI summarization, tagging, and reporting the moment feedback arrives — the widget stops at the browser event, and everything after capture is code you write.
The package is free but not the whole cost: you still pay for the endpoint, storage, and reviewer time to do anything with the submissions.
Feedchat is MIT-licensed at $0 — no tier, no seat count, no usage meter. That undercuts every hosted feedback SaaS, which typically charges monthly per seat or per response for the dashboard, routing and reporting Feedchat leaves you to build. It lands best for teams that already pay for an API or analytics stack; teams with no backend are effectively trading the subscription for engineering time, which is the more expensive side of the deal.
In short
UserFeedChat — Feedchat is an open-source Web Component that captures user feedback — sentiment, message, images and page context — and hands it to your app as a single typed. Best for Developers who want a self-contained feedback widget and full ownership of the data flow, Product teams that already run a backend, analytics pipeline, or webhook to receive events, Sites needing lightweight sentiment plus image feedback without a monthly SaaS bill. Free to use.
What people actually say about UserFeedChat — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
6 mentions across 1 source (Product Hunt) · researched Sep 23, 2026.
Weighted by the 6 posts each of 1 source contributed.
- +Framework-agnostic Web Component drops into React, Vue, Svelte, or plain HTML with no wrapper needed
- +Zero backend, zero accounts, MIT license — no lock-in and no recurring fees
- +Sentiment picker (sad/neutral/happy) plus enforced validation yields structured, usable feedback
- +Images delivered as File objects, not base64, keeps payloads lean and serializable
- +Automatic context capture — URL, title, user agent, viewport, timestamp — included by default
- −No AI summarization, clustering, or adaptive follow-ups despite the 'AI user researcher' tagline
- −No dashboard, analytics, or routing — every team must build its own ingest and storage
- −Directly competes with Canny/Delighted on capture while offering none of their workflow features
- −Zero cross-platform community signal beyond one Product Hunt thread — no real scale evidence
- −Commenters questioned whether follow-up questions adapt to responses, and no clear answer surfaced
- • You must build and host your own ingest endpoint, storage, and error handling
- • Engineering time to add analytics, dashboards, or AI summarization that competitors include
- • Ongoing maintenance if you fork the widget for brand-specific behavior
Viability Score
How well maintained and how widely used is UserFeedChat? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- Framework-agnostic <feedchat-widget> Web Component for React, Vue, Svelte, or plain HTML
- Sentiment selector with sad, neutral, or happy
- Message composer that emits trimmed text
- Image attachments delivered as File objects, not base64
- Automatic context capture: page URL, title, user agent, ISO timestamp, viewport dimensions
- Typed feedchat:submit browser event with a structured detail payload
- user-id and app-version element attributes mirrored into submit meta
- Any data-* attribute mirrored into submit meta (e.g. data-plan="pro")
- Submit validation — disabled until sentiment plus a non-empty message or an image
- Label attribute to set the launcher button text (default: Feedback)
- CSS variable theming: accent, surface, panel, border, text, muted, font
- Launcher button styling: background, hover background, color, radius
- Zero backend — no database, API, accounts, or hosted infrastructure
- Install via npm install feedchat or pnpm add feedchat
- Dependency-free package under the MIT license
About UserFeedChat
Feedchat is a framework-agnostic feedback widget shipped as a Web Component. You drop <feedchat-widget> into any front end that renders custom elements — React, Vue, Svelte, or a plain HTML page — and your app listens for a typed feedchat:submit browser event carrying everything the user typed, picked, or attached. Install with npm install feedchat or pnpm add feedchat, import the module, and wire up an event handler. A submission includes a required sentiment (sad, neutral, or happy), a trimmed message, image attachments delivered as File objects rather than base64, and automatic page context: URL, title, user agent, ISO timestamp, and viewport width and height. Element attributes feed the meta payload — user-id, app-version, and any data-* attribute you add — so you can tag a submission with a plan tier or customer ID without extra wiring. The submit control stays disabled until a sentiment is chosen and there is either a non-empty message or at least one image. Theming runs through CSS custom properties set on the element itself: --feedchat-accent, --feedchat-surface, --feedchat-panel, --feedchat-border, --feedchat-text, --feedchat-muted, and --feedchat-font, plus launcher controls for background, hover background, color and radius. The package is dependency-free and MIT licensed, and a local demo runs with pnpm install && pnpm dev. What you do not get is a dashboard. There is no analytics view, no AI summarization, no routing, no inbox, and no hosted infrastructure in the loop — no database, no API accounts, no vendor servers. You write the event handler and decide whether submissions land in your own API, an analytics tool, or an email webhook. Against hosted feedback SaaS, Feedchat trades turnkey reporting for zero infrastructure cost and full data ownership.
Behind the Verdict
Feedchat solves a narrow problem well: getting structured feedback out of your UI and into infrastructure you already own. The element listens for attributes — label, user-id, app-version, and any data-* — and mirrors them into the submit meta payload, so tagging a submission with data-plan="pro" or a customer ID takes one HTML attribute rather than a look-up call. The event detail is fully typed: message (trimmed), sentiment (sad | neutral | happy), images as File[] so you can POST them straight to your own storage, context with url, title, userAgent, timestamp and viewport, and the optional meta record. Validation is handled for you. Submit stays disabled until a sentiment is picked and there is a non-empty message or at least one image, which removes the most common source of junk submissions. Theming is genuinely yours to control. CSS custom properties cover accent, surface, panel, border, text, muted and font, plus launcher background, hover background, color and radius — the README demos a teal accent (--feedchat-accent: #0c6e6b) with a pill-radius launcher (--feedchat-launcher-radius: 999px), so brand-matching doesn't require forking internals. Where it falls short is everything after capture. There is no inbox, no analytics, no summarization, no routing or notification logic — the vendor handles none of that by design, and the repository's documentation is essentially the README. The repo itself is small and young (a handful of stars and commits), so treat it as a component you own rather than a product with a roadmap. For a team without an existing event endpoint, the "free" widget becomes a build project: storage, dedupe, review UI, and someone to read it. For a team that already runs an API or webhook, that same work is a few lines. That split is the entire decision.
Researching UserFeedChat? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas UserFeedChat actually fits — and what changes day-one when you adopt it.
Installs feedchat with npm install feedchat, drops <feedchat-widget label="Send feedback" user-id="u_123" data-plan="pro"> into the app shell, and adds a feedchat:submit listener that POSTs event.detail to an existing /feedback endpoint.
Outcome: Feedback starts flowing the same afternoon, with sentiment, page context and screenshots attached and no new vendor account or monthly cost.
Ships the widget on the cancellation page and routes the typed submit event into the warehouse alongside plan and account data already tagged via data-* attributes.
Outcome: Churn feedback is queryable next to usage data, so exit reasons can be sliced by plan tier instead of living in a separate tool's inbox.
Forks the MIT-licensed component, restyles the panel via --feedchat-accent and --feedchat-launcher-radius to match the project, and points the submit event at a GitHub issue webhook.
Outcome: Users get a branded in-page report button, and reports land as issues with URL and user agent already attached, cutting back-and-forth to reproduce.
Use Cases
- Capture bug reports with page URL, user agent and viewport attached automatically
- Collect feature requests tagged by sentiment so you can sort enthusiasm from frustration
- Interview users during a cancellation flow to understand churn reasons
- Attach screenshots as File objects and POST them straight to your own storage
- Tag submissions with data-plan or data-customer-id and route them in your own pipeline
Limitations
- Feedchat requires self-hosting: there is no hosted backend, database, or API, so the npm/pnpm package is the whole product and you supply the receiving endpoint.
- It captures feedback but does nothing after that — no dashboard, analytics, AI summarization, tagging, routing, or notifications.
- Documented guidance is limited to the README and the repository's code.
- Submissions are tied to whatever transport you build, so reliability, retries and storage are your responsibility.
- The project is early and small (a handful of stars and commits), so treat it as a component you own rather than a maintained product.
- Compliance guarantees such as SOC 2 or HIPAA are not offered by the vendor.
as of 2026-10-02
Verification history
We have re-verified UserFeedChat 6 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published UserFeedChat tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0/mo
Ideal for
Developers and product teams with an existing API, webhook, or analytics pipeline who want feedback capture without a subscription.
What this tier adds
Free entry point — MIT-licensed npm package at $0, with the whole product being the widget and its typed event; no paid tier exists.
Where the pricing makes sense
The company stage and team size where UserFeedChat's pricing actually pencils out — and where peers do it cheaper.
Feedchat is MIT-licensed at $0 — no tier, no seat count, no usage meter. That undercuts every hosted feedback SaaS, which typically charges monthly per seat or per response for the dashboard, routing and reporting Feedchat leaves you to build. It lands best for teams that already pay for an API or analytics stack; teams with no backend are effectively trading the subscription for engineering time, which is the more expensive side of the deal.
Setup time & first value
How long it actually takes to get something useful out of UserFeedChat — broken out by persona, not the marketing-page minute.
For a developer with an existing endpoint: roughly 15-30 minutes — install the package, add the custom element, and write the feedchat:submit handler. For a team with no receiving backend, expect half a day to a few days, since storage, dedupe and a way to actually read the submissions are all yours to build. Custom theming via the CSS variables adds another short pass.
Switching to or from UserFeedChat
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From a hosted feedback SaaS (e.g. Canny): export past submissions, replace the hosted widget with <feedchat-widget>, and point the submit handler at the endpoint that now owns the data.
- →From a hand-rolled feedback form: swap the form for the custom element and map your existing handler onto the typed feedchat:submit detail payload.
- →From Intercom or a chat widget's feedback form: keep the messenger, add Feedchat for the structured sentiment-plus-image capture and route both into one store.
- ↗To a hosted feedback platform (e.g. Canny or Featurebase): remove the custom element, re-embed the hosted widget, and import the submissions you stored from Feedchat events.
- ↗To a survey tool (e.g. Typeform): rebuild the question flow as a survey and retire the in-app widget if you need response analytics more than in-context capture.
- ↗To a support desk (e.g. Zendesk): route the feedchat:submit handler into ticket creation instead of a feedback store, so submissions become tickets with attachments.
Resources & Guides
Tutorials & Learning
YouTube returned 6 videos for “UserFeedChat”, and we withheld 6: 6 could not be judged, because “UserFeedChat” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about UserFeedChat.
Official links
Tools that pair well with UserFeedChat
Common stack mates teams adopt alongside UserFeedChat, with the specific reason each pairing earns its keep.
Casper AI
Chrome extension that summarizes web pages, PDFs and news into short notes you can share with your team
MaxAI.me
MaxAI.me puts a multi-model AI sidebar in your browser to summarize, translate, and reply anywhere you type.
Treble.ai
Official WhatsApp Business API platform with AI chatbots, mass campaigns, and native HubSpot/Salesforce sync for LATAM-focused teams.
Featured Head-to-Head Comparisons
Userfeedchat vs Hi Marley
Choose UserFeedChat if you need a free, open-source, AI-powered feedback chatbot for product insights, especially if you can self-host. Choose Hi Marley if you're a P&C insurer looking to digitize claims communication via SMS with industry-specific workflows and integrations. They serve entirely different use cases and aren't direct substitutes.
Userfeedchat vs B Rokratt
Choose UserFeedChat if you need a customizable, open-source chatbot to gather user feedback for a product or service globally. Choose Bürokratt if you are an Estonian citizen or e-resident seeking to interact with government services via a virtual assistant. They serve entirely different needs: product feedback vs. public service access.
Userfeedchat vs Chatlyn
If you're a hospitality business needing an omnichannel AI hub to boost bookings and automate guest communication, Chatlyn is purpose-built. For product teams who want open-source, self-hosted conversational feedback to replace surveys, UserFeedChat is a free, powerful choice. Choose based on your industry and need for hosted vs. self-managed deployment.
Alternatives to UserFeedChat
View all
Frequently Asked Questions
Categories
Best-of guides
Used UserFeedChat? Help shape our editorial sentiment research.