CLIs, libraries, SDKs, and the infrastructure around them. The audience reads code before it reads copy.
53 live Developer Tools listings, ranked by points. Browse every category.
Ranking uses points. 1 upvote = +25 points.
Developers evaluate tools by trying them, so the landing page matters less here than anywhere else on the site and the docs matter more. A quickstart that fits on one screen, an install command that works on a clean machine, and an honest note about what breaks are worth more than a hero section. If your README is better than your landing page, link the README.
Say what it is built on and what it assumes. Half the abandoned installs in this category come from a developer discovering after ten minutes that the tool needs Docker, a paid API key, or a runtime they do not use. Put the requirements above the fold and you lose the wrong users early instead of annoying them late.
Open source changes the pitch rather than replacing it. Being on GitHub is not a reason to adopt something. Say who maintains it, how often it ships, and what the paid layer covers if there is one, because the question behind every adoption decision is whether this thing will still exist in a year.
Yes, and they tend to do well here. A repository with a working example and a clear licence is a complete listing.
No. Libraries, CLIs, and services are all normal in this category. Screenshots are optional when there is nothing visual to show; a code block does the same job for this audience.
Either order works, and they answer different questions. A listing keeps working after launch day since it stays indexed and keeps sending traffic, while a Show HN is one spike of attention from people who will tell you exactly what is wrong with your idea. Launching here first at least means the page you point them at exists.
Ready to add yours? Submit a launch or read how the free and paid listings differ.