Horus

FAQ

Frequently asked questions

Answers about Horus — open-source incident investigation, read-only connectors, supported data sources, observability vs reconstruction, AI coding agents, and installation.

  • Horus is an open-source, local-first incident investigation tool. It connects runtime evidence — logs, metrics, queue state, database snapshots — with source-code intelligence to produce deterministic investigation reports your team and AI agents can act on.
  • No. Horus is read-only. Connectors gather evidence from Elasticsearch, Grafana, MongoDB, BullMQ, and other sources without modifying anything in your environment.
  • Elasticsearch, Grafana, Axiom, Sentry, MongoDB, PostgreSQL, BullMQ, git changes, and Horus source intelligence (TypeScript, JavaScript, and Python code graphs). More connectors — including Kubernetes and distributed traces — are in progress.
  • Dashboards show signals. Horus reconstructs what happened — correlating evidence, ranking hypotheses, building a timeline, and producing a structured report with suspected causes, gaps, and next actions.
  • Yes. Horus reports give agents grounded project context — evidence-backed causes and gaps instead of guesses. Optional --ai adds an Anthropic narrative on top of the deterministic engine output.
  • Yes. Horus is open source and installable today via the curl installer or Homebrew. See the getting started guide or the GitHub repository.