Alternatives to Rossum
Other Document AI and data capture vendors we measure, sorted by how much they publish that Rossum does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from Rossum on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Rossum has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Rossum does not” is the one that closes them.
| Vendor | Score | Publishes, and Rossum does not | Rossum publishes, and they do not | |
|---|---|---|---|---|
| Parseurparseur.com | 65/100 | 6 Data processing agreement, Data location stated, Certifications named, +3 | nothing | Compare |
| Formxformx.ai | 57/100 | 5 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +2 | 1 security.txt (RFC 9116) | Compare |
| Mindeemindee.com | 57/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| Nanonetsnanonets.com | 57/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| Veryfiveryfi.com | 48/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Abbyyabbyy.com | 39/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Docsumodocsumo.com | 52/100 | 4 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +1 | 1 security.txt (RFC 9116) | Compare |
| Upstageupstage.ai | 43/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 1 security.txt (RFC 9116) | Compare |
| Instabaseinstabase.com | 30/100 | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Deepsetdeepset.ai | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Bdo Digitalocrolus.com | 35/100 | 3 Data location stated, Status page with history, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Sensiblesensible.so | 35/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | 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.