SignalPipe is an agentic sales pipeline that monitors Reddit, Hacker News, and RSS feeds 24/7 for buying-intent signals. It uses AI to score each signal, draft a reply, and surface only real leads for human review and approval before anything is sent.

How does SignalPipe detect buying intent?

SignalPipe uses a three-stage pipeline: a keyword gate for cheap pre-filtering, OpenAI text-embedding-3-small for semantic similarity scoring against your anchor sentences, and a three-model LLM swarm (Optimist, Analyst, Skeptic) that evaluates each post independently. A hard skeptic veto suppresses any signal the most skeptical judge dismisses.

Does SignalPipe send messages automatically?

No. Every message requires human approval before it is sent. SignalPipe drafts the reply and queues it for your review — you approve, edit, or reject each one. Nothing is sent without your explicit sign-off.

What platforms does SignalPipe monitor?

SignalPipe monitors Reddit (via subreddit RSS feeds), Hacker News (via hnrss.org keyword feeds), and any RSS-compatible feed. You can add as many sources as you want per product.

How is SignalPipe different from Clay or Apollo?

Clay enriches contact lists you already have. Apollo is a cold email database. SignalPipe generates net-new leads by detecting live buying signals — finding people who are actively posting that they need what you sell, right now, in public communities.

SignalPipe has four tiers: BYOK ($19/mo — bring your own LLM key, 3 products, 50 leads/day, 1,000 prospects), Starter ($49/mo — 2 products, 25 leads/day, 500 prospects), Growth ($149/mo — 10 products, 250 leads/day, 5,000 prospects), and Scale ($499/mo — unlimited everything). Open Source is free for self-hosters. The first 100 waitlist members get 50% off for 3 months.

Does SignalPipe work with NVIDIA NeMoClaw?

Yes — fully compatible out of the box. NeMoClaw is NVIDIA's enterprise distribution of OpenClaw, so any OpenClaw plugin installs and runs on NeMoClaw without modification. For on-prem deployments, SignalPipe also supports local model inference: set COMPANION_LLM_PROVIDER=openai_compatible and point it at a locally running Nemotron or any OpenAI-compatible endpoint. Your leads, prospect data, and generated messages never leave your infrastructure.

Can I run SignalPipe fully on-premises?

Yes. Self-host the FastAPI backend on your own server, connect it to your own PostgreSQL database, and configure the companion message generation to use a local model via any OpenAI-compatible endpoint (Nemotron via NeMoClaw, Ollama, LM Studio, vLLM). The only external call that remains is the OpenAI embedding API for signal scoring — and that can be swapped for a local embedding model by request.

Developer Platform

Monitor GitHub Release Feeds for Developer Tool Buying Signals

When a team pins or upgrades a dependency, it's a signal. SignalPipe monitors GitHub Releases RSS feeds for migrations, new integrations, and infrastructure decisions that indicate a buyer.

Feed URL — add as a SignalPipe station

https://github.com/{owner}/{repo}/releases.atom

In your OpenClaw agent: signalpipe_add_station → paste the URL above

What is GitHub Releases?

Every GitHub repository has a public Atom feed for releases. For tool vendors, monitoring competitor or adjacent-tool release feeds reveals who is actively using, upgrading, or discussing those tools — a proxy for buyers already in your market.

Why monitor GitHub Releases for buying signals?

Release notes for competitor tools mention integrations, migrations, and partnerships. Teams that subscribe to those releases are active users — and therefore prospects. Monitoring these feeds identifies engineering teams who are actively invested in the space your product occupies.

How to monitor GitHub Releases with SignalPipe

Identify the feeds to monitor

Start with the top 3-5 competitor or adjacent tool GitHub repositories. Add each one's releases.atom URL as a station in SignalPipe.

Add release-context anchor sentences

Target migration and evaluation language: "migrating from X", "integrating with Y", "replacing our current Z setup".

Monitor release discussions

GitHub release pages generate Issues and Discussions. The RSS feed captures releases; community discussion happens on GitHub Issues — a complementary channel.

Identify authors and companies

Release contributors often have LinkedIn or personal sites linked from their GitHub profiles. Your agent can surface the company behind a release as a warm prospect.

Example GitHub Releases buying signals

"v2.0 — migrating away from [legacy dependency], full rewrite of the data pipeline"

Why it's a signal: Infrastructure migration in progress — team is actively re-evaluating their stack.

"Added SignalPipe integration in this release — tracking sales leads from GitHub Discussions now"

Why it's a signal: Direct product adoption signal — team is solving the same problem.

"Breaking: removed support for [competitor API]. Switching to [alternative] going forward"

Why it's a signal: Competitor churn — actively looking for replacement vendors.

Anchor sentences for GitHub Releases monitoring

Add these when calling signalpipe_add_product. SignalPipe uses them to detect semantically similar posts across your GitHub Releases station.

1"migrating our data pipeline away from a legacy tool"

2"integrating a new sales intelligence layer into our developer workflow"

3"replacing our manual lead tracking setup with something automated"

4"looking for a tool that works natively with our existing GitHub-based workflow"

Frequently asked questions

Do all GitHub repositories have public RSS feeds?

Public GitHub repositories have public Atom feeds at github.com/{owner}/{repo}/releases.atom. Private repositories require authentication. SignalPipe's RSS station supports public feeds only.

Are GitHub release feeds high-volume?

It depends on the repository. Major open-source projects release frequently; smaller tools release monthly. For sales signal purposes, you want active repositories in your competitive space — 2-10 releases per month is ideal.

Can SignalPipe monitor GitHub Issues and Discussions, not just releases?

GitHub Issues and Discussions do not have standard RSS/Atom feeds in the same format. Some repositories use third-party services to expose these. Releases.atom is the reliable public feed format that SignalPipe supports today.

Start monitoring GitHub Releases for buying signals

Join the waitlist. First 100 get Starter free for 3 months.

No credit card. No commitment.

More RSS feed monitoring

Full setup guide →

All 11 tools, anchor sentences, station types

How intent scoring works →

4-stage pipeline: keyword → embedding → sarcasm → LLM

Monitor Product Hunt →

Product Hunt launches attract your target audience

Monitor Lobste.rs →

Lobste

Monitor Hacker News (RSS) →

Beyond keyword-specific HN pages — SignalPipe can monitor the full HN RSS feed or targeted keyword feeds, scoring every post in your category for genuine buying intent

Monitor Stack Overflow →

A developer asking "how do I do X without [current tool]?" on Stack Overflow is a warm lead