Skip to content

Code generation656 of 27,186 tools

Filed under Code generation by what their own homepage shows, ranked by who uses them among those still maintained.

A tag is one of thirty-odd words from a closed list, chosen by the same reader from the same page as the line — never a keyword the vendor supplied.

Describe what you need

beta

A sentence or two about the job. We read it into the catalogue's own words, then ask about every tool that fits them.

Ranked by use

Price
What it doesAgents100Workflow automation65Security44Analytics33Video27Writing24

Figure and bar: visits/mo, estimate · year: online since

656Every tool here, by name

Continued, by name: 2

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk