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