The chart that is not a ranking
A MIT live chart of Nest adapters, labeled as one machine.
- Category
- Developer tools
- Who it is for
- Someone choosing a Nest HTTP adapter who will run the chart themselves.
- Possible model
- Open source
- Difficulty
- Medium
- Inspired by
- NestJS Benchmark · NestJS Benchmark
- Original launch
- Watch the launch · Oct 31, 2026
Difficulty is an editorial estimate of technical and operational complexity, not a score.
Startup idea analysis by Startup Ideas. Last reviewed Oct 31, 2026. How we read a launch.
The startup idea
Sajan posted on October 31 a live benchmark of NestJS HTTP adapters: Express, Fastify, and Node, one route at a time, charted as it runs. On his machine Nest plus Node led on all three routes. Yours may differ. The repository is sajanv88/nestjs-benchmark-workspace. The license is MIT. It runs on one machine and has nothing to deploy. The readme says the numbers are unofficial measurements from one machine. They are not comparable to another computer, or to the PR's M1 Pro results. The order held in every run here. The size of the lead did not. With the same 100 connections split across two load generators, Node's lead over Fastify on GET / fell from +54% to +6%. A single generator may become the limit before the faster adapters do, and their numbers would then describe the generator. The post says the order on one machine. It does not say a split load can shrink the lead from 54% to 6%. This page did not run it.
The opportunity is a chart you run on your own box, not a ranking you quote. A smaller product is three routes, the one-machine line, and the note that the ratio moved. A post that treats one machine as a winner is ahead of the readme.
Do not quote the ratio without the machine. Do not treat the generator as the adapter.
The problem
A benchmark post reads like a winner, and the ratios move when the load is split.
Who would pay for this?
- Primary
- Someone choosing a Nest HTTP adapter who will run the chart themselves.
- Secondary
- A person who already has a machine and will not paste the number into a slide.
- Early adopter
- One run, the order, the one-machine label.
How could it make money?
Possible models. Nothing here is a claim about what NestJS Benchmark charges.
- No price. MIT.
- Nothing to deploy.
- The post does not name a seat.
What would the MVP look like?
- Three routes.
- A live chart.
- The one-machine line.
- The +54% to +6% note.
How to validate the idea
- Ask five people to run it on a second machine.
- If the order flips, the post was the machine.
- Do not publish a ratio from one generator.
How to differentiate
- It is a chart, not a ranking.
- The order held. The ratio did not.
- MIT and local.
- Do not become a hosting benchmark.
Original product launch
This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. NestJS Benchmark did not write it.
- Product
- NestJS Benchmark
- Source
- NestJS Benchmark
- Film
- NestJS benchmark, one machine, not a ranking
- Posted
- Oct 31, 2026 · 2:42
Product that inspired this idea
Sajan's post says a live benchmark of NestJS HTTP adapters: Express, Fastify, and Node, one route at a time. On his machine Nest plus Node led on all three routes. Yours may differ. The repository is sajanv88/nestjs-benchmark-workspace. The license is MIT. The readme says the numbers are unofficial measurements from one machine. They are not comparable to another computer, or to the PR's M1 Pro results. The order held in every run here. The size of the lead did not: with the same 100 connections split across two load generators, Node's lead over Fastify on GET / fell from +54% to +6%. A single generator may become the limit before the faster adapters do. The post says the order on one machine. It does not say the ratios move that much. This page did not run the chart.
Posted by @sajanvtech. Watch the original launch. No separate product site is listed unless the post itself is the source.
- nodejs
- benchmark
Related startup ideas
- A browser inside the coding agent’s terminal
Open a real browser from the agent session so the agent can see the page it just changed.
- A checklist the coding agent cannot hide
A plain-language checklist beside Claude Code that pauses for an OK, says when a step is stuck, and puts the limit and the cost on the same screen.
- A coding agent that runs a small model in the browser
A coding assistant that runs locally in the browser on a small model, for people who will not send the repo out.
- A desktop for making games with the model you already pay for
A local app that turns a Claude or ChatGPT subscription, or a local model, into a game-making bench.
- A drive that files the document and cites the page
Upload a pile of files, have them land in a folder a person would recognize, and answer a question with the page it came from.
- A record of whether the setup actually worked
Show a trader how often a setup played out, with the sample size next to the number, on data they already have.
Looking for more ideas?
The full list is startup ideas for 2026, each one tied to a launch you can watch.
Browse startup ideas for 2026