Transparency alternatives to Acodei
Other Accounting vendors we measure, sorted by how much we found at them and not at Acodei. This is a comparison of disclosure, not of features or fitness.
12 shown of 70 that differ from Acodei on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Acodei has 7 gaps in what we could measure: Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at Acodei” is the one that closes them.
| Vendor | Score | Found there, not found at Acodei | Found at Acodei, not found there | |
|---|---|---|---|---|
| Odooodoo.comSee also Transparency alternatives to Odoo | 39/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| AccountKitaccount-kit.comSee also Transparency alternatives to AccountKit | 70/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 Notice before subprocessors change | Compare |
| Xeroxero.comSee also Transparency alternatives to Xero | 36/100 | 3 Data location stated, Status page with history, Certifications named | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Zervantzervant.comSee also Transparency alternatives to Zervant | 36/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| AuditFileauditfile.comSee also Transparency alternatives to AuditFile | 35/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Clear Booksclearbooks.co.ukSee also Transparency alternatives to Clear Books | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| FreeAgentfreeagent.comSee also Transparency alternatives to FreeAgent | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Billbill.comSee also Transparency alternatives to Bill | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Billomatbillomat.comSee also Transparency alternatives to Billomat | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | Compare |
| Meliomelio.comSee also Transparency alternatives to Melio | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Candiscandis.ioSee also Transparency alternatives to Candis | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | Compare |
| Fortnoxfortnox.seSee also Transparency alternatives to Fortnox | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | 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.