SaaS Ranking

Alternatives to Lexion

Other Contract management vendors we measure, sorted by how much they publish that Lexion does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 22 that differ from Lexion on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Lexion has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Lexion does not” is the one that closes them.

VendorScorePublishes, and Lexion does notLexion publishes, and they do not
Ironcladironcladapp.com 52/100 4 Subprocessor list, Public pricing, Notice before subprocessors change, +1 1 HTTPS enforced with HSTS Compare
Congaconga.com 48/100 3 Subprocessor list, Status page with history, Named privacy contact 1 Certifications named Compare
Gatekeepergatekeeperhq.com 39/100 3 Data processing agreement, Public pricing, Notice before subprocessors change 2 Data location stated, Certifications named Compare
Jurojuro.com 40/100 2 Status page with history, Public pricing 1 HTTPS enforced with HSTS Compare
Contractbookcontractbook.com 35/100 2 Subprocessor list, Public pricing 1 Data location stated Compare
DocJurisdocjuris.com 30/100 2 Status page with history, Public pricing 2 Data location stated, Certifications named Compare
fynkfynk.com 25/100 2 Public pricing, security.txt (RFC 9116) 2 Data location stated, Certifications named Compare
Agiloftagiloft.com 30/100 1 Named privacy contact nothing Compare
Outlawgetoutlaw.com 30/100 1 Named privacy contact nothing Compare
Summizesummize.com 20/100 1 Uptime SLA with a figure 1 Data location stated Compare
Avokaadoavokaado.io 17/100 1 Status page with history 2 Data location stated, Certifications named Compare
Cobriefcobrief.app 9/100 1 Public pricing 3 Data location stated, Certifications named, HTTPS enforced with HSTS 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.