Roadmap
All 60 tools on the plan are built and live, so nothing is queued. The next selection should come from Search Console impressions rather than another round of autocomplete research — the site is now large enough to have its own data.
What follows is the more useful half of that research: the tools considered and deliberately not built, and why. A decision recorded with its reasoning can be argued with and revisited. One that quietly disappears cannot.
Considered and deliberately not built(6)
Several of these are the server-backed versions of tools that did ship in a client-side form. The two standing rules — nothing leaves your browser, and no per-request cost — decided each one, and the page that shipped instead says so in its own words rather than leaving the absence unexplained.
- Prompt Optimizer, generative versionnot built
prompt optimizer ai
Rewriting a prompt with a model needs a server-held API key, a cost per request and rate limiting, and it can silently change what the prompt asks for. The rule-based optimizer ships instead, and says in its first paragraph that it is not generative.
- Regex Generator, natural-language versionnot built
regex generator ai
English-to-regex needs a model, and a regex that looks plausible and is subtly wrong is worse than none — it gets pasted into a validator and trusted. The block builder and sample inference ship instead, and both verify their output.
- HTTP Header Analyzer, URL-fetching versionnot built
check security headers of a url
Fetching a URL on the user's behalf means a request-forwarding endpoint on our origin. The paste-based tool works on authenticated and internal responses that a hosted checker cannot reach anyway.
- OpenAPI Mock Server, hosted versionnot built
hosted openapi mock
Serving user-defined responses from our origin is an open relay by another name. The generator emits a mock you run locally, which also works offline and can be committed.
- Password Generatornot built
password generator
Strong measured demand, but the results page belongs to password managers with acquisition budgets, and the people searching it are not developers.
- Regex Explainernot built
explain regex
Genuinely useful, and largely covered: the regex tester already highlights every match and names each capture group, and the cheat sheet explains the syntax. A separate page would compete with both.
What decides the next batch
Autocomplete breadth was a proxy used because no volume data was available, and it has now been spent: every term it identified is either built or listed above with a reason. Real impression data replaces it, and until there is enough of it the honest answer is that nothing is scheduled.