Know when it is ready.
One button on every page. One inbox for everything you ship. A clean-days counter that tells you when a release has earned its launch.
Start free See how the gate works
One script tag. Under 8 KB. Hosted in the EU.
You find a bug on your phone, in a queue, between two meetings. You mean to write it down. You don't. The next day looks clean, and the day after that. A find that is never captured becomes a clean day that was not one. Findings exists so that capture takes one tap and one sentence, from wherever you are.
The gate
Every product gets two numbers from real use: clean days since the last real defect, and find rate over 7 and 14 days. Ideas never count against you. Reports you discard never count against you. When nothing has been recorded, it says no data, never an encouraging zero.
One inbox for everything you ship
Run four side projects, or ten? Each gets the same button and its own counter. You triage all of them in one place. No per-project pricing that punishes you for shipping more.
An agent that proposes, never decides
Connect your coding agent over MCP. It reads graded defects on its own product and records the pull request it opened. It cannot deploy, merge, close a find, touch an idea, or work on a serious defect until you allow it. It cannot move a gate number either.
How it works
- Add a site. Name, allowed origins. You get one line:
<script src="https://findings.yindor.com/f.js" data-site="your-site" defer></script>
- Paste it before
</body>. Any stack. No framework, no dependencies. - Tap the pill. Write one sentence. Save. That is the whole capture.
Who sees what
| Visitor | Tester | You | |
|---|---|---|---|
| Sees | One button: Report | The fast path | Everything, on every site you own |
| Writes | One sentence, optional email | Defect or idea, severity S1 to S4 | Triage, grading, settings |
| Moves the gate | Never, until you file it as a defect | Yes | Yes |
Your product says who is signed in. Findings decides the role. Nobody configures a browser. A tester is a person in one of your test groups. The visitor button is off until you switch it on.
What it will not do
This list is part of the product.
- No screenshots. They capture your users' data.
- No session replay. We do not record anyone.
- No page content. A find carries the path, the viewport, the browser and the build. Nothing else.
- No lost finds. No signal on a plane? The find waits on the device and sends itself later. A find the service refuses is shown to you, never dropped.
- No agent with the keys. It proposes. You decide.
Pricing
Free
- Unlimited sites
- You plus 3 testers
- The gate, the inbox and triage
- The offline queue
- The API
Early access
Free until Pro opens
- The visitor button on public sites
- The MCP agent endpoint
Pro, coming
Visitor reports and the agent will move to Pro. Tell us what that is worth to you and we will set the price from your answers, not from a competitor's page.
Questions
Is this another bug tracker?
No. It is the capture and the counter. Keep your tracker. Findings tells you whether the thing you are about to launch is ready.
Why no screenshots?
Because a screenshot of your app is a screenshot of your user. One sentence and the page path is enough to find almost everything.
What counts as a clean day?
A calendar day with no real defect found on that product. Ideas, untriaged visitor reports and discarded reports do not count. The day a find happened counts, not the day it was typed in.
Where is my data?
In the EU, in Helsinki. One database, backed up daily.
Does it work offline?
Yes. A find you cannot send waits on the device and sends itself when you are back online.
Which agents work?
Anything that speaks MCP over Streamable HTTP: Claude Code, Cursor and others. One agent token per product.
Who makes it?
YINDOR, a small software company in Eindhoven. Findings runs on every YINDOR product today.