Transparency alternatives to Kyriba
Other Financial planning and close vendors we measure, sorted by how much we found at them and not at Kyriba. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Kyriba on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kyriba has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Kyriba” is the one that closes them.
| Vendor | Score | Found there, not found at Kyriba | Found at Kyriba, not found there | |
|---|---|---|---|---|
| Leapfinleapfin.comSee also Transparency alternatives to Leapfin | 61/100 | 5 Data processing agreement, Public pricing, Uptime SLA with a figure, +2 | 1 security.txt (RFC 9116) | Compare |
| Venavenasolutions.comSee also Transparency alternatives to Vena | 52/100 | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | 1 security.txt (RFC 9116) | Compare |
| BlackLineblackline.comSee also Transparency alternatives to BlackLine | 38/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 2 Data location stated, security.txt (RFC 9116) | Compare |
| SecureSheetsecuresheet.comSee also Transparency alternatives to SecureSheet | 35/100 | 3 Public pricing, Certifications named, Notice before subprocessors change | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Planfulplanful.comSee also Transparency alternatives to Planful | 30/100 | 3 Subprocessor list, Certifications named, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Anaplananaplan.comSee also Transparency alternatives to Anaplan | 26/100 | 3 Status page with history, Certifications named, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Alephgetaleph.comSee also Transparency alternatives to Aleph | 39/100 | 2 Subprocessor list, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Cubecubesoftware.comSee also Transparency alternatives to Cube | 35/100 | 2 Status page with history, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Pigmentpigment.comSee also Transparency alternatives to Pigment | 30/100 | 2 Certifications named, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Treasury Intelligencetis.bizSee also Transparency alternatives to Treasury Intelligence | 26/100 | 2 Status page with history, Public pricing | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Runwayrunway.comSee also Transparency alternatives to Runway | 22/100 | 2 Public pricing, Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Trintechtrintech.comSee also Transparency alternatives to Trintech | 22/100 | 2 Certifications named, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 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.