nowfound

Commerce · alternatives · 2026

24 alternatives to I built a tool that helps fixing JavaScript production bugs much faster

Logging and tools like Sentry are a thing of the past. A while back on a night out in northern Norway, I had to start debugging a critical production bug that broke the payment flow of my SaaS product. I had limited time to fix the bug or I would have lost about ~1K profit. Super stressful. I had logging and Sentry in place, but neither helped me reproduce or find the root cause of the bug. Ever since, I started thinking; why can’t we just have a tool that you setup once, and that allows us to reproduce every function call and function that the user ran before the bug? This is how the idea…

Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes. I built a tool that helps fixing JavaScript production bugs much faster launched in 2023; newer entries below may have overtaken it.

  1. 1AW

    Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. https://jam.dev It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create). It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer…

    2024 · its alternatives →

  2. 2MU

    Most feedback tools are built like people actually want to report bugs. They don’t. Unless you make it dead-simple, or better yet - a little fun. After shipping a few SaaS products, I noticed a pattern: Bugs? Yes. Bug reports? No. Not because users didn’t care but because reporting bugs is usually a terrible experience. Most tools want users to: * Fill out a long form * Enter their email * Describe a bug they barely understand * Maybe sign in or create an account * Then maybe submit it Let’s be real: no one’s doing that. Especially not someone just trying to use your product. So I built…

    2025 · bugdrop.app · its alternatives →

  3. 3
    Owltics▲125

    Report bugs directly from your product

    2024 · owltics.com · its alternatives →

  4. 4

    Hi HN! Thanks for your attention to my post. It was a big challenge to run most of Node.js packages in browser, fast moreover. Virtual File system, resolve import/export. I got cold many times, depressions, burned out, yet still alive and finished it. Many guys helped me with an advice. Many users give a lot of positive feedback. There are 200,000 monthly unique users. I work full time now because of the freemium business model. To be honest - I am happy after many years of hard work.

    2022 · playcode.io · its alternatives →

  5. 5

    Hey everyone, My friend and I built a simple bug fixing app that listens for alerts/issues from Sentry, contextualizes it against your codebase, and any other data sources you wish to connect (right now we support Notion, Google Docs, and Slack), and deploys an ai agent to write a PR for review in Github or Gitlab to solve the bug. Our current demo shows the end-to-end process for a trivial bug fix, but we have been testing it with open source python repos like http-pie, comparing how our agent solves a bug compared to a human engineer and it gets fairly close. We are working on adding…

    2023 · resolvd.ai · its alternatives →

  6. 6
    Sentry▲265

    Stop hoping your users will report errors

    2018 · sentry.io · its alternatives →

  7. 7

    Hey HN, bugstack started life as an internal tool for my other startup Fuelscout because my customers would encounter production bugs when I was away that would ruin their experience. When I went camping and came home to find out my internal tool had fixed an error and shipped it to production I knew it was bigger than Fuelscout, so my little tool became bugstack. bugstack monitors your production errors 24/7. When a user hits a bug, bugstack captures the error, pulls context from your repo, generates a minimal surgical code fix, runs it through CI, and delivers it as a pull request. If…

    Mar 2026 · bugstack.ai · its alternatives →

  8. 8

    Hi all, I've been working on this devtool for 1 month now for myself at first and I'll be curious to see if it's something that could work for you as well. So basically, it detects bugs in your website in production from real user sessions, an llm clusters them by severity and it provides the complete context of the issue that you can copy-paste into your coding agent to fix it in one go. Why did I create it? I've been shipping fast with tools like Cursor and Claude Code. The problem? When bugs happen in production, these tools have zero context about what actually went wrong. Sentry is…

    Nov 2025 · sonarly.dev · its alternatives →

  9. 9

    Faster user-land reimplementations for several common builtin native JavaScript functions. - codemix/fast.js

    2014 · github.com · its alternatives →

  10. 10
    Sentry▲171

    Real-time crash reporting for the web and apps

    2015 · sentry.io · its alternatives →

  11. 11

    The fastest and most detailed tool for fixing bugs

    2023 · useflytrap.com · its alternatives →

  12. 12
    FlowLens▲134

    Hi HN, We often run into this with coding agents like Claude Code: debugging turns into copy-pasting logs, writing long explanations, and sharing screenshots. FlowLens is an MCP server plus a Chrome extension that captures browser context (video, console, network, user actions, storage) and makes it available to MCP-compatible agents like Claude Code. You can try it here: https://magentic.ai/flowlens Any feedback—good, bad, or brutal—is welcome.

    Dec 2025 · magentic.ai · its alternatives →

  13. 13

    Report bugs faster. Now with voice and camera recording

    2020 · birdeatsbug.com · its alternatives →

  14. 14

    Hey HN, I’m a product designer on a payments team. Every time we were close to shipping a feature, we’d run a bug bash in a giant Google doc or spreadsheet: copy the spec in, write the test cases, ask people to mark Pass/Fail, paste screenshots, then manually turn everything into Jira tickets. It worked, but it always felt a bit painful. Instead of another heavy test management tool, I wanted something that feels closer to the tools we actually like using. More Linear/Notion, less old-school QA. With Preflight, you paste your product requirements and Figma link and get an initial…

    Dec 2025 · preflightqa.xyz · its alternatives →

  15. 15PE

    Hi HN, I think it's safe to say that the majority of developers don't give a second thought to writing code with I/O tangled in business logic. It's all too common to see code like: const user = findUser(email); if (!user) await saveUser(user); Now, you may ask: what's the big deal? When we write code like this, two things happen: 1. It gets harder to debug production bugs. Unless you have the exact same database and remote API services to connect to, you may fail to reproduce the bug. 2. You have to use mocks and fakes in your tests, or use test containers, which only help somewhat,…

    Jun 2026 · pure-effect.org · its alternatives →

  16. 16
    Djaty▲55

    Bug reporting tool for web applications

    2021 · djaty.com · its alternatives →

  17. 17

    First single-stepping debugger with everything you wanted

    2023 · sentio.xyz · its alternatives →

  18. 18

    Hi HN, my team and I have been working on a new tool to improve how bugs are reported to engineers. I used to be a developer, and I thought it was ridiculous the little amount of bug repro details I would get in JIRA tickets. Then I became a product manager, and I realized how time consuming and tedious it was to write good tickets for developers (and then understood why most tickets lack enough detail!) That’s why my team and I decided to build a browser extension for anyone to create bug reports that auto-include: console logs, network requests, session replay, timestamp, url, browser, OS…

    2022 · jam.dev · its alternatives →

  19. 19

    Hey HN! I’m Rasmus, co-founder of Flytrap. Flytrap is a debugging tool for reproducing and fixing production bugs faster. When launching a product quickly, there is bound to be some bugs. Tools like Sentry might help combat this, but when a bug lands in Sentry, all you see is the Red Carpet of Doom (the stack trace). We were frustrated with the poor developer-experience of current debugging tools, and decided to build Flytrap; a fast debugging tool that quickly allows developers to understand in detail what happened leading up to a bug, and focuses on reproducibility in the developer…

    2023 · useflytrap.com · its alternatives →

  20. 20

    I built FixBugs, an agent that ingests the rich context surrounding production bugs to reproduce them in a sandbox and generate verified fixes. It's available in the form of a self-hosted VSCode extension and as a Github app: VSCode Extension: https://fixbugs.ai/go/vscode-extension - full code and data privacy. - zero data retention models opted out of training. GitHub App: https://fixbugs.ai/go/github-app - we do access your code temporarily. - pick a repo to install FixBugs on. What motivated me to build FixBugs were my years being on-call at Google…

    Jul 2026 · fixbugs.ai · its alternatives →

  21. 21

    Hey HN! I'm Ivan. I've been working on a solution to visually debug my own https:&#x2F;&#x2F;pptr.dev&#x2F; crashes, and this week I opened it to the public: https:&#x2F;&#x2F;buglesstack.com&#x2F;. If you have any questions or suggestions to improve it, feel free to contact me at [email protected]. Thanks for reading! <3

    2025 · buglesstack.com · its alternatives →

  22. 22ME

    We are building a VM that helps you simulate realistic production conditions, model latencies, different interleaving, user requests, and find bugs. Every non-deterministic property is turned into a knob you or a coding agent can control. We have helped teams perfectly reproduce support incidents and found bugs in some of the world's most well tested software (including a database).

    Jun 2026 · workers.io · its alternatives →

  23. 23IM

    I am excited to introduce my solo project, a platform built with the frontend development community in mind. It's an interactive environment aimed at refining debugging skills through exposure to real-world bugs. This project stems from the need for a hands-on, practical method of learning to debug. The site features a variety of intentional bugs for users to solve, mirroring the types of challenges faced in professional settings. Over the coming weeks, I will be adding many more exercises and new features to enhance your learning experience further. Check out CodeMender at…

    2024 · codemender.io · its alternatives →

  24. 24IM

    Hello I'm Jack, I was previously a Site Reliability Engineer and i've been working on monitro.dev which makes log monitoring simple for individuals or small teams. It allows you to easily forward any logs to multiple channels such as Slack, Discord & Telegram. The events are also viewable though the admin dashboard and are easily filterable. Currently there is only an NPM package with javascript &#x2F; typescript support but i have plans to expand this to other languages such as Python, Rust etc. The package has many options, one of them is forwarding any uncaught exception and as an event…

    2024 · monitro.dev · its alternatives →

Also compare

Ranked by how close each launch is in meaning, then by votes. Prices were read from each product’s own site when checked and can change. Refine with your own description →