Five high-impact use cases.

Where ALEXUS earns its keep — week one.

Shipping today

Present use cases

Five high-impact patterns ALEXUS earns its keep on this week — built on the features live in the platform now.

Use Case 01 · Conversational AI Service Desk

Ask Alexus,right in chat.

Employees self-serve answers. SREs query app health and raise tickets. All in natural language, all inside Slack and Teams — no console-hopping, no queue.

  • Self-serve deflection
    Users ask in their own words; ALEXUS cites runbooks and prior fixes — no ticket needed.
  • Natural-language ops queries
    “Is checkout-api healthy?” · “What's CI status of auth-svc?” — answers backed by your live CMDB.
  • Raise tickets from any thread
    Alexus pre-fills service, last deploy, recent incidents and on-call assignment from thread context.
#it-help · #ops-channel
Slack · Teams · ALEXUS connected
Live
EM
How do I reset my VPN config?
AI
Run /runbook reset-vpn — rotates your client cert and re-pulls config from the IdP. Takes ~40 seconds. Cited: runbooks/vpn-reset.md · 3 prior fixes.
SR
@alexus is checkout-api healthy?
AI
🟢 checkout-api healthy. 3/3 replicas green · p99 142ms · last incident 14d ago (INC-4218 · resolved).
SR
@alexus raise ticket — login returning 500s
AI
Raised INC-4221 · linked to auth-svc · last deploy 2h ago (v3.4.1) · P2 · assigned to @sarah (on-call). Thread linked.
Type a message · @alexus to ask⏎ send
Pattern detected
redis-oom · checkout-api
0×
auto-resolved this month
30 days agotoday
All confidence-gated0 escalations
Use Case 02 · Self-Healing

Repeat issuesfix themselves.

ALEXUS spots recurring patterns, applies the proven fix, and closes the ticket. Every action signed and reviewable.

Confidence-gated

Acts only when sure.

Full audit log

Every step recorded.

Use Case 03 · Knowledge KB

No morestale wikis.

Every fix becomes a knowledge entry — automatically. The KB grows with every incident, every PR, every runbook change.

  • Builds itself from fixes
    Resolutions become canonical entries.
  • Searchable in seconds
    Hybrid graph + vector retrieval.
how to handle pod OOM12 results · 0.18s
redis pod OOM — graceful restart
INC-3892 · 14 days ago
checkout-api memory leak resolution
INC-4218 · 2 days ago
rolling restart with PDB awareness
runbook · 47 uses
247 articlesauto-built · last update 2m ago
Diagnosing INC-42182.4s
checkout-api
payment-svc
redis
redis · v1.2.3memory leak
Culpritredis pod-7f8 · OOM at v1.2.3
Use Case 04 · Root-Cause AI

Diagnosis inseconds.

ALEXUS correlates logs and metrics, walks the dependency graph, and names the culprit before the page is acknowledged.

Logs + metrics

Correlated automatically.

Dependency-aware

Walks the graph 2 hops out.

Use Case 05 · Live CMDB · CI Lifecycle

A CMDB thatstays current.

ALEXUS spots new services the day they spin up, flags dead ones the moment traffic stops, and reconciles ownership from PagerDuty, CODEOWNERS and Slack — so the inventory is current, not just complete.

  • New CI auto-detection
    Canary deploy, new namespace, new SaaS connector — surfaced with a confidence-scored ownership guess.
  • Dead CI flagging
    No traffic, no owner, no recent deploy? ALEXUS proposes decommission — with the evidence trail attached.
  • Drift reconciliation
    Modelled state vs reality drift — caught in minutes, not at the next audit. Decision log attached.
Asset events · live
CMDB · 247 CIs · last sync 14s ago
Streaming
Discovered · payments-worker-v2NEW CI · 92% confidence

k8s · ns:prod · seen 4× from canary deploy · owner inferred: @ravi (CODEOWNERS + last 3 PRs)

Dead · legacy-reports-apiDEAD CI · 88% confidence

No traffic for 47 days · no owning team in Slack · last deploy 8 months ago · suggested: → deprecated

Drift · redis-cache · ownershipDRIFT · auto-resolved

PagerDuty says @platform-team · CODEOWNERS says @infra · reconciler picked @platform-team (more recent signal)

Lifecycle state — payments-worker-v2
Planned
Live
Degraded
Deprecated
Decommissioned
Coming next · planned

Future use cases · Q3 2026 onwards

What ships into your tier as the CMDB Substrate, NIS2 Compliance Module and Executive Accountability Pack roll out — included at no extra cost.

Planned
Use Case 06

Predictive change-risk scoring

CMDB Substrate Module

Govern + Operate · Q3 2026

Every proposed change is scored against a live dependency graph — what it touches, what depends on what, where the blast radius lands. Risky changes get flagged before they ship, dropping change-failure rate from typical 7–10% to high-elite 4%.

  • Live blast-radius queries on every change request
  • Pre-flight risk score (low / medium / high) + remediation suggestions
  • Failed-change cost avoidance — biggest single dollar driver in the ROI calc
  • Underpins change-failure-rate avoidance — the biggest single dollar driver for regulated mid-market customers
Planned
Use Case 07

NIS2 Article 23 — 24h incident reporting

NIS2 Compliance Module

Govern + Operate · Q3–Q4 2026

Material incident? ALEXUS auto-assembles the Article 23 early-warning report (24h) and the full report (72h) from the live CMDB — affected systems, data in scope, controls in place — and pushes it to your national CSIRT in the required format.

  • Continuous Article 21 readiness scoring (low / medium / high)
  • Auto-drafted Article 23 reports — 24h warning + 72h full
  • CSIRT push integration (Ireland, Germany, France national bodies)
  • Drives the qualitative NIS2 risk-reduction badge in the calculator
Planned
Use Case 08

Executive Accountability Pack — quarterly evidence

Executive Accountability Pack

Operate (included) · Govern add-on · Q3–Q4 2026

Audit-grade quarterly evidence pack for the board and CISO. Defensibility under NIS2 Article 20 personal-liability exposure, cleanly assembled for D&O and cyber-insurance underwriting — turns asset-inventory hygiene from a hand-wave into a hash-chained artefact.

  • Hash-chained quarterly asset-inventory snapshot
  • Personal-liability defensibility narrative (Article 20)
  • Cyber + D&O underwriting evidence pack (5–15% premium swing)
  • Audit-prep time cut ~50% versus spreadsheet baseline

Planned features ship into Govern + Operate at no extra cost during your contract — and become available at Detect as paid add-ons from 2027 for non-founding customers. See the pricing roadmap for module-by-module timing.

ALEXUS · Pitch Deck · May 2026
What's next

See it in action

Watch ALEXUS run through these scenarios live.