Transparency alternatives to Nucleus Software
Other Lending and mortgage software vendors we measure, sorted by how much we found at them and not at Nucleus Software. This is a comparison of disclosure, not of features or fitness.
12 shown of 47 that differ from Nucleus Software on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Nucleus Software has 10 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, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Nucleus Software” is the one that closes them.
| Vendor | Score | Found there, not found at Nucleus Software | Found at Nucleus Software, not found there | |
|---|---|---|---|---|
| Floifyfloify.comSee also Transparency alternatives to Floify | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 Named privacy contact | Compare |
| Lendboxlendbox.ioSee also Transparency alternatives to Lendbox | 35/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Encompassicemortgagetechnology.comSee also Transparency alternatives to Encompass | 30/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Mambumambu.comSee also Transparency alternatives to Mambu | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Moxomoxo.comSee also Transparency alternatives to Moxo | 30/100 | 3 Data location stated, Status page with history, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Drooms Lendingdrooms.comSee also Transparency alternatives to Drooms Lending | 26/100 | 3 Public pricing, Certifications named, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Lendingpadlendingpad.comSee also Transparency alternatives to Lendingpad | 22/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Q2q2.comSee also Transparency alternatives to Q2 | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | nothing | Compare |
| Banxwarebanxware.comSee also Transparency alternatives to Banxware | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| PCFS Solutionspcfssolutions.comSee also Transparency alternatives to PCFS Solutions | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Blendblend.comSee also Transparency alternatives to Blend | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| DownHome Solutionsdownhomesolutions.comSee also Transparency alternatives to DownHome Solutions | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 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.