HorusUse case
Give your engineering team shared investigation memory
Horus Cloud syncs investigations, evidence, and agent runs across your team so debugging knowledge is reusable and auditable — not trapped in one engineer's terminal.
When one engineer debugs an incident locally, the reasoning leaves with them. Horus Cloud syncs investigations, evidence, and agent runs across the team so that knowledge becomes shared, searchable, and reusable.
The problem: investigation knowledge is siloed
- Findings live in one person's terminal, scrollback, or memory.
- The next incident repeats the same digging from scratch.
- There's no shared record of what was checked, found, or ruled out.
Shared, reusable investigations
The CLI runs investigations locally and syncs the results to Horus Cloud, where the whole team can browse them. Past investigations become a starting point instead of lost context.
Organized the way teams work
Horus Cloud structures everything as Organization → Workspace → Repository, with the core flow Repository → Investigation → Evidence → Agent Run.
| Level | What it holds |
|---|---|
| Organization | Your team and its members |
| Workspace | A product or system area |
| Repository | A codebase and its synced investigations |
| Investigation | An incident's evidence, timeline, and agent runs |
Evidence and agent runs everyone can see
- Evidence is captured with each investigation and viewable by the team.
- Agent runs are recorded, so work an AI agent already did is reusable and auditable.
- New teammates can read past investigations instead of starting cold.
Local-first, synced to Cloud
The CLI gathers evidence and runs agents locally; only the results sync to Horus Cloud. Cloud never connects to your runtime.
Getting your team on Horus
Install the CLI and run your first investigation, then sign in to Horus Cloud to share it with your team. Start with the getting started guide.