Argus documentation
Operate a self-hosted, revisioned data layer for X, public Telegram announcements, and the Web.
Argus continuously collects public signals, stores canonical records and their revisions, and exposes deterministic queries with source links. Optional summaries are derived artifacts; ingestion and storage do not depend on an LLM.
Choose your path
- New operator: run the quick start.
- Existing operator: open operations or troubleshooting.
- Agent: use the machine-readable interfaces.
- Contributor: start with the contributor guide.
Supported in v1
| Area | Current capability |
|---|---|
| Public sources | X accounts and queries through FxEmbed, public Telegram announcements, and Web URLs, feeds, and SearXNG-backed queries. |
| Storage | SQLite for a single all-in-one runtime, or PostgreSQL for shared multi-role deployments. |
| Scheduling and query | Cron-derived target jobs, leased workers, retries and checkpoints, plus authenticated deterministic record and artifact queries. |
| Optional intelligence | OpenRouter-backed sourced summaries stored separately as artifacts. |
| Deployment | Signed release installation on a supported VPS Docker host, with Argus-managed Docker Compose and private, optional SearXNG and FxEmbed services. |
| Runtime boundaries | API, scheduler, worker, and processor responsibilities can run together; SQLite requires the combined role while PostgreSQL supports separated roles. |
Product boundary
Argus does not access private Telegram conversations, bypass site controls, or require an LLM for deterministic ingestion and querying.