Rule-Based Check
Deterministic detectors that catch known patterns quickly.
Enterprise-grade audit intelligence. Finally affordable for every CA firm.
launches on 1st April 2026
Fast, deterministic checks for known suspicious patterns (duplicates, blacklisted accounts, threshold breaches).
Robust outlier scoring using distribution-aware math for volume, frequency and velocity deviations.
Models identify complex patterns and subtle fraud that rules miss — continuously improving with data.
A clean, customer-friendly summary of how Auraium analyzes transactions. Every stage emits a score + human explanation. High-risk transactions advance through all stages and are re-evaluated by our LLM-based fraud validator.
The transparent, auditor-ready breakdown of how Auraium processes each transaction.
Visual flow that shows how transactions travel through the system.
Scroll horizontally through the pipeline stages with subtle animation.
We minimize data shared with external services and always prefer on-premise or private inference for sensitive fields.
Only necessary, non-identifying fields are sent to third-party services or LLMs for mapping: column headers, transaction metadata tags, and hashed IDs. Raw PII (names, account numbers) is never sent without being obfuscated or hashed — and only when explicitly allowed.
Models run in your controlled environment when possible. If cloud inference is used, data is pseudonymized and logged with strict retention policies.
Every API call is logged with a minimal bleed of fields and includes a reason code. This provides traceability while protecting privacy.
If automatic mapping fails, Auraium will (optionally) call an internal LLM helper with only column names — not values — to suggest mappings. You always see suggested mappings before they’re applied.
Auraium tracks precision, recall, and false positive rate per rule and per model. You can view suite-level metrics on the dashboard and set thresholds to meet your tolerance.
Yes — Auraium supports on-premise models and private inference. Cloud ML is optional and used only after explicit configuration.