Transparency alternatives to Axians
Other Telecom and SaaS expense management vendors we measure, sorted by how much we found at them and not at Axians. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from Axians on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Axians has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Axians” is the one that closes them.
| Vendor | Score | Found there, not found at Axians | Found at Axians, not found there | |
|---|---|---|---|---|
| Augmenttaugmentt.comSee also Transparency alternatives to Augmentt | 65/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Spendbasespendbase.coSee also Transparency alternatives to Spendbase | 61/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Flexeraflexera.comSee also Transparency alternatives to Flexera | 52/100 | 4 Data processing agreement, Data location stated, Status page with history, +1 | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Obsidianobsidiansecurity.comSee also Transparency alternatives to Obsidian | 48/100 | 3 Data location stated, Status page with history, Public pricing | 1 security.txt (RFC 9116) | Compare |
| Tropictropicapp.ioSee also Transparency alternatives to Tropic | 43/100 | 3 Subprocessor list, Status page with history, Public pricing | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Valencevalencesecurity.comSee also Transparency alternatives to Valence | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Wingswithwings.aiSee also Transparency alternatives to Wings | 35/100 | 2 Data location stated, No third-party tracking before consent | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Calerocalero.comSee also Transparency alternatives to Calero | 30/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Cocuscocus.comSee also Transparency alternatives to Cocus | 30/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Recoreco.aiSee also Transparency alternatives to Reco | 26/100 | 1 Status page with history | 1 security.txt (RFC 9116) | Compare |
| Sakonsakon.comSee also Transparency alternatives to Sakon | 26/100 | 1 Data location stated | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Nudge Securitynudgesecurity.comSee also Transparency alternatives to Nudge Security | 22/100 | 1 Public pricing | 2 security.txt (RFC 9116), Named privacy contact | 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.