Transparency alternatives to Nexvia
Other Construction management vendors we measure, sorted by how much we found at them and not at Nexvia. This is a comparison of disclosure, not of features or fitness.
12 shown of 64 that differ from Nexvia on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Nexvia has 7 gaps in what we could measure: Subprocessor list, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at Nexvia” is the one that closes them.
| Vendor | Score | Found there, not found at Nexvia | Found at Nexvia, not found there | |
|---|---|---|---|---|
| Daluxdalux.comSee also Transparency alternatives to Dalux | 52/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 3 Data processing agreement, Status page with history, Public pricing | Compare |
| CompanyCamcompanycam.comSee also Transparency alternatives to CompanyCam | 48/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Bridgitgobridgit.comSee also Transparency alternatives to Bridgit | 39/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| SmartPMsmartpmtech.comSee also Transparency alternatives to SmartPM | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Data location stated, Status page with history, +1 | Compare |
| Capmocapmo.comSee also Transparency alternatives to Capmo | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 5 Data processing agreement, Data location stated, Status page with history, +2 | Compare |
| Cosunocosuno.comSee also Transparency alternatives to Cosuno | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 5 Data processing agreement, Data location stated, Status page with history, +2 | Compare |
| VisiLeanvisilean.comSee also Transparency alternatives to VisiLean | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Data location stated, Status page with history, +2 | Compare |
| CUBE CDEcube.msSee also Transparency alternatives to CUBE CDE | 35/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Status page with history, Notice before subprocessors change | Compare |
| Rakenrakenapp.comSee also Transparency alternatives to Raken | 35/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data processing agreement, Status page with history, Notice before subprocessors change | Compare |
| Assignarassignar.comSee also Transparency alternatives to Assignar | 32/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Notice before subprocessors change | Compare |
| Bluebeambluebeam.comSee also Transparency alternatives to Bluebeam | 30/100 | 2 Certifications named, Named privacy contact | 3 Data location stated, Status page with history, Notice before subprocessors change | Compare |
| Procoreprocore.comSee also Transparency alternatives to Procore | 30/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Public pricing | 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.