Social listening comparison
Obsei vs ThreadRadar
Prices, documented capabilities and limits from dated official sources, side by side. Unknowns remain unknown; different billing units do not establish a cost winner.
Latest evidence check Nov 10, 2026
Who it is forobsei is a self-hosted tool for teams that want to understand what customers say in reviews, tickets, calls and surveys without sending that text to another SaaS or a public LLM.
Latest evidence check Nov 11, 2026
Who it is forThreadRadar describes a self-hosted topic monitor for public conversations that compares scheduled checks and links to relevant threads.
What the evidence answers
A reading of reviewed official documentation for Obsei and ThreadRadar. It is not a hands-on test, a ranking or a recommendation of one product.
- Common buyer questions answered
- 0 requirements
- Documented for one
- 1 requirement
- Not verified for either
- 1 requirement
- Prices
- Not like-for-like yet
Price
Obsei
Free plan · paid prices not verified ·
- Self-hosted: no subscription charge ·
ThreadRadar
Free plan · paid prices not verified ·
- Self-hosted: no subscription charge ·
A complete like-for-like price comparison is not established; the next steps say what is missing.
Documented in unconfirmed terms
These facts may describe different measures, markets, languages or scopes. Check each plan, unit and period before comparing them.
- Hosting responsibility
- Obsei The README documents a container image on the GitHub Container Registry, tagged by release and run against a project directory, with the database key read from .obsei/secrets.env or passed as an environment variable.
- ThreadRadar ThreadRadar requires uv, which fetches Python 3.11+ itself; the README says to open http://127.0.0.1:8787, and data is stored in the user data directory.
- Analysis and scoring
- Obsei The README lists classification with an in-process zero-shot model by default, a decision model or an LLM, labelling sentiment, intent, language and custom fields with confidence; low-confidence answers go to a stronger model or human review.
- ThreadRadar ThreadRadar scores each conversation from visible engagement (replies × 3 + reactions + reshares × 2) and age, using a freshness decay of exp(-age_hours / 36).
- Alerts and delivery
- Obsei The README lists alerts on theme spikes, new themes, digests, the review queue and pipeline health.
- ThreadRadar The README says alerts appear in the app only; email, Slack and Discord delivery, an alerts inbox across topics, desktop notifications and per-topic include and exclude terms are not built yet.
Limits to check
- Obsei The README lists built-in sources including App Store, Google Play, helpdesks, GitHub issues, Hacker News, Bluesky, YouTube and RSS; Reddit is offered only as an unpublished community plugin installed from Git.
- Obsei The README says obsei provides controls that support compliance with laws such as the GDPR, India’s DPDP Act, Brazil’s LGPD and California’s CCPA, makes no compliance claims, and leaves the operator as the data controller.
- ThreadRadar The project says its first check establishes a baseline and does not alert; later alerts use the documented change rules.
Not verified yet
No reviewed evidence for either product on history kept.
Documented for one product only, shown in the table below: ThreadRadar: channels.
Not verified means our reviewed sources do not establish it. It does not mean a product lacks the capability or that it costs nothing.
Side-by-side evidence
Documented values with their sources and check dates; requirements the sources do not establish stay marked.
- Documented as supported
- Documented as unsupported
- Not verified Sources do not establish it
- Not applicable
| Requirement | Obsei | ThreadRadar |
|---|---|---|
| Pricing | Free plan · paid prices not verified | Free plan · paid prices not verified |
| Who it is for | obsei is a self-hosted tool for teams that want to understand what customers say in reviews, tickets, calls and surveys without sending that text to another SaaS or a public LLM. Verified Nov 8, 2026 · Obsei: obsei-project | ThreadRadar describes a self-hosted topic monitor for public conversations that compares scheduled checks and links to relevant threads. Verified Nov 4, 2026 · ThreadRadar: threadradar-source |
| Coverage limits | The README lists built-in sources including App Store, Google Play, helpdesks, GitHub issues, Hacker News, Bluesky, YouTube and RSS; Reddit is offered only as an unpublished community plugin installed from Git. Verified Nov 8, 2026 · Obsei: obsei-project
| The project says its first check establishes a baseline and does not alert; later alerts use the documented change rules. Verified Nov 4, 2026 · ThreadRadar: threadradar-source |
| Channels | Not verified | Reddit is available only with the operator’s own Reddit API app credentials; the adapter ships without credentials, and Reddit limits free use of its Data API to non-commercial purposes. Publisher README at a pinned repository revision, captured 9 November 2026; supplier description, not a test. Other sources are listed as public endpoints needing no credentials, with optional tokens or keys for some; YouTube needs an API key. Current third-party API terms were not checked. Verified Nov 11, 2026 · ThreadRadar: threadradar-project |
| Hosting responsibility | The README documents a container image on the GitHub Container Registry, tagged by release and run against a project directory, with the database key read from .obsei/secrets.env or passed as an environment variable. Dated publisher project README (release v1.1.1) captured on 9 November 2026; supplier description, not a deployment or independent test. The README also describes installing the obsei command with uvx, uv tool or pip, and a server mode (obsei serve) for scheduled pipelines, webhooks, MCP and Studio. No installation, capacity or operations testing was performed. Verified Nov 10, 2026 · Obsei: obsei-project | ThreadRadar requires uv, which fetches Python 3.11+ itself; the README says to open http://127.0.0.1:8787, and data is stored in the user data directory. Publisher README at a pinned repository revision, captured 9 November 2026; a Docker image build is also described. The local mode has no authentication and binds to loopback only, and the scheduler runs only while the process runs. No installation or capacity test was performed. Verified Nov 11, 2026 · ThreadRadar: threadradar-project |
| Analysis and scoring | The README lists classification with an in-process zero-shot model by default, a decision model or an LLM, labelling sentiment, intent, language and custom fields with confidence; low-confidence answers go to a stronger model or human review. Dated publisher project README (release v1.1.1) captured on 9 November 2026; supplier description, not a deployment or independent test. Classification accuracy, model behaviour and any model-provider charges were not tested. Verified Nov 10, 2026 · Obsei: obsei-project | ThreadRadar scores each conversation from visible engagement (replies × 3 + reactions + reshares × 2) and age, using a freshness decay of exp(-age_hours / 36). Publisher README at a pinned repository revision, captured 9 November 2026; the scoring formula is the publisher’s description and was not independently verified. The README also says the project uses no language model. Verified Nov 11, 2026 · ThreadRadar: threadradar-project |
| Alerts and delivery | The README lists alerts on theme spikes, new themes, digests, the review queue and pipeline health. Dated publisher project README (release v1.1.1) captured on 9 November 2026; supplier description, not a deployment or independent test. The Sinks row of the README lists signed webhooks, Slack, Telegram, Discord, email and Teams via Apprise (obsei[notify]), GitHub issues, Jira, Linear, Parquet and SQL databases and warehouses. Delivery, permissions and reliability were not tested. Verified Nov 10, 2026 · Obsei: obsei-project | The README says alerts appear in the app only; email, Slack and Discord delivery, an alerts inbox across topics, desktop notifications and per-topic include and exclude terms are not built yet. Publisher README at a pinned repository revision, captured 9 November 2026; version 0.3 beta status, which can change. No alert was triggered or delivered in testing. Verified Nov 11, 2026 · ThreadRadar: threadradar-project |
| Coverage note | Dated publisher project README captured on 7 November 2026; supplier description, not a deployment or independent test. Infrastructure, accounts, third-party services and managed offerings have separate costs and terms. | Publisher README at the captured repository revision, 4 November 2026. No service, installation, integration, monitoring or security test performed; source use is one-time factual paraphrase. |
1 requirement without reviewed evidence here
Not verified means the reviewed sources do not establish it; it does not mean a product lacks it or that it costs nothing.
- History kept Obsei: not verified · ThreadRadar: not verified
Next steps
- Confirm Obsei's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
- Confirm ThreadRadar's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
- Ask Obsei about history kept and channels; our sources do not establish them yet.
- Ask ThreadRadar about history kept; our sources do not establish it yet.
- ObseiVisit ObseiProfile and plans
- ThreadRadarVisit ThreadRadarProfile and plans
Commissions never change costs, eligibility or rankings.