Transparency alternatives to Financial Software Systems
Other Lending and mortgage software vendors we measure, sorted by how much they publish that Financial Software Systems does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Financial Software Systems on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Financial Software Systems has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Financial Software Systems does not” is the one that closes them.
| Vendor | Score | Publishes, and Financial Software Systems does not | Financial Software Systems publishes, and they do not | |
|---|---|---|---|---|
| Moxomoxo.com | 39/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 1 No third-party tracking before consent | Compare |
| Floifyfloify.com | 35/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Mambumambu.com | 30/100 | 4 Status page with history, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 No third-party tracking before consent | Compare |
| Q2q2.com | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Drooms Lendingdrooms.com | 26/100 | 4 Public pricing, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Encompassicemortgagetechnology.com | 30/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Banxwarebanxware.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| PCFS Solutionspcfssolutions.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Blendblend.com | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| DownHome Solutionsdownhomesolutions.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Meridianlinkmeridianlink.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Nortridgenortridge.com | 17/100 | 2 Status page with history, Public pricing | 1 No third-party tracking before consent | 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.