Contact

Say hello.

Found a bug, know a tool I should add, or have an idea? Send it over. I read everything.

Get in touch

The quickest way to reach me is a GitHub issue. It keeps things public and searchable, so the next person with the same question can find the answer. Prefer email? That works too.

⏱ Response timesI usually get to GitHub issues within a couple of days. The form opens your email client, and replies to those take a bit longer, but I do get to them.

Send a message

Fill in the form and it'll open your email client with everything pre-filled.

Opens your email client with the message pre-filled. Your data is never stored by this site.

Frequently asked questions

Best way is to open a GitHub issue with the name, URL, category, and a line on what it does. I check suggestions by hand, usually within a week. The form above works too, just pick the "Tool / Tech Suggestion" subject.
Open an issue with the tool name and what's wrong (pricing, description, URL, category). Corrections are the fastest thing for me to fix, so don't hesitate.
The raw data files (tools-data.js and tech-data.js) are right there in the GitHub repo. There's no formal API, but it's plain JSON so it's easy to work with. Ask if you need something specific.
I'm open to tasteful, developer-focused sponsorships that don't mess with the catalog. What I won't do is sell placement. Paying won't move a tool up the rankings or into a category. If that works for you, use the form with the "Partnership / Collaboration" subject.
I try to refresh it monthly. The "Updated May 2026" badge in the hub shows the last big pass. Corrections and additions people send in get merged as I work through them.
Yep, all the source is on GitHub. PRs are welcome for fixes, accessibility tweaks, and features. For anything bigger, open an issue first so we can talk it through before you put in the work.