How do you monitor competitors on GitHub and Hacker News?

What should you watch for each competitor?

Watch their launches, the threads where users complain about them, the issues on their public repos, and any thread where someone asks for an alternative to them.

Most of what you learn about a competitor on these two sites comes from their users, in comment threads and issue trackers, written in the users' own words. A launch post tells you what they shipped. The comments under it tell you what developers thought of it.

The fourth signal is the rarest and the most useful. Someone asking 'is there an alternative to X that I can self-host?' has already decided to leave and is choosing where to go.

How do you follow a competitor on Hacker News?

Search hn.algolia.com for each competitor's name, filter to the past day, and check both stories and comments every morning.

Hacker News has a public search at hn.algolia.com. Search the product name and the company name separately, since people use both, and set the date filter to the past 24 hours. Switch between stories and comments: most competitor mentions sit inside threads about something else, where someone writes 'we moved off X last year because...'.

When a competitor posts a Show HN, read the whole thread the same day. The top comments usually ask the questions your own buyers will ask you, and the maker's replies show how the competitor positions itself under pressure. Copy the two or three strongest objections into your notes with the link.

Which GitHub searches show what competitors' users are saying?

Scope the search to the competitor's organisation with org:, add is:issue and is:open, and search titles with in:title for words like 'alternative' or 'migrate'.

A plain search for a competitor's name on GitHub returns code, package files and forks. Qualifiers narrow it to conversations. Replace examplecorp below with the competitor's GitHub organisation or product name, and bookmark each search.

Watching a competitor's repository sends you a notification for all of its activity, which is far too much for a busy project. A bookmarked search you open daily is easier to keep up with. Our guide to monitoring GitHub issues for competitors covers reading reactions and labels in more depth.

• org:examplecorp is:issue is:open sort:reactions-+1-desc lists their most wanted open requests.
• repo:examplecorp/examplecorp is:issue is:open in:title slow finds performance complaints in their main repo.
• examplecorp is:issue -org:examplecorp finds issues in other projects that mention them, often integrations or replacements.
• "alternative to examplecorp" is:issue finds people asking other maintainers for a replacement.

What should you do with a competitor mention once you find it?

Reply with disclosure when someone asks a question you can answer, log repeated complaints for the roadmap, and update your comparison page when an objection keeps coming up.

Most finds need no reply. A complaint in a competitor's issue tracker belongs to their maintainers, and posting your product there will annoy everyone reading it. A thread on HN where someone asks 'what do people use instead of X?' is different: that person asked, and a useful answer from you is welcome if you say who you are.

• Reply: start with 'I work on [product]', answer the actual question, and mention your product only where it fits what they asked.
• Roadmap: keep one sheet with the competitor, the complaint, the link and a count. A complaint that appears five times in a month is worth a product conversation.
• Comparison page: when the same objection about a competitor keeps appearing, address it on your comparison page using the words users wrote.

How does MarketHQ track competitors on GitHub and Hacker News?

Add each competitor's name to your workspace and MarketHQ matches it in Hacker News stories and comments and in GitHub issues and pull requests, on every plan.

Lite tracks two competitors and ten keywords, and every plan checks these sources four times a day and keeps the last 30 days of posts in one feed alongside Stack Overflow, Dev.to, Lobsters, blogs and news. It picks up to three reply opportunities from that feed and sends a weekly summary email. GitHub results leave out bot accounts, so dependency update bots do not fill the list.

Paid plans raise the competitor limit (2 on Lite, 5 on Startup, 10 on Growth), add Reddit, X, LinkedIn, YouTube and Bluesky, and run a weekly gap analysis that compares you with each competitor and turns the gaps into an action plan with the evidence attached.

One caution: MarketHQ matches names on word boundaries, so a competitor whose name is a common word will bring in noise. Add a qualifying keyword, such as the name plus the category, to keep the feed clean.

What does a week of competitor watching look like?

Illustrative example: two rivals, about a dozen matches, one reply, one roadmap note and one comparison page edit.

Illustrative example: a team selling a feature flag service watches two rivals. Over one week they see a Show HN from the first rival, where the top comment complains about per-seat pricing, and four open issues on the second rival's repo asking for a self-hosted option. An Ask HN thread asks for an open source alternative to the first rival. They answer that thread with disclosure, add 'self-hosted requests: 4' to the roadmap sheet with links, and add a short pricing section to their comparison page that answers the per-seat objection.

What will GitHub and Hacker News monitoring miss?

Anything said in private, anything about a closed-source competitor without a public tracker, and buyers who never post.

Enterprise buyers rarely comment on HN about vendors they are evaluating, and closed-source competitors keep their bug reports in private tools. Small competitors may get no mentions for weeks. Treat these two sites as one source of evidence about competitors, and pair them with sales call notes and, if your buyers are there, Reddit and LinkedIn.