What Naerru searches
Naerru looks for public conversations where users describe real product friction: broken workflows, confusing setup, tool comparisons, missing features, pricing objections, and integration problems.
The search surface is intentionally bounded. A report is only as useful as the evidence it can point to, so Naerru favors sources where discussions are accessible, stable enough to cite, and appropriate to ingest.
Current sources
Hacker News
Public APIUsed for discussions around products, tools, technical workflows, and founder/operator complaints.
Stack Exchange
Public APIUsed for specific problem statements, implementation friction, and questions that reveal unmet needs.
GitHub Issues
Repository connectorsUsed where issue discussions expose setup pain, bugs, missing features, integrations, and adoption blockers.
Product Hunt
Launch feedUsed for product launches and their discussion, surfacing how makers position tools and what early users react to.
RSS feeds
Curated feedsUsed for a curated set of blogs and changelogs where product changes, announcements, and recurring complaints surface.
What Naerru does not search
Naerru does not crawl the entire web, bypass paywalls, scrape private communities, or collect from sources that cannot be explained clearly to a report reader.
It also does not treat a lack of direct mentions as proof that a market has no demand. When direct evidence is sparse, the report can lean on category or competitor discussions, and it should say so.
Why scope matters
A narrower source set makes the product more honest. Naerru can show where a claim came from, separate direct signals from inferred ones, and avoid presenting vague web noise as product intelligence.
Source criteria
A source is useful only when it improves evidence quality and can be handled responsibly. Naerru favors reliable public signals, source-specific access paths, clear usage boundaries, and stable links back to the original discussion.