Transparency alternatives to Nasdaq Private Market
Other Equity and cap table management vendors we measure, sorted by how much we found at them and not at Nasdaq Private Market. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 that differ from Nasdaq Private Market on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Nasdaq Private Market has 11 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Nasdaq Private Market” is the one that closes them.
| Vendor | Score | Found there, not found at Nasdaq Private Market | Found at Nasdaq Private Market, not found there | |
|---|---|---|---|---|
| Cartacarta.comSee also Transparency alternatives to Carta | 70/100 | 8 Subprocessor list, Data location stated, Status page with history, +5 | 1 Data processing agreement | Compare |
| Cake Equitycakeequity.comSee also Transparency alternatives to Cake Equity | 35/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 1 Data processing agreement | Compare |
| Hiivehiive.comSee also Transparency alternatives to Hiive | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Data processing agreement | Compare |
| Sydecarsydecar.ioSee also Transparency alternatives to Sydecar | 26/100 | 4 Public pricing, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data processing agreement | Compare |
| Bunchbunch.capitalSee also Transparency alternatives to Bunch | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Companistocompanisto.comSee also Transparency alternatives to Companisto | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Data processing agreement | Compare |
| Fairmintfairmint.comSee also Transparency alternatives to Fairmint | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Data processing agreement | Compare |
| Ledgyledgy.comSee also Transparency alternatives to Ledgy | 26/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Pulleypulley.comSee also Transparency alternatives to Pulley | 22/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Qapitaqapita.comSee also Transparency alternatives to Qapita | 22/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | 1 Data processing agreement | Compare |
| Corporifycorporify.comSee also Transparency alternatives to Corporify | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Allocationsallocations.comSee also Transparency alternatives to Allocations | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 Data processing agreement | 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.