21 Analytics
- Name: 21 Analytics
- URL: https://www.21analytics.co/
- Category: Travel Rule compliance software company / self-hosted-wallet verification operator / privacy-first transaction-gating stack
- Summary: 21 Analytics belongs as an entity note, not a protocol note. The useful cut is that a named company operates a compliance workflow stack around counterparty exchange, pre-transfer approval, self-hosted-wallet proof, policy configuration, and local deployment. The practical leverage is not
Travel Rulein the abstract; it is that the company packages the decision surface that determines which transfers are allowed to proceed, which proof methods count, how counterparties are modeled, and how much supposedly local compliance logic still inherits vendor defaults. - What it does:
- Provides web and API tooling to review, register, export, and report Travel Rule data for VASP-to-VASP and VASP-to-self-hosted-wallet flows
- Supports pre-transaction approval or rejection workflows before funds move onchain
- Verifies self-hosted-wallet ownership through AOPP, Satoshi tests, signed-message flows, and visual-proof methods depending on wallet and risk context
- Lets customers manage counterparty VASPs, apply business rules, and attach external blockchain-risk signals while keeping sensitive data in their own environment
- Ships as containerized enterprise software, with release notes showing ongoing work on AOPP Portal, TRP workflows, legal-person support, and dashboard hardening
- Key claims:
- The company page says 21 Analytics was founded in 2020 to address the Travel Rule while preserving peer-to-peer crypto transactions without introducing a new intermediary
- The product page says the platform runs on customer servers, exposes both a web interface and API, supports unlimited transactions, and covers both self-hosted-wallet and VASP scenarios
- The self-hosted-wallet verification page says the product supports 540+ wallets and offers four ownership-proof methods, with AOPP positioned as a one-click flow
- The security and FAQ materials say personally identifiable information stays within the customer environment and is exchanged directly between counterparties rather than through a central hub
- The company page says 21 Analytics contributed to open standards, invented AOPP, and became the first Travel Rule solution provider to join TRUST while also supporting TRP
- The 8.0.0 release notes show active product development across Phantom and TronLink AOPP support, legal-person handling, TRP workflow changes, non-root containers, and dashboard/API improvements
- Whitepaper: No classic standalone whitepaper is the point here. The clearest primary materials remain the official company, product, security, user-guide, and release-note pages collected in
../whitepapers/21-analytics-primary-sources-2026-04-30.md. - Sources:
- https://www.21analytics.co/
- https://www.21analytics.co/company/
- https://www.21analytics.co/21-travel-rule-solution/
- https://www.21analytics.co/self-hosted-wallet-verification/
- https://www.21analytics.co/data-security/
- https://www.21analytics.co/why-choose-21-analytics/
- https://www.21analytics.co/tfr-user-guide/
- https://www.21analytics.co/what-is-aopp/
- https://www.21analytics.co/release-notes/8-0-0/
- https://github.com/21analytics
Internal linkages
- Project-layer alias: 21-analytics.
- Keep the comparison set tight around the clearest adjacent compliance and transaction-gating reads: notabene, trisa, and aopp.
- Reusable lens: when a product says
self-hostedorprivacy-first compliance, the real leverage may still sit in proof-method acceptance, workflow configuration, and the vendor’s model of what counts as a transfer-ready counterparty.
Control surface
-
Practical leverage sits in proof-method acceptance, pre-broadcast approval rules, counterparty-data modeling, retention and exchange policy, risk-signal integration, and how much day-to-day compliance logic still follows 21 Analytics’ software assumptions even when the stack is customer-hosted.
-
The sticky dependency is not only data exchange. Once onboarding, wallet-proof checks, approval gating, and reporting all run through the same company-defined workflow shell, institutions start inheriting that shell as part of their effective transaction policy.
-
Treat 21 Analytics as a company-run compliance control plane, not as a neutral Travel Rule protocol primitive.
-
Last reviewed: 2026-08-05 UTC