Local execution.Shared evidence.
Horus CLI runs on your machine, close to your code and runtime. Horus Cloud gives your team one place to search every investigation, evidence trail, agent run, log snippet, and code context.
Cloud does not run investigations. The CLI is the executor.
Missed call sync delay
claude-code
agent run · 04m 12s
The model
Designed around a clean boundary
The CLI works where your code and runtime live. Cloud keeps what the team needs after the investigation.
Horus CLI
The local executor
Runs on your machine, reads local repository context, executes investigations, gathers evidence, and pushes selected results to Cloud when you choose.
Local pipeline
- Runs near your code and runtime
- Collects logs, queues, metrics, state, and source context
- Executes agent workflows locally
- Pushes investigation output on demand
Horus Cloud
The collaboration layer
Stores investigation history, evidence, source references, and agent runs so your team can search, inspect, and reuse what was already found.
Team memory
- Searchable investigation history
- Shared evidence and source context
- Agent run history
- Workspace and repository views
What gets synced
Everything your team needs after the investigation
Cloud turns local investigation output into a searchable team memory.
Investigations
Every CLI investigation with timeline, summary, status, and linked evidence.
Evidence
Logs, queue snapshots, metrics, database state, file paths, symbols, and structured findings.
Agent runs
Execution history from agents: what ran, when, what it found, and what changed.
Repositories
Repository context connected to each investigation.
Audit & security
Membership changes, token lifecycle, access events, and evidence upload history.
CLI integration
Device login, CLI tokens, and repository sync status.
How it works
From CLI to team memory in three steps
Run locally
Sign in, select the Cloud repository, then run Horus investigations on your machine.
horus loginhorus context use acme/web/leadcallhorus investigate "missed calls are not syncing to Zoho"Sync to Cloud
The CLI uploads investigation results, evidence, source references, and agent run metadata to your team workspace.
horus cloud sync ✓ 42 evidence items✓ 1 agent run✓ synced 2m agoInspect together
Your team can browse investigations, search evidence, open source references, and review agent execution history.
# open in your browsercloud.horus.sh/ meritt-dev/leadcallSecurity & trust
Your evidence stays scoped to your team
Horus Cloud is built around workspace boundaries, role-based access, CLI token lifecycle, and audit trails.
Evidence scope
Tenant isolation
Evidence is scoped to your organization, workspace, and repository.
Role-based access
Owner, admin, and member roles control access to team data.
CLI token lifecycle
Tokens can be created, revoked, consumed, and audited.
Audit trail
Important membership, access, token, and upload events are recorded.
Ready to make investigations searchable?
Create a workspace, connect your first repository, and give your team one place to inspect what Horus found.
Cloud does not run investigations. Horus CLI is the executor.