Administration

Running ARGUS day to day: the clusters it watches, who may do what, what it connects out to, and what it keeps.

• Clusters — enrolling, accepting, states, and removing a cluster.
• Users and roles — accounts, roles and the scope a grant applies to.
• Single sign-on — sign in with your own identity provider, and map its groups to ARGUS roles.
• AI providers — configuring providers and switching between them.
• Model pricing and spend — making cost visible and bounding it.
• Git repositories — where ARGUS may propose pull requests.
• Outbound access — naming the internal model and Git servers ARGUS may reach.
• AI tools and tokens — using ARGUS from Claude Code, Cursor or VS Code with a personal token.
• Detector settings — controlling what becomes an incident.
• Data retention — how long history is kept.
• Insights — fleet-wide patterns across incidents and findings.
• Audit log — the hash-chained record of consequential actions.