Alternatives
Products that do what Tapr does
Debug API performance in seconds- right from your terminal
- 1
- 2SA
I've frequently found myself using [nvitop](https://github.com/XuehaiPan/nvitop) to diagnose GPU/CPU contention issues. The two best things about it are: - It's easy to install if I can access pip in the container - It makes a compelling screenshot (which helps me communicate with coworkers.) With those two lessons in mind: Here is Sping! Purpose: Help observe and diagnose latency issues at layer 4+ (TCP/HTTP/HTTPS) Two good things about it: - It's easy to install if you have pip. (Available at…
2025 · dseltzer.gitlab.io
- 3
- 4
- 5
- 6FF
A few months ago, I benchmarked FastAPI on an i9 MacBook Pro. I couldn't believe my eyes. A primary REST endpoint to `sum` two integers took 6 milliseconds to evaluate. It is okay if you are targeting a server in another city, but it should be less when your client and server apps are running on the same machine. FastAPI would have bottleneck-ed the inference of our lightweight UForm neural networks recently trending on HN under the title "Beating OpenAI CLIP with 100x less data and compute". (Thank you all for the kind words!) So I wrote another library. It has been a while since I have…
2023 · github.com
- 7IB
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
- 8DB
I built a CLI to benchmark DNS resolvers after discovering DNS was adding 300ms to my API requests. v0.3.0 just released with new features: compare: Test single domain across all resolvers top: Rank resolvers by latency/reliability/balanced monitor: Continuous tracking with threshold alerts 1,400+ downloads in first week. Quick start: pip install dns-benchmark-tool dns-benchmark compare --domain google.com CLI stays free forever. Hosted version (multi-region, historical tracking, alerts) coming Q1 2026. GitHub: https://github.com/frankovo/dns-benchmark-tool…
Nov 2025 · github.com
- 9AT
Hi everyone, I recently published a small open-source project. It’s a minimal network packet analyzer written in Go — designed more like a learning toy than a replacement for Wireshark. It currently supports parsing basic protocols like TLS, DNS, and HTTP, and includes a tiny fuzzing engine to test payload responses. You can inspect raw packet content directly from the terminal. The output is colored for readability, and the code structure is kept simple and clear. The entire program is very small — just about 400 lines of Go code. I know it’s not anywhere near Wireshark’s level, and I still…
2025 · github.com
- 10AT
I recently built a small open-source tool to benchmark different LLM API endpoints — including OpenAI, Claude, and self-hosted models (like llama.cpp). It runs a configurable number of test requests and reports two key metrics: • First-token latency (ms): How long it takes for the first token to appear • Output speed (tokens/sec): Overall output fluency Demo: https://llmapitest.com/ Code: https://github.com/qjr87/llm-api-test The goal is to provide a simple, visual, and reproducible way to evaluate performance across different LLM providers, including…
2025 · llmapitest.com
- 11PI
I built pbar.io because I was tired of SSH'ing into servers to check if my data processing scripts were still running, or worse, having them finish/crash without knowing. It's a simple REST API that lets you create and update progress bars from anywhere. The same progress bar can be viewed as terminal output (with ANSI colors), in a browser, or consumed as JSON. I'm actually tracking this HN discussion with pbar. The progress bar increases with each comment - watch it live as we discuss! Web: https://pbar.io/Y8yg3BG Terminal: curl…
Sep 2025 · pbar.io
- 12VD
Hey all, I've been working on this side project to get a Cypress.io-like experience, but for Ruby developers. It's plug-n-play with Capybara system tests, with the following features: - visualize assertions/commands as they happen - view all API requests, errors, and logs in the timeline - pause/continue on any step - rewind through history with a recorded video This is brand new, so looking for people to start trying it out and leave feedback.
2024 · github.com
- 13
- 14TY
2021 · github.com
- 15IR
Sharing an internal tool that accelerated my development work 10-fold, especially with API debugging. Thought fellow developers here might find it useful. As a developer, I often have trouble reproducing errors at the client end. https://intercept.rest lets me debug and monitor API requests and responses. It is similar to the Network tab in Chrome Developer Tools but works for any API: mobile apps, webhooks, frontend etc. After I shared it with a close circle of friends, they found it incredibly useful and even found new use cases, I never imagined. Been a long time lurker here and…
2018
- 16AO
Hey HN. We’re Jay and Vadim from Highlight.io (https://highlight.io). We’re building an open source [1] monitoring platform for web applications. Today we’re excited to be sharing a performance tool we’ve been working on, which helps you inspect the latency of code execution from the client to the server. As engineers at past startups, we often had to debug slow queries, poor load times, inconsistent errors, etc... While tools like Jaegar [2] helped us inspect server-side performance, we had no way to tie user events to the traces we were inspecting. In other words, although we had…
2024 · github.com
- 17
- 18IB
Hi HN, I built this because I got tired of the Claude Code CLI hiding details from me. Recent updates have replaced critical output with summaries like "Read 3 files" or "Edited 2 files". To see what actually happened, I was forced to use `--verbose`, which floods the terminal with unreadable JSON and system prompts. I wanted a middle ground: *Full observability without the noise.* `claude-devtools` is a local Electron app that tails the session logs in `~/.claude/` to reconstruct the execution trace in real-time. *Unlike wrappers, it solves the visibility gap in your native…
Feb 2026 · github.com
- 19WB
Hi, this is Mish and Sebastian. We are working on Step CI - a fully automated API testing platform for developers. Step CI works programming-language independent and for different API paradigms (REST, GraphQL, XML). Our CLI and test runner are available on GitHub (https://github.com/stepci) under the MPLv2 license. Since our last launch, Step CI is now able to generate automated tests for your API based on your OpenAPI (Swagger) spec. This saves you a lot of time as you never have to write and maintain your tests again! We would like to invite you to try our tool and give us…
2022 · stepci.com
- 20IM
Mar 2026 · github.com
- 21
- 22AF
2025 · httl.dev
- 23TA
Note: this is an update to [this](https://news.ycombinator.com/item?id=44568529) "Show HN" post. timep is a state-of-the-art [debug-]trap-based bash profiler that is efficient and extremely accurate. Unlike other profilers, timep records: 1. per-command wall-clock time 2. per-command CPU time, and 3. the hierarchy of parent function calls /subshells for each command the wall-clock + CPU time combination allows you to determine if a particular command is CPU-bound or IO-bound, and the hierarchical logging gives you a map of how the code actually executed. The standout…
2025 · github.com
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →