Dibbayajyoti

Klinder-OSS - Watch a screen recording of every bug your users hit

by
Most tools tell you a user churned. Klinder shows you why. When someone hits a bug (a JS error or failed API call), it auto-saves a screen recording of what they did and drops you at the moment it broke, stack trace next to the video. No more "it's broken" tickets you can't reproduce. It also does event tracking, a customer timeline, and lifecycle emails, replacing your analytics, replay, and email stack. $9/mo flat, or free self-hosted.

Add a comment

Replies

Best
Dibbayajyoti
Maker
📌
Hey Product Hunt 👋 I built Klinder because of one moment that kept repeating: a user emails "it's broken," I open the app, and it works fine for me. No repro, no stack trace, no idea what they actually did. I'd lose an afternoon guessing. PostHog and LogRocket solve this, but they're a separate vendor, a separate bill, and the "watch the bug happen" workflow is something you wire up yourself. So I made the recording trigger itself. Every session buffers quietly in the browser, and the moment someone hits a JS error or a failing API call, Klinder uploads the recording — including the seconds before it broke — and drops you ~2 seconds before the error, with the stack trace and failing request next to the video. It even groups recordings by error, so you can see how many users hit the same bug, and you can share any recording with a public link straight into a GitHub issue. Then I figured: if I'm already tracking everything, the events, the customer timeline, and the lifecycle emails might as well live in the same place. So they do. It's $9/mo flat, or free if you self-host on your own Postgres. Would genuinely love feedback — especially: what would make you trust this enough to put it on a real production app? What's missing?