Social listening comparison

looot-mentions vs Obsei

Prices, documented capabilities and limits from dated official sources, side by side. Unknowns remain unknown; different billing units do not establish a cost winner.

What the evidence answers

A reading of reviewed official documentation for looot-mentions and Obsei. 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

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
looot-mentions The README says the web UI stores its data in a local file, so it should run on a machine with a disk (npm run build and npm start), and that the supported hosted setup is a daily GitHub Actions run.
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.
Analysis and scoring
looot-mentions The README says sentiment (positive, neutral, negative) is tagged with editable word lists that show the words behind each label, and intent (complaint, question, recommendation request, comparison) with editable patterns.
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.
Alerts and delivery
looot-mentions The README describes a daily digest grouped as Needs a reply (complaints, questions, recommendation requests), comparisons and everything else, with unanswered sources listed at the bottom.
Obsei The README lists alerts on theme spikes, new themes, digests, the review queue and pipeline health.

Limits to check

  • looot-mentions The captured documentation says a real run needs a funded looot balance; provider terms and charges are separate.
  • looot-mentions The README sets a default cap of $0.25 per run and period budgets of $10 a day and $50 a month, which the owner can change, and refuses a call that would pass them.
  • 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.

Not verified yet

No reviewed evidence for either product on history kept.

Documented for one product only, shown in the table below: looot-mentions: 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
Documented scope and limits; unverified dimensions remain unknown.
Requirementlooot-mentionsObsei
Pricing
Free plan · paid prices not verified

Free plan · paid prices not verified

Who it is for
The project describes brand and keyword listening that searches through looot.

Verified Nov 4, 2026 · looot-mentions: looot-mentions-readme

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

Coverage limits
The captured documentation says a real run needs a funded looot balance; provider terms and charges are separate.

Verified Nov 4, 2026 · looot-mentions: looot-mentions-readme

  • Self-hosted The README sets a default cap of $0.25 per run and period budgets of $10 a day and $50 a month, which the owner can change, and refuses a call that would pass them.
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

  • Self-hosted 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.
Channels
In the author’s 13 October 2026 live-run account, X, YouTube, Instagram and News parsers remained unverified against real answers.

Verified Nov 4, 2026 · looot-mentions: looot-mentions-readme

Not verified
Hosting responsibility
The README says the web UI stores its data in a local file, so it should run on a machine with a disk (npm run build and npm start), and that the supported hosted setup is a daily GitHub Actions run.

Dated publisher project README (repository head 80dce941, after release v0.1.6) captured on 9 November 2026; supplier description, not a deployment or independent test. The README requires Node 22.13 or newer. Rate-limit and lockout counters live in memory in one process. No deployment was tested.

Verified Nov 10, 2026 · looot-mentions: looot-mentions-project

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

Analysis and scoring
The README says sentiment (positive, neutral, negative) is tagged with editable word lists that show the words behind each label, and intent (complaint, question, recommendation request, comparison) with editable patterns.

Dated publisher project README (repository head 80dce941, after release v0.1.6) captured on 9 November 2026; supplier description, not a deployment or independent test. The README itself says word-list sentiment misses sarcasm and should be treated as a first pass. Accuracy was not tested.

Verified Nov 10, 2026 · looot-mentions: looot-mentions-project

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

Alerts and delivery
The README describes a daily digest grouped as Needs a reply (complaints, questions, recommendation requests), comparisons and everything else, with unanswered sources listed at the bottom.

Dated publisher project README (repository head 80dce941, after release v0.1.6) captured on 9 November 2026; supplier description, not a deployment or independent test. The README lists alerts on volume spikes among features it dropped. Delivery from the daily GitHub Actions run was not tested.

Verified Nov 10, 2026 · looot-mentions: looot-mentions-project

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

Coverage note

Publisher repository at an exact dated commit; project description and author-reported checks are not independent tests. Provider accounts, funds, source access and applicable third-party terms are separate. No recurring acquisition or paid request.

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.

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 looot-mentions: not verified · Obsei: not verified

Next steps

  • Confirm looot-mentions's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Confirm Obsei's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Ask looot-mentions about history kept; our sources do not establish it yet.
  • Ask Obsei about history kept and channels; our sources do not establish them yet.

Commissions never change costs, eligibility or rankings.

looot-mentions vs Obsei: pricing, capabilities and limits