Alternatives to Blockaid
Other Crypto compliance and blockchain analytics vendors we measure, sorted by how much they publish that Blockaid does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Blockaid on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Blockaid has 11 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, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Blockaid does not” is the one that closes them.
| Vendor | Score | Publishes, and Blockaid does not | Blockaid publishes, and they do not | |
|---|---|---|---|---|
| TaxBittaxbit.com | 48/100 | 6 Data location stated, Status page with history, Public pricing, +3 | 1 No third-party tracking before consent | Compare |
| CoinTrackingcointracking.info | 39/100 | 5 Data location stated, Public pricing, Certifications named, +2 | 1 No third-party tracking before consent | Compare |
| Notabenenotabene.id | 39/100 | 5 Data location stated, Public pricing, Certifications named, +2 | 1 No third-party tracking before consent | Compare |
| Blockpitblockpit.io | 35/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Chainalysischainalysis.com | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Scorechainscorechain.com | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Ellipticelliptic.co | 30/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| 21 Analytics21analytics.co | 22/100 | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Accointingaccointing.com | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| CoinLedgercoinledger.io | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Integralintegral.xyz | 26/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Bitwavebitwave.io | 22/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | 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.