Social listening comparison

Litehook vs OpenMagpie

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 OpenMagpie. It is not a hands-on test, a ranking or a recommendation of one product.

Common buyer questions answered
1 requirement
Documented for one
2 requirements
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.
OpenMagpie The project lists X, YouTube, Reddit, Hacker News and RSS or Atom as sources.

Documented in unconfirmed terms

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

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.
OpenMagpie The publisher describes delivering matches to a webhook or logs.

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.
  • OpenMagpie The project says its user interface and hosted version are planned.

Not verified yet

No reviewed evidence for either product on history kept.

Documented for one product only, shown in the table below: Litehook: hosting responsibility; OpenMagpie: 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.
RequirementLitehookOpenMagpie
Pricing
Free plan · paid prices not verified

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

A self-hostable application that uses a model supplied by the operator.

Project documentation captured 3 November 2026. Source-specific access, current provider terms and required credentials must be checked. No monitoring, account connection, model or integration was run.

Verified Nov 3, 2026 · OpenMagpie: openmagpie-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 project says its user interface and hosted version are planned.

Current README description, not a promise of release timing or a currently available hosted plan.

Verified Nov 3, 2026 · OpenMagpie: openmagpie-readme

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

The project lists X, YouTube, Reddit, Hacker News and RSS or Atom as sources.

Supplier source list, not proof of complete coverage or access; provider credentials, platform rules and geographic availability vary. No source was queried.

Verified Nov 3, 2026 · OpenMagpie: openmagpie-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

Not verified
Analysis and scoringNot verified
The publisher describes an operator-supplied model scoring posts against a natural-language relevance description.

Dated publisher documentation; relevance accuracy, model behavior and performance were not tested.

Verified Nov 5, 2026 · OpenMagpie: openmagpie-readme

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 publisher describes delivering matches to a webhook or logs.

Dated publisher documentation; delivery, permissions, reliability and third-party services were not tested.

Verified Nov 5, 2026 · OpenMagpie: openmagpie-readme

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.

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 · OpenMagpie: 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 OpenMagpie'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 OpenMagpie about history kept and hosting responsibility; our sources do not establish them yet.

Commissions never change costs, eligibility or rankings.