Écoute sociale : comparatif

Litehook vs looot-mentions

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 Litehook et looot-mentions. Ce n’est ni un test pratique, ni un classement, ni la recommandation d’un produit.

Questions d’achat traitées pour les deux
1 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.

Questions d’achat traitées pour les deux

Même quand les libellés concordent, vérifiez dans chaque source les différences d’offres, d’unités et de périmètre.

Canaux
Litehook The README says Litehook scrapes public Telegram channels at a set interval without authorisation, or authenticates with a user account to reach direct messages and private channels, and sends a webhook when a post is new.
looot-mentions In the author’s 13 October 2026 live-run account, X, YouTube, Instagram and News parsers remained unverified against real answers.

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
Litehook The README quick start is a Docker Compose service using the ghcr.io/tensake/litehook image, port 4101, a ./data volume and a WEBHOOK_SECRET variable; docker compose up -d starts it and the dashboard opens at http://localhost:4101/.
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.
Alertes et diffusion
Litehook The README says webhooks go out by POST, the receiving server must return a 2xx status, a failed delivery is retried 4 more times at 1 second intervals, the data stays in the database if every retry fails, and each request carries an x-secret header with the configured webhook secret.
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.

Limites à vérifier

  • Litehook Litehook lists one platform, Telegram, supported either by scraping public channels or by a self-bot that can also reach private channels and direct messages.
  • Litehook The README says Litehook can use a SOCKS5 proxy list set through the PROXY_LIST_URL variable and warns that a proxy can be slow and time out the HTTP request.
  • 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.

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 : analyse.

« 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.
ExigenceLitehooklooot-mentions
Tarifs
Offre gratuite · prix payants non vérifiés

Offre gratuite · prix payants non vérifiés

Pour qui
Litehook is a self-hosted social media monitoring tool and webhook server with a web dashboard, HTTP API, Docker deployment and SOCKS proxy support.

Vérifié le 8 nov. 2026 · Litehook: litehook-project

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

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

Limites de couverture
Litehook lists one platform, Telegram, supported either by scraping public channels or by a self-bot that can also reach private channels and direct messages.

Vérifié le 8 nov. 2026 · Litehook: litehook-project

  • Self-hosted The README says Litehook can use a SOCKS5 proxy list set through the PROXY_LIST_URL variable and warns that a proxy can be slow and time out the HTTP request.
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.
Canaux
The README says Litehook scrapes public Telegram channels at a set interval without authorisation, or authenticates with a user account to reach direct messages and private channels, and sends a webhook when a post is new.

Dated publisher project README (release v3.1.3, commit 8bc5c33d) captured on 9 November 2026; supplier description, not a deployment or independent test. Telegram is the only platform in the README feature table. The permitted use of Telegram data and of user-account access was not assessed.

Vérifié le 10 nov. 2026 · Litehook: litehook-project

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

Responsabilité de l’hébergement
The README quick start is a Docker Compose service using the ghcr.io/tensake/litehook image, port 4101, a ./data volume and a WEBHOOK_SECRET variable; docker compose up -d starts it and the dashboard opens at http://localhost:4101/.

Dated publisher project README (release v3.1.3, commit 8bc5c33d) captured on 9 November 2026; supplier description, not a deployment or independent test. Deployment was not tested. Sizing and production hardening are not described.

Vérifié le 10 nov. 2026 · Litehook: litehook-project

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

AnalyseNon vérifié
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

Alertes et diffusion
The README says webhooks go out by POST, the receiving server must return a 2xx status, a failed delivery is retried 4 more times at 1 second intervals, the data stays in the database if every retry fails, and each request carries an x-secret header with the configured webhook secret.

Dated publisher project README (release v3.1.3, commit 8bc5c33d) captured on 9 November 2026; supplier description, not a deployment or independent test. Webhook delivery was not tested; the README has no email or chat-app alert channel.

Vérifié le 10 nov. 2026 · Litehook: litehook-project

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

Note de couverture

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

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é Litehook: non vérifié · looot-mentions: non vérifié

Prochaines étapes

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

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