nowfound

Alternatives

Products that do what Errorcore does

Runtime context layer for production failures

  1. 1

    Complete Frontend Error Tracking at an Affordable Price

    2024

  2. 2
    Context178

    A WayBackMachine for your user experience

    2021

  3. 3
    Recost130

    Your API costs fully visible.

    Apr 2026

  4. 4
    Replay279

    Your time travel debugger

    2021

  5. 5

    Production Debugging Games for Software Engineers

    May 2026

  6. 6

    Live logs inside your IDE to Debug without context switching

    Apr 2026

  7. 7

    Production context for AI with logs, DBs, and error tracking

    May 2026

  8. 8

    Discover you only debug 1% of your time

    Oct 2025

  9. 9

    Trace, evaluate, and improve AI agents in production

    30d ago · telerik.com

  10. 10DY

    Hi HN, this is Shimon and Eyar of Datree (https://www.datree.io/). When I was an Engineering Manager of Infrastructure at ironSource (NASDAQ:IS) for 400 developers, a developer made a mistake, causing a misconfiguration to reach production, which caused major problems for the company's infrastructure. Mistakes happen all the time - you learn from them and hope to never make them again. But how can we prevent a production issue from recurring, or, how about a bigger challenge — how can you prevent the next one from the get-go? In our case, we tried sending emails to our devs,…

    2021

  11. 11

    Trace AI requests, workflows, and costs in one timeline

    May 2026

  12. 12
    TraceLLM100

    OpenTelemetry for production AI applications

    Jul 2026 · tracellm.in

  13. 13

    Helping developers debug less & code more

    2019

  14. 14
    Confeur70

    Observability for program management

    2019

  15. 15SF

    Hi HN, Over the past two years I’ve built and debugged a fair number of production pipelines—mainly retrieval‑augmented generation stacks, agent frameworks, and multi‑step reasoning services. A pattern emerged: most incidents weren’t outright crashes, but silent structural faults that slowly compromised relevance, accuracy, or stability. I began logging every recurring fault in a shared notebook. Colleagues started using the list for post‑mortems, so I turned it into a small public reference: 16 distinct failure modes (semantic drift after chunking, embedding/meaning mismatches,…

    2025 · github.com

  16. 16

    Capture twice the context in half the steps

    Feb 2026

  17. 17ST

    We're a couple of software engineers who believe that to build great software you need to write good tests, but we also sympathise when engineers say things like: - "Writing tests was too time consuming on my tight schedule", or - "Unit tests don't catch enough bugs, so they're useless", or - "I've inherited a legacy code base without tests and have no idea where to start" To tackle this we're building Symbolica (https://www.symbolica.dev), a symbolic code executor [1], that lets you run your code for all possible inputs. This means you can do things like: - Assert properties about…

    2021

  18. 18

    One run: bug found, ticket written, fix prompt ready

    13d ago · optics-qa.com

  19. 19
    Loghead20

    Context aware log layer for AI coding tools

    Jan 2026

  20. 20AV

    We made a VS Code extension [1] that lets you visualise logs and traces in the context of your code. It basically lets you recreate a debugger-like experience (with a call stack) from logs alone. This saves you from browsing logs and trying to make sense of them outside the context of your code base. We got this idea from endlessly browsing traces emitted by the tracing crate [3] in the Google Cloud Logging UI. We really wanted to see the logs in the context of the code that emitted them, rather than switching back-and-forth between logs and source code to make sense of what happened. It's a…

    2025 · github.com

  21. 21

    Incident tracking for runtime errors

    28d ago · retracekit.cloud

  22. 22IB

    Hi HN, I've been working on this for a while and it was hard to decide when to stop, either on the way information is presented or when to stop with adding entries. It's not meant as a blog, but rather as a reference that keeps growing. Link: https://thehardparts.dev Currently I've created 4 main section: - Failure Modes: ways project go wrong - Red Flags: early signals that are worth taking seriously - Tech Decisions: common and not so common trade-offs for hard choices - Playbooks - guided approach for situations that repeat I've also focused on creating links between them to…

    Apr 2026 · thehardparts.dev

  23. 23WV

    Hi HN, I'm the CEO at https://replay.io. We've been working on time travel debugging for web development for a while (https://news.ycombinator.com/item?id=28539247) and more recently an AI app builder that uses that debugger to get past problems instead of spinning in circles (https://news.ycombinator.com/item?id=43258585). We've gotten to where we can pretty easily build apps to replace business-critical SaaS tools, some of which we're now using internally: * We built our own issue tracker to keep track of all our development projects, tickets, bug…

    Dec 2025

  24. 24SO

    I built Checkpoints App out of my experience of not being able to quickly and easily measure the speed of processes across my tech stack in my startup. All startups optimize for speed in all of their operations: deploying code, responding to API requests, loading the UI, and in background processes such as sending emails to users or processing data in an ETL pipeline. But the tools available to measure the performance of all these operations are separate and time-costly to integrate, in the first place. Checkpoints App allows you to measure the speed of processes across your entire stack…

    2022 · checkpoints-app-36545.web.app

Ranked by how close each launch is in meaning, then by votes. Refine with a description →