planned
Launches and comments through the official GraphQL API. Planned.
When Product Hunt ships as a source, discatch will read launches and comments through the official GraphQL API, free. Competitor launches on the day they happen, comments on your own launch, and new products in your category are all catches waiting to fire. The launch-day playbook sets tight-interval catches 12 hours before and tears them down 48 hours after. Product Hunt is planned.
Launches that name you or your category, and comments on them.
The official GraphQL API, free.
One syntax for every source: quotes, AND, OR, NOT, site:, author:, lang:.
query
"your category" OR "your product"One result, as a catch delivers it: source, author, the post, a prescore, thread context, and a suggested action your agent can act on.
We built a social listening tool for developer teams. Monitor Reddit, HN, and GitHub for mentions of your project. Free for open source.
Product Hunt is an event source, not a continuous one. The launches that matter happen on specific days. The launch-day playbook is the right pattern: tight catches during the event, standard catches after. This is the opposite of Reddit or HN, where the conversation is continuous. A catch at 5-minute intervals during the 48-hour window and a 24-hour catch afterward covers both the launch event and the long-tail discussion that follows.
The official Product Hunt GraphQL API returns launches, comments, and metadata like upvote count and maker status. It is free. Comment reads are cheap. The constraint is that the mention surface is small: only launches and their comments, not broader discussion about your product outside of launch threads. For broader coverage, combine a Product Hunt catch with catches on Hacker News, web, and Bluesky.
No listening vendor has a dedicated Product Hunt tool page. Mention.com has a blog post that ranks by default. An Apify actor and an indie tracker fill the gaps. The intent splits between launch monitoring and VC scouting. discatch targets the launch monitoring side: competitor launches, comments on your own launch, and new products in your category.
Product Hunt is planned. No results arrive from it today. When it ships, discatch will use the official GraphQL API, which is free, to read launches and comments. The launch-day playbook pairs with it.
Your category
"social listening" OR "brand monitoring" OR "keyword alerts"Your product name on launch day
"your product" OR "yourdomain.com"Launch comments are dense signal. The first question is almost always "how is this different from X?" The second is about pricing. The third is about whether it works with their stack. A catch on your product name during a launch, routed to whoever answers comments, means nothing goes unanswered in the first hour. A catch on competitor names tells you what people ask about their product that they struggle to answer.
The launch-day playbook sets 5-minute catches across every source 12 hours before your launch. It watches for your product name, your domain, your category terms, and your competitor names. Everything routes to a Slack channel and a Claude Code command that files anything bug-shaped. 48 hours after the launch, the playbook tears down the tight-interval catches and switches to a standard 6-hour watch.
The same playbook works when a competitor launches. Set it on their product name 12 hours before their announced date and you will know what people ask about them, what they compare them to, and whether your product comes up.
The intent splits between launch monitoring and VC scouting. Most tools in this category focus on ongoing brand monitoring, not event-driven watching. Product Hunt’s GraphQL API is free but the comment surface is small. For discatch, the value is the playbook integration: event-driven catches that spin up, watch, and tear down automatically.
No. Product Hunt is planned. It is behind the same gate as the other planned sources.
Yes. The launch-day playbook sets 5-minute catches across every source 12 hours before and tears them down 48 hours after.
The GraphQL API is free. Costs are one alert unit per firing plus one result unit per matched item.
Both. A comment on a launch is a result with parent_url pointing at the launch.
Not directly. Some Product Hunt pages may appear as web results if the index has picked them up, but comment content and launch metadata do not appear in web results.
No listening vendor has a dedicated Product Hunt tool page. Mention.com has a blog post that ranks by default. An Apify actor and an indie tracker fill the rest of the results.
The API returns launches and comments, not funding data. The intent of this source is launch monitoring and mention tracking, not VC scouting.
An Apify actor is a one-off scraper that runs when you trigger it. discatch is a standing catch with a destination that runs on the interval you set and pushes scored, filtered results with a suggested action to your agent. The actor returns raw data; discatch returns results with prescore, thread context, and an action the agent can take immediately.
Yes. Name multiple sources in the catch. A launch-day catch might name producthunt, hackernews, web, and bluesky to catch reactions across every platform where your launch is discussed.
No. Product Hunt uses the GraphQL API, not a firehose. The catch interval determines how often discatch checks.
Last reviewed by Parsa Khazaeepoul, founder, dcouple. Facts from docs/data-sources.md and docs/coverage-matrix.md; status from docs/api.md; the search landscape from docs/seo/keyword-map.md.