Who it's for
Atlas serves the people accountable for KYB/AML decisions and the engineers who run the platform. Each persona has a different question; Atlas answers all of them from the same resolved graph.
MLRO / Head of Compliance
Question: "Can we defend every decision, and is our policy applied consistently?"
- Owns the risk matrices and the survivorship/policy posture.
- Relies on provenance and audit trails to satisfy regulators.
- Values the competitive advantage: defensible, reproducible answers.
KYB/AML Analyst
Question: "Who is really behind this company, and what's the risk?"
- Runs investigations and reviews reports in the Atlas Console.
- Resolves conflicts flagged for human judgement.
- Explores ownership graphs and lineage for EDD.
Onboarding Operations
Question: "How do we clear more cases without lowering the bar?"
- Cares about throughput: parallel modules, repeatable workflows, fewer false positives to triage.
- Benefits from resolution collapsing duplicate noise.
Compliance Engineer (Studio user)
Question: "How do I encode our policy and data sources into the platform?"
- Configures ontology field mappings, risk matrices and categories, data segments, and provider credentials in the Console's Studio.
- Uses the Extending Atlas guides to evolve policy without code changes where possible.
Platform Operator / Engineer
Question: "How do I deploy, scale, and keep this healthy — and evolve it?"
- Runs the stack (Operations), watches observability, onboards tenants.
- Evolves the system using the architecture and extension guides.
One graph, many questions
| Persona | Primary surface | Primary doc |
|---|---|---|
| MLRO | Risk dashboards, audit trail | Outcomes |
| Analyst | Investigations, reports, graph | Use cases |
| Onboarding ops | Investigation throughput | Investigation story |
| Compliance engineer | Studio configuration | Extending Atlas |
| Operator | Deployment & ops | Operations |