draft-imran-systems-and-arguments-45Internet-Draft
← draft-imran-systems-and-arguments-45
Off the Bit Tools Category: Catalogue Count: 13 with evidence, 591 catalogued
M. Imran Index: draft Checked: 2026-09-04

Tools

Two lists, kept apart on purpose. One is short and carries evidence. The other is long and carries no claim at all.
The difference between the two halves is the only thing here worth being careful about. Used here is 13 tools, and every row names the file in this repository that proves it. Catalogued is 591 tools described from their own homepages: what each one is, what it is sold for, and whether it still answers. None of that is a claim that anyone here has used them. Merging the two would read as fluency across six hundred products, which nobody has.

Find

Searches names and descriptions, answered server-side. The reading path here ships no JavaScript, and a search box that needs a bundle to work is a search box this site cannot have.

Used here

These build, check or serve this site. The evidence line is the point: each one names a file you can open in the repository and confirm, rather than asking you to take a rating on trust. They are the only starred entries on the site.

What the three words mean.
builds In the dependency graph or the deploy path of this site. Removing it breaks the build.
checks Runs in CI against every push. Removing it loses a guarantee the site makes in public.
serves Runs in production, on the request path of a real visitor.

Depth of use across the owner's wider work is not recorded yet. The vocabulary above describes this repository only, which is the part that can be checked by reading it.

By category

Fourteen shelves. Each page lists everything on it, alphabetically, with a drawing where the entries actually reference each other and a note where they do not.

115 AI assistants and agents Editors, completions and agents that write or change code. 88 Workflow and productivity Repos, code navigation, extensions and the rest of the desk. 66 Testing and code quality Test runners, review tools, linters and debuggers. 45 Security and secrets Scanning, identity and secret handling. 41 Models and AI infrastructure Model families, local runners, SDKs and the MCP surface. 41 Monitoring and analytics Knowing what the thing did after you shipped it. 35 Data, APIs and backends Databases, backends-as-a-service, API tooling and search. 34 CI, CD and infrastructure Pipelines, provisioning and orchestration. 31 Docs and content Documentation platforms, headless CMS and localisation. 29 Payments and messaging Billing, mail, messaging and shipping. 22 Hosting and cloud Where it runs once it leaves the laptop. 18 Terminal and CLI Shells, terminal emulators and command-line utilities. 16 Design and media Interface design, images and video. 10 Editors and IDEs Where the code is actually typed.

What the check found

Every homepage in the catalogue was fetched on 2026-09-04, twice: once plainly, then again in a real browser for the ones that refused. That is where the descriptions come from, and it is the only way to find out that something is gone.

33 of 591 did not answer. Some are dead domains, some return 404, some present an expired certificate, and a few simply refuse automated requests and are probably fine. Each one says which. They stay listed, struck through, because nothing here is deleted.

140 answered from a different address than the one listed. Some are ordinary redirects. Others are acquisitions, renames, or a domain that changed hands and now sells something else entirely. Each tool's page names where it actually led.

On the word "cloud"

This was asked for as a cloud, with every tool wired to the ones it relates to. The data does not support that drawing and the honest thing is to say so here rather than to invent the wiring.

An edge means one entry names another by name. That yields 85 edges across 591 tools, and only 6 of the fourteen categories have enough of them to draw. Products are described on their own terms, so the text almost never says what a thing works with. Where a graph exists it is on the category page. Where it does not, that page says so and lists the tools instead. A hundred nodes wired by shared category would look like a cloud and would mean nothing.

How this was built

The list of names was assembled from public directories of developer tools. Nothing else came from them: every description, every line about what a tool is sold for, and every judgement about where it sits was written here from the product's own homepage.

Re-running the check is one command, and the results are committed rather than fetched at build time. A page that reaches the network to render is a page that depends on a stranger's uptime.

ImranTools[Catalogue]