Transparency alternatives to Instabase
Other Document AI and data capture vendors we measure, sorted by how much we found at them and not at Instabase. This is a comparison of disclosure, not of features or fitness.
12 shown of 39 that differ from Instabase on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Instabase has 8 gaps in what we could measure: Data processing agreement, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Instabase” is the one that closes them.
| Vendor | Score | Found there, not found at Instabase | Found at Instabase, not found there | |
|---|---|---|---|---|
| Hypatoshypatos.aiSee also Transparency alternatives to Hypatos | 65/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Parseurparseur.comSee also Transparency alternatives to Parseur | 65/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 1 Subprocessor list | Compare |
| Mindeemindee.comSee also Transparency alternatives to Mindee | 57/100 | 5 Data processing agreement, Data location stated, Status page with history, +2 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Formxformx.aiSee also Transparency alternatives to Formx | 57/100 | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | 2 Certifications named, Named privacy contact | Compare |
| Nanonetsnanonets.comSee also Transparency alternatives to Nanonets | 57/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 Certifications named, Notice before subprocessors change | Compare |
| Anyrowanyrow.aiSee also Transparency alternatives to Anyrow | 48/100 | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | 2 Subprocessor list, Certifications named | Compare |
| Upstageupstage.aiSee also Transparency alternatives to Upstage | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Deepsetdeepset.aiSee also Transparency alternatives to Deepset | 39/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Veryfiveryfi.comSee also Transparency alternatives to Veryfi | 48/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Abbyyabbyy.comSee also Transparency alternatives to Abbyy | 39/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Sensiblesensible.soSee also Transparency alternatives to Sensible | 35/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Docparserdocparser.comSee also Transparency alternatives to Docparser | 30/100 | 3 Data location stated, Status page with history, Public pricing | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +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.