Alternatives to Nucleus Software
Other Lending and mortgage software vendors we measure, sorted by how much they publish that Nucleus Software does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 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 “publishes and Nucleus Software does not” is the one that closes them.
| Vendor | Score | Publishes, and Nucleus Software does not | Nucleus Software publishes, and they do not | |
|---|---|---|---|---|
| Floifyfloify.com | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 Named privacy contact | Compare |
| Drooms Lendingdrooms.com | 39/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 1 Named privacy contact | Compare |
| Moxomoxo.com | 39/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 1 security.txt (RFC 9116) | Compare |
| Encompassicemortgagetechnology.com | 30/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Mambumambu.com | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Meridianlinkmeridianlink.com | 30/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Lendingpadlendingpad.com | 22/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Banxwarebanxware.com | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Fiservfiserv.com | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Blendblend.com | 22/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Bluevinebluevine.com | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Europaceeuropace.de | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 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.