Dev tools · alternatives · 2026
24 alternatives to Errorcore
Runtime context layer for production failures
Below are 24 products that do a similar job, ranked by how close each is in meaning and then by launch-day votes.
- 1
Automated Penetration Testing for AI-Built Apps
2021 · replay.io · its alternatives →
- 2
Resolve incidents faster with AI-driven triage, contextual insights, and streamlined collaboration for improved reliability and reduced downtime.
2013 · takipi.com · its alternatives →
- 3
I got sick of the old software development loop: Change code -> Run tests -> wait -> wait some more -> look at failures. I decided to build a tool that will enable you to: Change code -> look at failures. No wait time, no explicit test running. Under the hood: - Runs the whole test suite and collects code coverage per test. - For each auto file save, analyzes the changes on the tests. - Runs changed tests in the background. - Display results, the loop time from change to test results is approx 250ms. Instead of: code -> alt+tab -> arrow up -> rerun all the tests -> wait ... -> test results…
2022 · github.com · its alternatives →
- 4
- 5
- 6
Stop guessing why bugs happen
2023 · launchdarkly.com · its alternatives →
- 7
- 8
- 9
Debugging a crash can sometimes feel like a noir detective story: following faint clues, chasing red herrings, and eventually hitting the moment where the whole case finally makes sense. I leaned into that idea and built Fatal Core Dump, a small game where the investigation is real crash debugging. The game gives you a Linux binary, its core dump, a source file, and some logs. You solve the mystery by debugging it. The premise: an engineer dies when an airlock on an asteroid mining station opens unexpectedly. Your job is to determine whether it was a simple software bug or something more…
Mar 2026 · robopenguins.com · its alternatives →
- 10
Observer▲83Live logs inside your IDE to Debug without context switching
Apr 2026 · mobileagents.io · its alternatives →
- 11WV
2020 · visualprogramming.net · its alternatives →
- 12
Hey HN, the is Chris, creator of FireDBG. We’ve been working on this debugger just about a year now. Time travel debugging isn’t a new concept, the new idea here is to use call tree visualisation to help us navigate the debug trace. It supports various Linux distros on x64 and macOS on x64 and M1. It’s only available for Rust right now, but we do want to bring this debugging experience to other programming languages. Please give it a try! Would love to know your thoughts. What’s your anecdote in debugging programs? My stupidity is usually in the form of: after a few hours of debugging, I…
2023 · firedbg.sea-ql.org · its alternatives →
- 13
Comie.dev▲78Production context for AI with logs, DBs, and error tracking
May 2026 · comie.dev · its alternatives →
- 14
This project is inspired by some of the asserts in Unreal engine. Due to reliance on core_intrinsics it is necessary to develop using nightly Rust, but there are stubs in place so a production build will not require nightly. I recently released version 0.2 which includes no_std support and adds optional log message arguments to the ensure macro.
2024 · github.com · its alternatives →
- 15UD
Hey HN! I’m the founder of Unify, and we’ve just released our Model Hub, which provides a collection of LLM endpoints with live runtime benchmarks all plotted across time: https://unify.ai/hub A key finding is that static tabular runtime benchmarks for LLMs simply do not work. It’s necessary to take a time-series perspective, and plot the variations through time. We currently have 21 models provided by: Anyscale, Perplexity AI, Replicate, Together AI, OctoAI, Mistral AI and OpenAI, with more on the roadmap. We test across different regions (Asia, US, Europe), with varied…
2024 · its alternatives →
- 16
Hi HN! We’re Arthur and Adrien from CodSpeed. We’re building a tool measuring software performance before any production deployment, catching performance regressions before they hit production environments and reporting performance changes directly in Pull Request comments. It’s kind of like Codecov but for performance measurement. Today, the go to solution to measure performance is probably to use an APM(DataDog, Sentry, …), continuously analyzing your production environment. However, since those solutions are operating on real environments they need real users to experience poor…
2023 · codspeed.io · its alternatives →
- 17VT
Hi All, this is Shardul here - I am the co-founder of Videobug. https://bug.video We are super excited to share Videobug with you. Videobug records run time code execution so that developers can watch it line by line as frequently as they want, right in their IDE. It takes away the pain of recreating exact conditions that led to a bug and saves developer time in every bug squash. Parth (my co-founder) and I have worked on multiple production grade applications in startups and enterprises. We used Logrocket, Sentry, and Datadog for logging and found ourselves adding more logs after…
2022 · its alternatives →
- 18
Incident/Ops▲59I've been an on-call engineer at startups where "incident management" meant someone panic-creating a Slack channel called #fire-fire-fire, or all incidents handled in the #incidents channel at the same time... and the postmortem was whatever someone remembered to write in Notion three days later. So I built a Slack bot to fix my own workflow. Figured I'd share it. What it does: "/incident start sev2 API latency spike" creates a dedicated channel, invites whoever's on-call, pins the details, and starts recording a timeline. When you run "/incident resolve", it uses GPT-4 to analyze…
Jan 2026 · incidentops.io · its alternatives →
- 19
- 20
Freeze the exact moment your app failed. Replay it.
Jul 2026 · runtimevault.dev · its alternatives →
- 21
I've been presenting at local meetups about Context Engineering, RAG, Skills, etc.. I even have a vbrownbag coming up on LinkedIn about this topic so I figured I would make a basic example that uses bedrock so I can use it in my talks or vbrownbags. Hopefully it's useful.
Apr 2026 · github.com · its alternatives →
- 22
A cross-language, zero-copy coroutine observability framework based on the cTP shared-memory protocol, utilizing lock-free ring buffers for ultra-low overhead state tracing. - lixiasky-back/coroTracer
Mar 2026 · github.com · its alternatives →
- 23
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 · its alternatives →
- 24
Stack Error is a pragmatic error handling library for Rust that provides helpful messages for debugging, and structured data for runtime error handling. Features: * Informative error messages: stack error messages and optionally add file/line context to your messages. This helps convey not just what went wrong, but also how it went wrong, making debugging faster. * Programmatic error handling: include optional error codes and URIs for robust runtime handling. * Library-Friendly: define custom error types easily while staying compatible with Rust’s error ecosystem. If designing good…
2025 · github.com · 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 →