Crypto compliance that can prove why.
Avus detects, investigates and reports crypto-asset risk for CASPs in the EU and the Emirate of Dubai, and keeps the proof behind every alert, score and filing.
Compliance takes more from every team than anyone planned.
For a crypto-asset service provider it draws on people, capital, time and personal accountability, all at once.
People
Analysts spend their days triaging noise. The judgement they were hired for comes last.
Capital
Licences, vendors and headcount stack up faster than revenue does.
Risk
Personal liability sits with the MLRO on every decision that leaves the building.
Time
Filing deadlines and supervisor questions arrive on their own schedule.
The answer a supervisor wants is spread across eight tools.
Monitoring, KYC, the Travel Rule, screening lists, case files and internal records each hold a piece. Avus connects them into one workflow, so the answer is already assembled.
Each tool holds a piece. Your team stitches them together by hand.
Detect to filing, in one workflow.
The engine screens every transfer.
Blockchain analytics, sanctions and counterparty checks run on each transaction. Scores and thresholds come from a deterministic engine, so the same input gives the same answer.
- Rules by customer type, written in plain language
- Screening against connected analytics and list providers
- Every score names the rule that produced it
transfers screened today
Fewer, better alerts.
Each alert leads with its reason. Risk is shown three ways: the word, the meter and the color. Analysts see what matters first and how long they have.
- Reason-first titles, never a bare rule number
- SLA and owner on every row
- Filter by risk, customer type or counterparty
The agent explores. You read the trail.
Case AI follows the funds across hops and bridges, then hands back a reasoning sentence with the evidence beneath it. It proposes. A person confirms.
- Ask about a case, a cluster or a related case
- Agent activity is always labelled and logged
- Numbers come from the engine, never from the agent
Hand-offs with a record.
A case moves up the chain with its trail attached. Each step logs who, when and why, so the MLRO opens a case that is already assembled.
- Configurable escalation paths by risk level
- Four-eyes approval where policy requires it
- One audit trail from first alert to final decision
Triaged
Confirmed
Reviewing
Pending
The filing writes from the trail.
Suspicious transaction reports draft themselves from the evidence already collected. Review, edit, sign off, and export to goAML.
- STR and SAR drafts, monthly and yearly reports
- goAML export with the evidence attached
- Every edit tracked against the source trail
Customer C-88213, account opened 12 Aug 2026
Inbound 48,200 USDT reached a sanctioned cluster in three hops. Source and list match attached.
Proof trail, transaction graph, screening results
Every score can explain itself.
The agent explores the chain. The engine owns every score. A person makes every decision.
Read about Proof of WhyBecause the funds reached a sanctioned cluster in three hops.
- Agent
Traced the funds across three hops.
- Engine
Scored the exposure 87, High.
- Analyst
Confirmed and escalated to the MLRO.
What I like about Avus is that it has been designed around the real challenges compliance teams face every day.
Instead of adding another standalone tool to an already fragmented compliance stack, Avus brings transaction monitoring, blockchain analytics, sanctions screening, investigations, case management and regulatory reporting into one coherent workflow. I particularly value its focus on explainability: every risk score can be traced back to the rule and evidence that produced it, while AI supports the investigation without replacing human judgement. For regulated crypto businesses, that combination of efficiency, transparency and regulatory defensibility is particularly compelling.
Write the rule the way you would say it.
Avus reads the sentence, understands each part, and asks when a threshold is ambiguous. Every customer type gets rules that fit it, and a second officer approves before anything goes live.
Built with regulation in mind.
MiCA, AMLR, the Travel Rule and DORA shape the product from the first line. Requirements become controls, and controls leave evidence.
MiCA
Markets in Crypto-AssetsAuthorisation, governance and ongoing obligations, evidenced from day one.
Read moreAMLR
Anti-Money Laundering RegulationOne EU rulebook for due diligence and monitoring, applied the same way every time.
Read moreTravel Rule
Transfer of Funds RegulationOriginator and beneficiary data travels with every transfer and is checked before funds move.
Read moreDORA
Digital Operational Resilience ActOperational resilience, with the logs, controls and third-party records auditors ask for.
Read moreMade for the people who answer for it.
MLROs
You carry personal regulatory liability.
Every decision, defensible in front of a supervisor.
Why was AV-2291 escalated?
Funds reached a sanctioned cluster in three hops.
- Trail
- Source
- Approvals
Analysts
You carry a queue and an SLA.
Less noise, with the reasoning already assembled.
Engineering
You carry integration and DORA risk.
Clean APIs, clear data lineage, no black boxes.
{ "score": 87, "risk": "high", "trail": "trl_2291"}
Founders
A team you can meet in person.
Founders who have built and exited a company together, engineers from inside banking systems, and advisors from law, finance and digital assets. We work across Milan, Vienna, Riga and the United Kingdom, and we host the people we build for.
The people behind Avus, from banking, law and the digital asset community.
How your MLRO answers ‘why’ in under a minute.
Bring a real case. We will show you the trail, the score and the filing.