Escucha social: comparación

Litehook vs ThreadRadar

Precios, funciones documentadas y límites de fuentes oficiales fechadas, lado a lado. Lo desconocido sigue siendo desconocido; con unidades de facturación distintas no se pueden comparar los costes directamente.

Qué responden las fuentes

Una lectura de la documentación oficial revisada de Litehook y ThreadRadar. No es una prueba práctica, una clasificación ni la recomendación de un producto.

Preguntas de compra respondidas para ambos
1 requisito
Documentado solo para uno
1 requisito
Sin verificar para ninguno
1 requisito
Precios
Aún no comparables

Precio

Aún no hay una comparación de precios completa en igualdad de condiciones; los próximos pasos indican qué falta.

Preguntas de compra respondidas para ambos

Aunque las etiquetas coincidan, revisa en cada fuente las diferencias de planes, unidades y alcance.

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

Documentado en términos no confirmados

Estos datos pueden describir medidas, mercados, idiomas o alcances distintos. Revisa cada plan, unidad y periodo antes de compararlos.

Responsable del alojamiento
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/.
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.
Alertas y entrega
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.
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.

Límites que revisar

  • 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.
  • ThreadRadar The project says its first check establishes a baseline and does not alert; later alerts use the documented change rules.

Aún sin verificar

No hay fuentes revisadas para ninguno de los productos sobre: historial conservado.

Documentado solo para un producto, en la tabla de abajo: ThreadRadar: análisis.

«Sin verificar» significa que nuestras fuentes revisadas no lo establecen. No significa que a un producto le falte la función ni que no cueste nada.

Evidencia lado a lado

Valores documentados con sus fuentes y fechas de comprobación; los requisitos que las fuentes no establecen quedan marcados.

  • Documentado como compatible
  • Documentado como no compatible
  • Sin verificar Las fuentes no lo establecen
  • No aplica
Alcance y límites documentados; las dimensiones sin verificar siguen como desconocidas.
RequisitoLitehookThreadRadar
Precios
Plan gratuito · precios de pago sin verificar

Plan gratuito · precios de pago sin verificar

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

Comprobado el 8 nov 2026 · Litehook: litehook-project

ThreadRadar describes a self-hosted topic monitor for public conversations that compares scheduled checks and links to relevant threads.

Comprobado el 4 nov 2026 · ThreadRadar: threadradar-source

Límites de cobertura
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.

Comprobado el 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 project says its first check establishes a baseline and does not alert; later alerts use the documented change rules.

Comprobado el 4 nov 2026 · ThreadRadar: threadradar-source

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

Comprobado el 10 nov 2026 · Litehook: litehook-project

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.

Comprobado el 11 nov 2026 · ThreadRadar: threadradar-project

Responsable del alojamiento
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.

Comprobado el 10 nov 2026 · Litehook: litehook-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.

Comprobado el 11 nov 2026 · ThreadRadar: threadradar-project

AnálisisSin verificar
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.

Comprobado el 11 nov 2026 · ThreadRadar: threadradar-project

Alertas y entrega
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.

Comprobado el 10 nov 2026 · Litehook: litehook-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.

Comprobado el 11 nov 2026 · ThreadRadar: threadradar-project

Nota de cobertura

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 requisito sin evidencia revisada aquí

Sin verificar significa que las fuentes revisadas no lo establecen; no significa que el producto no lo tenga ni que no cueste nada.

  • Historial conservado Litehook: sin verificar · ThreadRadar: sin verificar

Próximos pasos

  • Confirma los precios de los planes de pago, el plazo de facturación y los impuestos de Litehook en su página oficial de precios; aquí solo está verificado su plan gratuito.
  • Confirma los precios de los planes de pago, el plazo de facturación y los impuestos de ThreadRadar en su página oficial de precios; aquí solo está verificado su plan gratuito.
  • Pregunta a Litehook por estos puntos: historial conservado y análisis. Nuestras fuentes aún no los confirman.
  • Pregunta a ThreadRadar por este punto: historial conservado. Nuestras fuentes aún no lo confirman.

Las comisiones nunca cambian los costes, la idoneidad ni el orden.