Écoute sociale : comparatif

looot-mentions vs Obsei

Prix, fonctionnalités documentées et limites issus de sources officielles datées, côte à côte. Les inconnues restent inconnues ; des unités de facturation différentes ne permettent pas de comparer directement les coûts.

Ce que les sources établissent

Une lecture de la documentation officielle vérifiée pour looot-mentions et Obsei. Ce n’est ni un test pratique, ni un classement, ni la recommandation d’un produit.

Questions d’achat traitées pour les deux
0 critère
Documenté pour un seul
1 critère
Non vérifié pour aucun
1 critère
Prix
Pas encore comparables

Prix

Aucune comparaison de prix complète à conditions égales n’est encore établie ; les prochaines étapes indiquent ce qui manque.

Documenté en termes non confirmés

Ces données peuvent décrire des mesures, marchés, langues ou périmètres différents. Vérifiez chaque offre, unité et période avant de les comparer.

Responsabilité de l’hébergement
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.
Analyse
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.
Alertes et diffusion
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.

Limites à vérifier

  • 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.

Pas encore vérifié

Aucune source vérifiée pour l’un ou l’autre produit sur : historique conservé.

Documenté pour un seul produit, voir le tableau ci-dessous : looot-mentions : canaux.

« Non vérifié » signifie que nos sources vérifiées ne l’établissent pas. Cela ne veut pas dire qu’un produit n’a pas la fonctionnalité ni qu’il est gratuit.

Preuves côte à côte

Valeurs documentées avec leurs sources et dates de vérification ; les exigences que les sources n’établissent pas restent signalées.

  • Documenté comme pris en charge
  • Documenté comme non pris en charge
  • Non vérifié Les sources ne l’établissent pas
  • Sans objet
Périmètre et limites documentés ; les critères non vérifiés restent inconnus.
Exigencelooot-mentionsObsei
Tarifs
Offre gratuite · prix payants non vérifiés

Offre gratuite · prix payants non vérifiés

Pour qui
The project describes brand and keyword listening that searches through looot.

Vérifié le 4 nov. 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.

Vérifié le 8 nov. 2026 · Obsei: obsei-project

Limites de couverture
The captured documentation says a real run needs a funded looot balance; provider terms and charges are separate.

Vérifié le 4 nov. 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.

Vérifié le 8 nov. 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.
Canaux
In the author’s 13 October 2026 live-run account, X, YouTube, Instagram and News parsers remained unverified against real answers.

Vérifié le 4 nov. 2026 · looot-mentions: looot-mentions-readme

Non vérifié
Responsabilité de l’hébergement
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.

Vérifié le 10 nov. 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.

Vérifié le 10 nov. 2026 · Obsei: obsei-project

Analyse
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.

Vérifié le 10 nov. 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.

Vérifié le 10 nov. 2026 · Obsei: obsei-project

Alertes et diffusion
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.

Vérifié le 10 nov. 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.

Vérifié le 10 nov. 2026 · Obsei: obsei-project

Note de couverture

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 exigence sans preuve vérifiée ici

Non vérifié signifie que les sources examinées ne l’établissent pas ; cela ne veut pas dire que le produit en est dépourvu ni que c’est gratuit.

  • Historique conservé looot-mentions: non vérifié · Obsei: non vérifié

Prochaines étapes

  • Vérifiez les prix des offres payantes, la durée de facturation et les taxes de looot-mentions sur sa page de tarifs officielle ; seule son offre gratuite est vérifiée ici.
  • Vérifiez les prix des offres payantes, la durée de facturation et les taxes de Obsei sur sa page de tarifs officielle ; seule son offre gratuite est vérifiée ici.
  • Interrogez looot-mentions sur ce point : historique conservé. Nos sources ne l’établissent pas encore.
  • Interrogez Obsei sur ces points : historique conservé et canaux. Nos sources ne les établissent pas encore.

Les commissions ne modifient jamais les coûts, l’éligibilité ni l’ordre.