Collect feedback from
every project in one place.
Feedex is a lightweight feedback platform for developers who ship more than one thing. Drop a single script into any site, and bugs, feature requests, and UI issues land in a dashboard built for triage — with the browser, viewport, and page already attached.
<script src="https://feedex.rianfernando.com/widget.js"
data-feedex-key="pk_fdx_your_key" defer></script>- 7 kB gzipped
- No dependencies
- Works on any framework
- MIT licensed
Features
Everything you need to close the loop
Feedex does one job properly: getting feedback out of your users' heads and into a list you can work through.
Every project, one inbox
Portfolio, storefront, blog, dashboard, side project. Each gets its own widget and keys, and everything lands in one place you actually check.
Context without asking
Page URL, browser and version, operating system, device, viewport, screen, language, and timezone travel with every report. Reporters type one thing.
Built for triage
Seven categories, five statuses, four priorities. Filter by any of them, and the URL carries the filter so a view is shareable.
A widget that stays out of the way
7 kB gzipped, zero dependencies, rendered in a shadow root. It cannot inherit your styles and cannot leak into them.
Multi-tenant from the first commit
Workspaces own projects, projects own feedback. Every query is workspace-scoped in the service layer, not by convention in the UI.
Keys you can rotate
A public key for the browser and a secret key for your server. Secrets are stored as HMACs and shown exactly once.
How it works
From a bug on someone's screen to a fix on yours
The whole loop, end to end. Step through it, or let it play.
Add one script tag
A single tag on any page. No build step, no framework requirement, no configuration file.
<!-- Anywhere before </body> -->
<script
src="https://feedex.rianfernando.com/widget.js"
data-feedex-key="pk_fdx_9Kd2..."
defer
></script>For developers
An API that behaves itself
Every response uses the same envelope. Errors carry a stable machine-readable code alongside a message you can show a user. Rate limits are returned in headers, not discovered by getting blocked.
- Bearer-token auth with per-project secret keys
- Consistent { data } / { error } envelope on every route
- Rate limit headers on every authenticated response
- Webhooks and integrations designed for, not bolted on
curl https://feedex.rianfernando.com/api/v1/issues \
-H "Authorization: Bearer sk_fdx_..." \
-G -d status=open -d priority=critical
{
"data": {
"items": [
{
"id": "fbk_m4x9k2c1_a83jf0zq",
"reference": 42,
"title": "Export button does nothing",
"category": "bug",
"status": "open",
"priority": "critical",
"context": {
"url": "https://example.com/reports",
"browser": "Chrome",
"viewport": { "width": 1512, "height": 858 }
}
}
],
"pagination": { "page": 1, "total": 1, "totalPages": 1 }
}
}Open source
Free, and built to stay that way
Feedex is MIT licensed and developed in the open. Use the hosted instance or run your own — they are the same application.
Free, with no tier above it
Every feature is in the box. There is no plan to upgrade to, no seat count, and no usage meter counting your feedback.
MIT licensed
Read it, fork it, run it commercially, change whatever you like. The whole application and the widget are in one public repository.
Self-host it
Point it at your own PostgreSQL and deploy it anywhere Node runs. Your feedback stays in a database you control.
No tracking of your users
The widget reads no cookies, writes no storage, and builds no fingerprint. It collects what is needed to reproduce a bug and nothing else.
FAQ
Questions, answered
If something is not covered here, the source is the documentation of last resort.
What is Feedex?
Feedex is a lightweight developer feedback platform. You install a single script on any web application, and the bugs, feature requests, and UI issues your users submit are collected into one central dashboard, with browser and page context attached automatically.
How does Feedex work?
You create a project in your Feedex workspace and get a public key. You add one script tag carrying that key to your site. A feedback button appears in the corner; when a visitor submits a report, it is validated, rate limited, and stored against your project, then appears in your dashboard where you can set a status and priority and work through it.
Is Feedex free?
Yes, entirely. Feedex is MIT licensed, so you can self-host it at no cost with your own PostgreSQL database, and the hosted instance at feedex.rianfernando.com is free to use. There is no paid tier, no seat pricing, and no usage limit on your feedback.
Who is Feedex for?
Developers and small teams who maintain more than one web property and want a single place to collect feedback across all of them, rather than a separate tool or inbox per project.
How do developers integrate Feedex?
Add one script tag with your project public key before the closing body tag. There is no build step, no package to install, and no framework requirement. For React or Next.js you can load the same script through next/script. You can also post feedback directly to the REST API from any client, including mobile apps and command-line tools.
What data does the widget collect?
Page URL and path, referrer, browser name and version, operating system, device class, viewport and screen dimensions, language, and timezone. It does not read cookies, does not write to storage, and does not compute a fingerprint. Email is collected only if the reporter chooses to provide it.
Can I self-host Feedex?
Yes. Feedex is a standard Next.js application backed by PostgreSQL. Set DATABASE_URL and AUTH_SECRET, run the migrations, and deploy it anywhere that runs Node. Local development needs no database at all — it falls back to an embedded PGlite instance.
Does Feedex use AI?
Not in this version. AI-assisted categorisation, duplicate detection, and issue summaries are on the roadmap, but the current release is deliberately a solid, predictable foundation without them.
Put it on one project today
Create a workspace, add a project, paste one script tag. The first piece of feedback usually arrives before you have finished reading the docs.