21 Analytics

  • Name: 21 Analytics
  • URL: https://www.21analytics.co/
  • Category: crypto compliance / Travel Rule infrastructure / self-hosted-wallet verification / privacy-first compliance software
  • Summary: 21 Analytics sells Travel Rule compliance software with a privacy-first, customer-hosted deployment model. Its official materials consistently emphasize on-premises deployment, direct counterparty data exchange, self-hosted-wallet verification via AOPP and related proof methods, and interoperability across networks such as TRP and TRUST. The useful distinction is simple: this is software for regulated transfer gating that tries not to hand the whole data exhaust to a central network operator.
  • What it does:
    • Provides web-interface and API-based tooling to review, register, export, and report Travel Rule transaction data for VASP-to-VASP and VASP-to-self-hosted-wallet flows
    • Supports pre-transaction approval or rejection workflows so counterparties can review Travel Rule information 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-note evidence of ongoing work on AOPP Portal, TRP workflows, legal-person support, and dashboard/infrastructure 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 customers’ servers, exposes both a web interface and API, supports unlimited transactions, and is designed for 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 canonical standalone 21 Analytics whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official company, product, security, user-guide, and release-note pages; see ../whitepapers/21-analytics-primary-sources-2026-04-30.md.
  • Sources:

Internal linkages

  • Keep this note pointed at the few strongest adjacent reads: aopp for the narrow wallet-proof rail, notabene for the broader operator stack, and verifyvasp for the closer regulated-transfer workflow comparison.

Governance / control risk

  • The important questions are who defines wallet-verification policy, which proof methods are treated as sufficient, how counterparty data is retained or exchanged, and how much practical logic still sits in vendor defaults even when the software runs in the customer environment.

  • The chain transfer is not the hard part here. The leverage sits in pre-broadcast approval rules, proof-method acceptance, and counterparty-data handling.

  • Last reviewed: 2026-05-25 UTC