Alternatives to IPRally
Other Patent and trademark management vendors we measure, sorted by how much they publish that IPRally does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 22 that differ from IPRally on at least one criterion we measured for both. Public transparency score, not a product or security rating.
IPRally has 7 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Named privacy contact. The column “publishes and IPRally does not” is the one that closes them.
| Vendor | Score | Publishes, and IPRally does not | IPRally publishes, and they do not | |
|---|---|---|---|---|
| PatSnappatsnap.com | 52/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Wellspringwellspring.com | 48/100 | 3 Subprocessor list, Status page with history, Named privacy contact | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Amplifiedamplified.ai | 43/100 | 2 Public pricing, No third-party tracking before consent | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Corsearchcorsearch.com | 26/100 | 2 Subprocessor list, Named privacy contact | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | Compare |
| Red Pointsredpoints.com | 13/100 | 2 Public pricing, Named privacy contact | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | Compare |
| Doppeldoppel.com | 27/100 | 1 Certifications named | 2 Data processing agreement, Notice before subprocessors change | Compare |
| EBRANDebrand.com | 26/100 | 1 Named privacy contact | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Questelquestel.com | 22/100 | 1 Subprocessor list | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | Compare |
| Inteuminteum.com | 17/100 | 1 Certifications named | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| IPzenipzen.com | 17/100 | 1 Public pricing | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | Compare |
| Nameshieldnameshield.com | 17/100 | 1 Certifications named | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Anaquaanaqua.com | 13/100 | 1 Certifications named | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | 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.