# Developer Tools Directory

> A curated directory of developer tools: AI coding assistants, editors, CI/CD, observability, databases, API tooling and security scanners. Editorial, unpaid, and checked.

Site: https://developertoolsdirectory.com/
Listings: 29
Updated: 2026-09-11

## What this site is
Every team assembles roughly the same toolchain and argues about it endlessly. This is a plain directory of the serious options in each layer — write, build, ship, watch, store, secure — with enough of a description to tell you whether a tool is even aimed at you before you sit through a demo.

## Machine-readable data
- https://developertoolsdirectory.com/entries.json  — the full listing set as JSON (name, url, category, blurb, tags).
  Stable shape. Attribution appreciated; a link back to the listing page is the only ask.

## Editorial policy
Listings are editorial and unpaid. Inclusion is not an endorsement. Outbound links are
checked to resolve before publication. Advertising is labelled and never determines
editorial placement.

## Categories
- Write
- Build & ship
- Watch
- Store
- APIs
- Secure

## Questions this site answers directly

### How much of a toolchain should a small team actually pay for?
Pay for the things that cost you hours when they break and that you do not want to operate: CI runners, error tracking, and a managed database are usually worth money early. Self-host the things you would otherwise pay a premium for and rarely touch. The expensive mistake is buying an enterprise observability contract before you have enough traffic to generate signal.

### Do AI coding assistants actually save time?
They reliably save time on well-specified, mechanical work — boilerplate, tests, translations between languages, unfamiliar API syntax. The gains are far less clear on novel design decisions and on debugging, where reviewing a confident wrong suggestion can cost more than writing it yourself. Measure it on your own work before rolling it out as policy.

### What is the difference between monitoring and observability?
Monitoring answers questions you thought of in advance — CPU, error rate, latency. Observability is the ability to ask new questions about a running system without shipping new code, which in practice means high-cardinality structured events and traces rather than pre-aggregated metrics. Most teams need both and buy only the first.

### Should CI run on the same platform as source control?
It is the simplest choice and usually the right one — integration is free and permissions are already solved. Move off it when build minutes become expensive at your volume, when you need specialised hardware, or when you need to run builds inside your own network for compliance reasons.

### Does this directory take payment for listings?
No. Listings are editorial and unpaid. Advertising on the site is labelled and has no bearing on what gets listed or where it appears.

## Contact
privacy@developertoolsdirectory.com · legal@developertoolsdirectory.com