Transparency alternatives to Optimus
Other Tax compliance software vendors we measure, sorted by how much we found at them and not at Optimus. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Optimus on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Optimus has 10 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. The column “Found there, not found at Optimus” is the one that closes them.
| Vendor | Score | Found there, not found at Optimus | Found at Optimus, not found there | |
|---|---|---|---|---|
| Avalaraavalara.comSee also Transparency alternatives to Avalara | 70/100 | 7 Data processing agreement, Data location stated, Status page with history, +4 | 1 No third-party tracking before consent | Compare |
| TaxJartaxjar.comSee also Transparency alternatives to TaxJar | 65/100 | 7 Data processing agreement, Data location stated, Status page with history, +4 | 2 No third-party tracking before consent, Named privacy contact | Compare |
| Quadernoquaderno.ioSee also Transparency alternatives to Quaderno | 48/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 2 No third-party tracking before consent, Named privacy contact | Compare |
| Fintuafintua.comSee also Transparency alternatives to Fintua | 35/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Kontistkontist.comSee also Transparency alternatives to Kontist | 35/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Taxandotaxando.deSee also Transparency alternatives to Taxando | 35/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Billitbillit.euSee also Transparency alternatives to Billit | 26/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Steuerbotsteuerbot.comSee also Transparency alternatives to Steuerbot | 26/100 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 No third-party tracking before consent | Compare |
| Vertexvertexinc.comSee also Transparency alternatives to Vertex | 22/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 No third-party tracking before consent, Named privacy contact | Compare |
| Amavatamavat.euSee also Transparency alternatives to Amavat | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Amazon VAT Partnertaxually.comSee also Transparency alternatives to Amazon VAT Partner | 26/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Tungsten Automationtungstenautomation.comSee also Transparency alternatives to Tungsten Automation | 26/100 | 2 Data location stated, 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.