Escucha social: comparación

Litehook vs looot-mentions

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

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

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

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: looot-mentions: 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.
RequisitoLitehooklooot-mentions
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

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

Comprobado el 4 nov 2026 · looot-mentions: looot-mentions-readme

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 captured documentation says a real run needs a funded looot balance; provider terms and charges are separate.

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

In the author’s 13 October 2026 live-run account, X, YouTube, Instagram and News parsers remained unverified against real answers.

Comprobado el 4 nov 2026 · looot-mentions: looot-mentions-readme

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

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.

Comprobado el 10 nov 2026 · looot-mentions: looot-mentions-project

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

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

Comprobado el 10 nov 2026 · looot-mentions: looot-mentions-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 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 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 · looot-mentions: 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 looot-mentions 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 looot-mentions por este punto: historial conservado. Nuestras fuentes aún no lo confirman.

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