Command
The problem
A security analyst investigating a breach might touch six tools in twenty minutes: a SIEM, a threat intel feed, an endpoint console, a ticketing system, a browser, and a chat window to ask a colleague what happened last time. The problem is not any single tool. The problem is that the work lives in the gaps between them.
What it is
Command is a conversational AI layer that sits across Axur's product ecosystem. Instead of moving between dashboards, an analyst describes what they need in natural language: correlate these indicators, pull the context from last week's incident, draft the escalation. The system retrieves, synthesizes, and acts.
My role
I helped shape what this product should be, not just technically but conceptually: what it means for AI to move from isolated question-answering toward coordinated operational judgment. Product vision, experience structure, and the longer-term direction toward agentic orchestration.
Why it matters
The difference between automation and useful AI is the difference between scaling rules and scaling judgment. Most security automation runs playbooks. Command is aimed at the harder layer: the one where context matters and the right next step depends on what just happened.