Alternatives to Nansen
Other Crypto compliance and blockchain analytics vendors we measure, sorted by how much they publish that Nansen does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Nansen on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Nansen has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Nansen does not” is the one that closes them.
| Vendor | Score | Publishes, and Nansen does not | Nansen publishes, and they do not | |
|---|---|---|---|---|
| TaxBittaxbit.com | 48/100 | 4 Data location stated, Status page with history, Public pricing, +1 | nothing | Compare |
| CoinTrackingcointracking.info | 39/100 | 3 Data location stated, Public pricing, Certifications named | nothing | Compare |
| Notabenenotabene.id | 39/100 | 3 Data location stated, Public pricing, Certifications named | nothing | Compare |
| Blockpitblockpit.io | 35/100 | 2 Data location stated, Public pricing | nothing | Compare |
| Chainalysischainalysis.com | 35/100 | 2 Data location stated, Status page with history | nothing | Compare |
| Scorechainscorechain.com | 35/100 | 2 Data location stated, Status page with history | nothing | Compare |
| Accointingaccointing.com | 30/100 | 2 Data location stated, Public pricing | 1 Named privacy contact | Compare |
| Ellipticelliptic.co | 30/100 | 2 Data location stated, Certifications named | nothing | Compare |
| CoinLedgercoinledger.io | 26/100 | 2 Status page with history, Public pricing | 1 Named privacy contact | Compare |
| Integralintegral.xyz | 26/100 | 2 Data location stated, Certifications named | 1 Named privacy contact | Compare |
| 21 Analytics21analytics.co | 22/100 | 2 Certifications named, security.txt (RFC 9116) | nothing | Compare |
| Bitquerybitquery.io | 22/100 | 2 Data location stated, Public pricing | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.