Technology philosophy
The principles we build by.
These principles shape what we choose to build, how we evaluate it, and what we decline to claim. They are the standard we expect to be held to.
Why principles
Security tools are trusted with a great deal. That trust has to be earned.
A platform that observes an organization’s most privileged automation, and tells a security team what to worry about, has real influence over how that team spends its time and what it believes about its own environment.
That influence should come with explicit commitments: about the quality of what we raise, how conclusions are reached, who holds authority, and how honestly we describe what the platform can and cannot do.
The principles below are those commitments. They apply to product design, to how we evaluate detection quality, and to how we talk about Ordrani — including on this website.
In practice
- Detection quality judged by analyst outcomes, not alert counts
- Every finding traceable to the events behind it
- No autonomous changes to a customer’s environment
- AI that explains and cites, never decides
- Product claims we can demonstrate
Our principles
Six commitments.
01
Precision before volume
A security team’s attention is the scarcest resource in the system. We would rather raise one well-evidenced case than ten plausible alerts, and we measure ourselves accordingly.
02
Evidence before inference
Every conclusion the platform presents must be traceable to the events that support it. Where the evidence is incomplete, the platform says so.
03
Context before conclusion
An operation cannot be judged without knowing who performed it, on behalf of which workflow, against what, and in what sequence. Context is the product, not decoration.
04
People hold authority
Ordrani observes, correlates and recommends. Decisions that change a customer’s environment are made by the people accountable for it.
05
Complement, don’t replace
Enterprises have invested in identity providers, SIEMs and cloud-native detection. Ordrani is built to strengthen that investment, not to compete for the same role.
06
Narrow, then deep
We begin where the problem is most concentrated and most tractable, and earn the right to broaden by doing that one thing well.
How they show up in the product
Principles are only useful if they constrain decisions.
01
Corroboration before a case
02
Attribution with a grade
03
Assessments that cite
04
Response held for approval
05
Exports, not a new silo
06
Measures defined first
Continue exploring
Related reading.
Hold us to these standards.
We welcome conversations with security leaders and engineers who care about how security tooling earns trust.