One button on every page. One inbox. One release gate.
Findings is one script tag. It puts a report button on every page of every product you run, and every find lands in one inbox. It also keeps the number that decides a release: the days since the last real defect.
Not for sale. This runs on one person's products and it is built in the open as a portfolio piece.
How it works
- Paste one tag.
<script src="/f.js" data-site="pelgrim" defer></script>3.6 KB over the wire, no dependencies, no framework, no build step on your side. - People report. A visitor sees one button and one required field. A tester sees the fast path: defect or idea, S1 to S4, details prefilled. Capture takes under 15 seconds, which is the only reason it happens at all.
- You triage from your phone. One inbox across every product. File a visitor's find as a defect, grade it, close it.
The gate is the point
Every other tool in this market collects bugs. This one answers the question that collecting them is for: is the product ready to ship?
The gate is seven consecutive days of normal use without finding a defect. So the instrument reports four things: clean days, the find rate over 7 and 14 days, open defects, and ideas counted beside the gate rather than inside it.
That last one is the rule that took two rewrites to get right. An idea is "I missed this functionality, nothing is broken". It stores no severity and it never touches a gate number. If it counted, logging one would reset the clean run and lift the find rate, so the instrument would report a product getting worse at the exact moment its owner was working on it most carefully.
A visitor's find arrives untriaged and is also outside every number until an admin files it as a defect. A stranger cannot move your release date.
What runs today
The snippet
3.6 KB gzipped. Three roles answered by the server, never by the page. Hold the pill 400 ms and drag it along the bottom edge; it remembers the corner per site. A find typed with no network waits in local storage and sends itself when you reconnect, because the plane is the normal case.
The service
PHP and MariaDB, one inbox, one database. Site keys for server-to-server clients, per-site reporter tokens for people, an origin allow list per site, and a rate limit on the visitor button.
The desk
Add a site from a phone, copy the snippet, read the gate card, triage the list. Filters are links, so a view is a URL you can bookmark.
The agent hook
An hourly agent may read open graded defects, attempt a fix on a branch and open a pull request. It may not deploy, merge, close a find or touch a gate number. A bad hour costs one pull request.
Roadmap
| What | Status |
|---|---|
| The service: finds, roles, tokens, gate numbers, health | shipped |
| The snippet and the pill, with the offline queue | shipped |
| Accounts, the site overview and triage from a phone | shipped |
| Moving an existing product's finds in, with the numbers compared field by field | building |
| A generated desk in the vault, and every open S1 or S2 as an action line in the morning brief | building |
| An MCP endpoint so a coding agent can fetch a find and propose a fix | building |
| A Chrome extension that captures a find on any page, with a denylist for employer domains | later |
| A public roadmap page derived from the ideas people file | later |
| A WordPress plugin, which is a wrapper around the same tag | later |
What it will not do
Screenshot annotation, session replay and live chat are each a week of work and none of them moves the gate. A screenshot can also hold a customer's data, so if it ever ships it will be opt-in per find and stored with a retention date.
Where this sits
Prices as listed in September 2026, for orientation rather than as a comparison anybody should buy on.
| Tool | Price | What it is for |
|---|---|---|
| Marker.io | USD 59 a month | Annotated screenshots into Jira and Linear |
| BugHerd | USD 50 a month | Pin a comment to an element on a page |
| Userback | USD 7 a seat | Feedback widgets and a public roadmap |
| Gleap | USD 149 a month | Feedback, chat and a help centre in one |
| FasterFixes | Open source, AGPL | The same MCP shape for coding agents |
| Findings | Not for sale | The release gate, with the defect and idea split |
Every tool above has screenshot annotation, console capture and issue-tracker sync. None of them sells the gate, which is the reason this exists at all.