How we assess vendors

Why there’s no numeric score

Most comparison sites give every product a number out of 5 or 10. We don’t, for a simple reason: nobody on this site has run every one of these systems hands-on in a live lab, so a precise numeric score would imply a level of tested confidence we don’t have. Instead, each fiche carries an assessment by dimension: a qualitative reading of the publicly available, sourced evidence, shown as color-coded cards rather than a bar chart.

There’s also no aggregate star rating anywhere on this site, and no aggregateRating in the page’s structured data. That kind of rating is meant for real user reviews, not editorial reading of vendor documentation.

The three levels

Each dimension is marked one of three ways:

• Strong — the evidence found is clearly positive and reasonably specific (a dedicated compliance document, a large, consistently strong independent review base, a concrete deployment option).
• Mixed — the evidence is genuinely split: some positive signal, some real limitation, or a small/uncertain sample size that shouldn’t be over-weighted.
• Limited — the evidence found is thin, absent, or points to a real constraint (no published pricing with no third-party estimate either, no independent reviews found, a standard left unaddressed).

Every card also carries a short rationale explaining specifically why it landed where it did, with a link back to the fiche’s sources for anyone who wants to check the underlying evidence themselves.

The six dimensions

• Fit — how well the vendor’s stated positioning (research discipline, team size, deployment model) matches the segments it’s compared against here.
• Compliance — a roll-up of the standard-by-standard evidence table on each fiche (documented / vendor-claim / unknown / not-supported), not a separate judgment call.
• Deployment — how much flexibility the vendor offers (cloud, on-premise, hybrid) and how specific the vendor is about implementation timelines.
• Pricing transparency — whether the vendor publishes pricing at all, and if not, whether a credible third-party estimate exists.
• Usability — what independent reviewers (primarily G2) say about day-to-day use, weighted by how many reviews that’s based on.
• Support — independent review signal specifically about support and service quality, again weighted by sample size.

Compliance evidence levels, specifically

Because compliance is the dimension most likely to matter for a regulated lab, it gets its own table on every fiche, standard by standard, using four levels:

• Documented — the vendor publishes a specific, citable page or document mapping its product to that standard.
• Vendor claim — the vendor states support for the standard without that level of detail or a dedicated source.
• Unknown — nothing on this was found during research; it does not mean the vendor lacks the capability, only that we couldn’t verify it.
• Not supported — the vendor or another credible source explicitly states the standard isn’t supported.

For an electronic lab notebook, two of these matter more than the rest. 21 CFR Part 11 and EU Annex 11 govern whether notebook entries and electronic signatures can stand as regulated records, which is the whole point of replacing a paper notebook in a GxP environment. ISO 27001 and SOC 2 matter because an ELN usually holds a lab’s unpublished research data in a vendor’s cloud. Where a vendor documents an audit trail and signature workflow specifically, that’s called out on the fiche.

See Methodology for the sourcing rules behind all of this.