Recorded facts and estimates stay apart
Every edge, link and label shows where it came from and how sure Authe is about it.
The tracer draws recorded transfers and estimated allocations differently, and calls an estimate an estimate. A bridge transfer whose destination Authe has not seen is marked not observed, which is not the same as failed. Sandwich and peel-chain findings are labelled as inferred patterns, not proof of intent. A per-scope confidence policy decides how sure the platform has to be before it links an entity or raises an alert.
Bridge legs matched on the bridge's own IDs
Source and destination transactions are grouped by the identifier the protocol itself uses.
Fifty built-in grouping recipes cover about 25 bridges and messaging protocols: the CCIP message ID, the Wormhole VAA, the LayerZero packet, the CCTP burn message, IBC packets and THORChain memos. The same engine ties a CoW Swap order to the settlement that filled it, and follows a Polymarket market from creation to payout. On Pro, you can add your own grouping rules on top.
Cases that hold up to review
Transactions, graphs, notes and annotations live in one shared case.
Analysts work on the same case at the same time. Catalog entries record who wrote them, from your own notes up to the platform catalog, so a colleague's label is never mistaken for a vendor's. A workflow step can wait for sign-off from people other than its author, or for a two-factor signature, and a finished case prints as a report.
A finding becomes a watch
Save the query, watch the addresses, and send alerts to wherever your on-call already looks.
Alert rules run inside the pipeline, after decoding and enrichment, so a rule can match decoded fields and risk scores rather than raw logs. Alerts go to Slack, HMAC-signed webhooks, email, AWS SNS or the in-app queue. Pipelines, tracers, rules and destinations can also live in Terraform and go through code review like any other change.
Works alongside your screening tools
Authe does not ship a full sanctions list. Risk scoring uses the labels in your catalog, which come from your team, the platform catalog and third-party providers. Run it next to the screening service you already use and bring the decoded evidence into your existing review workflow.
Paired US regions
Oregon and N. Virginia back each other up
Team roles
Built-in roles, custom roles on Pro
Managed sign-in
Auth0 accounts and organisations
Audit log
Who changed what, and when