Channel funnel
Discovered, screening, vetted, active, paused. A channel with zero return leaves the line and frees the limit for one that delivers.
public data collection
Reconnaissance by direction, not a single-site parser
You set a direction — the system finds the communities where the audience lives, collects public messages, filters out noise and returns signals: pains, intent, trends.
- 11
- surfaces in the fan-out
- 4
- cascade stages
- 0
- paid services
From topic to signal
Every stage is cheaper than the next. The expensive one only sees what survived the cheap one.
- 01
Direction
A brief: product, audience, geo, languages and a spending cap. Data, not code — a new direction needs no deploy.
- 02
Queries
Human phrasings, model expansion and the demand layer: frequencies, search suggestions, dynamics.
- 03
Channels
Native in-platform search for communities, screening by topic and activity, a funnel from candidate to working source.
- 04
Crawl
Incremental, cursor-based, at a speed matching account health. Pauses always jittered.
- 05
Cascade
Rules, embeddings, reranker, language model in batches. The expensive layer only sees survivors.
- 06
Signals
Pain, intent, complaint, trend — scored, with author and channel. Your marking feeds back into queries.
Own stack instead of subscriptions
Every paid piece replaced by an open or self-hosted one. Where there is no replacement, it is stated plainly.
| Usually bought | Ours |
|---|---|
| SERP API | self-hosted metasearch across dozens of engines |
| Telegram analytics | official client and our own accounts |
| forum archives | open archives and official APIs |
| contact databases | open traces in public profiles |
| keyword services | frequencies, suggestions, dynamics |
| per-token embeddings and models | local models on our own card |
| residential addresses | our own egress farm |
What does not come free: one search engine closed its feed and now charges for it, one video platform bans commercial use of its research access, private profiles are unreachable by design. That is the state of the market, not a gap in the build.
Control room, not a script runner
Channels, accounts and egress points are objects with state, limits and a recorded reason for every transition.
Accounts and egress
An account is pinned to one address for good: changing it reads as a login from a new device. Warm-up, daily limits, speed modes.
Leased jobs
A worker pulls work itself and extends the lease. The machine dies — the job returns to the queue with no external watchdog.
Visible failures
A success code with a stub body is caught separately. Data off-schema goes to quarantine, not to the table.
Collection boundaries
- Public messages in open communities only.
- Closed groups, private messages and private profiles are never touched.
- Minimum is stored: public handle, link, message, community metrics.
- Contacts are encrypted and kept only when needed for outreach.