Écoute sociale : comparatif

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

  • Litehook

    Dernière vérification des sources : 10 nov. 2026

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

  • Obsei

    Dernière vérification des sources : 10 nov. 2026

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

Ce que les sources établissent

Une lecture de la documentation officielle vérifiée pour Litehook 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
2 critères
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
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/.
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.
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.
Obsei The README lists alerts on theme spikes, new themes, digests, the review queue and pipeline health.

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.
  • 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 : Litehook : canaux; Obsei : 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.
ExigenceLitehookObsei
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

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

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

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

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.

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é Litehook: 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 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 Obsei 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 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.