Auto-classify severity
Drop an incident in. Argus reads the title and description, labels it P1–P4, and tags the systems affected — before anyone gets paged.
"Checkout 503s climbing" → P1 · payments-api · customer-facing
Argus tracks incidents, changes, on-call, and postmortems with AI classification, similar-incident search, drafted postmortems, and plain-English search. Audit trail on every entity.
Not a chatbot bolted on the side. Argus's AI works inside the operations workflow — classifying, drafting, searching, and surfacing similar past incidents. Output is always a suggestion, never a side effect.
Drop an incident in. Argus reads the title and description, labels it P1–P4, and tags the systems affected — before anyone gets paged.
"Checkout 503s climbing" → P1 · payments-api · customer-facing
Vector embeddings on every postmortem and known error. The runbook from three months ago shows up next to the new alert, not buried six clicks deep.
3 similar: INC-1284, INC-998, INC-742 → known-error KE-12 · workaround attached
Once an incident is resolved, Argus pulls the timeline from comments, alerts, and audit log into a postmortem draft. You edit and publish — never write from scratch.
Timeline · Root cause · Contributing factors · Action items → draft ready in 8s · review and publish
"All P1s in the payments service last quarter." "What ran on the gateway during the 3am page?" Argus reads it. No query DSL, no filter pyramid.
"show me on-call escalations that paged twice last week" → 4 results · grouped by team · with timeline
The legacy ITSM stack is an artefact of pre-AI workflows. Argus is built for the way IT teams actually work in 2026 — keyboard, audit trail, and AI assistance from day one.
The console you'll actually want open at 3 a.m. Severity colour-coded by visual weight, AI tags inline, similar incidents one keystroke away.
▌ ask Argus: "what changed in payments-api in the last hour?"
No. Argus works inside the operations workflow: it classifies severity, surfaces similar past incidents, drafts postmortems, and presents every suggestion for operator approval before anything commits. Humans stay in the decision loop.
Heavy legacy ITSM suites, lightweight ticketing tools you have outgrown, and the home-grown incident workflows every team starts with. Argus brings ITIL-aligned process discipline without the weight.
Self-hosted and managed deployments are both planned. Argus is being designed for teams that need control over data residency, identity, and operational history.
AI output is a suggestion, never a side effect. Severity classification, similar-incident matches, and postmortem drafts are presented to the operator for review. We will publish accuracy benchmarks alongside the public release.
No. Tenant data is never used to train models. Your operational data stays under your control, and AI-assisted suggestions are handled under zero-retention commitments where applicable.
No. Argus discovers assets, services, and relationships incrementally. Start with one incident; add structure as you go.
Yes. Argus uses Pydantic AI under the hood. Swap providers via the AI_MODEL config without code changes — OpenAI, Anthropic, self-hosted, or your enterprise gateway.
No fixed date. The waitlist is for early access and design partners. We will write when there is something to share, not before.
Early access for IT teams, SREs, and incident responders who want ITSM that works for them, not the other way around. No countdowns, no spam — we'll write when there's something to share.
Curious about the ITSM domains Argus covers? Security posture, API & integrations, changelog.