Social listening comparison

Litehook vs looot-mentions

Prices, documented capabilities and limits from dated official sources, side by side. Unknowns remain unknown; different billing units do not establish a cost winner.

What the evidence answers

A reading of reviewed official documentation for Litehook and looot-mentions. It is not a hands-on test, a ranking or a recommendation of one product.

Common buyer questions answered
1 requirement
Documented for one
1 requirement
Not verified for either
1 requirement
Prices
Not like-for-like yet

Price

A complete like-for-like price comparison is not established; the next steps say what is missing.

Common buyer questions answered

Even when labels match, check each source for differences in plans, units and scope.

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

Documented in unconfirmed terms

These facts may describe different measures, markets, languages or scopes. Check each plan, unit and period before comparing them.

Hosting responsibility
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.
Alerts and delivery
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.

Limits to check

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

Not verified yet

No reviewed evidence for either product on history kept.

Documented for one product only, shown in the table below: looot-mentions: analysis and scoring.

Not verified means our reviewed sources do not establish it. It does not mean a product lacks the capability or that it costs nothing.

Side-by-side evidence

Documented values with their sources and check dates; requirements the sources do not establish stay marked.

  • Documented as supported
  • Documented as unsupported
  • Not verified Sources do not establish it
  • Not applicable
Documented scope and limits; unverified dimensions remain unknown.
RequirementLitehooklooot-mentions
Pricing
Free plan · paid prices not verified

Free plan · paid prices not verified

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

Verified Nov 8, 2026 · Litehook: litehook-project

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

Verified Nov 4, 2026 · looot-mentions: looot-mentions-readme

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

Verified Nov 8, 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.

Verified Nov 4, 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.
Channels
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.

Verified Nov 10, 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.

Verified Nov 4, 2026 · looot-mentions: looot-mentions-readme

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

Verified Nov 10, 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.

Verified Nov 10, 2026 · looot-mentions: looot-mentions-project

Analysis and scoringNot verified
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.

Verified Nov 10, 2026 · looot-mentions: looot-mentions-project

Alerts and delivery
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.

Verified Nov 10, 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.

Verified Nov 10, 2026 · looot-mentions: looot-mentions-project

Coverage note

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 requirement without reviewed evidence here

Not verified means the reviewed sources do not establish it; it does not mean a product lacks it or that it costs nothing.

  • History kept Litehook: not verified · looot-mentions: not verified

Next steps

  • Confirm Litehook's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Confirm looot-mentions's paid plan prices, billing term and taxes on its official pricing page; only its free plan is verified here.
  • Ask Litehook about history kept and analysis and scoring; our sources do not establish them yet.
  • Ask looot-mentions about history kept; our sources do not establish it yet.

Commissions never change costs, eligibility or rankings.