Alternatives to Reco
Other Telecom and SaaS expense management vendors we measure, sorted by how much they publish that Reco does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 17 that differ from Reco on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Reco has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Reco does not” is the one that closes them.
| Vendor | Score | Publishes, and Reco does not | Reco publishes, and they do not | |
|---|---|---|---|---|
| Spendbasespendbase.co | 59/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Augmenttaugmentt.com | 48/100 | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Flexeraflexera.com | 52/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 2 Certifications named, Named privacy contact | Compare |
| Valencevalencesecurity.com | 52/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 1 Status page with history | Compare |
| Obsidianobsidiansecurity.com | 48/100 | 2 Data location stated, Public pricing | nothing | Compare |
| Nudge Securitynudgesecurity.com | 35/100 | 2 Data location stated, Public pricing | 2 Status page with history, Named privacy contact | Compare |
| Vcomvcomsolutions.com | 35/100 | 2 Data location stated, Public pricing | 2 Status page with history, Certifications named | Compare |
| Calerocalero.com | 30/100 | 1 Data location stated | 1 Status page with history | Compare |
| Cocuscocus.com | 30/100 | 1 Data location stated | 1 Status page with history | Compare |
| Axiansaxians.de | 22/100 | 1 security.txt (RFC 9116) | 1 Status page with history | Compare |
| Saasmentsaasment.com | 17/100 | 1 Public pricing | 3 Status page with history, Certifications named, Named privacy contact | Compare |
| License Dashboardlicensedashboard.com | 13/100 | 1 Data location stated | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +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.