Alternatives to Looker
Other Business intelligence vendors we measure, sorted by how much they publish that Looker does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 28 that differ from Looker on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Looker has 8 gaps in what we could measure: Data processing agreement, Data location stated, Status page with history, Certifications named, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Looker does not” is the one that closes them.
| Vendor | Score | Publishes, and Looker does not | Looker publishes, and they do not | |
|---|---|---|---|---|
| Databoxdatabox.com | 55/100 | 4 Data processing agreement, Data location stated, Status page with history, +1 | 3 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| Klipfolioklipfolio.com | 48/100 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | 3 Subprocessor list, Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| ThoughtSpotthoughtspot.com | 57/100 | 3 Data location stated, Certifications named, Notice before subprocessors change | 1 Uptime SLA with a figure | Compare |
| Cluviocluvio.com | 55/100 | 3 Data location stated, Status page with history, Certifications named | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| Hexhex.tech | 35/100 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | 2 Subprocessor list, Uptime SLA with a figure | Compare |
| Omniomni.co | 30/100 | 3 Data location stated, Status page with history, Certifications named | 4 Subprocessor list, Public pricing, Uptime SLA with a figure, +1 | Compare |
| Lightdashlightdash.com | 60/100 | 2 Data location stated, Status page with history | 1 Uptime SLA with a figure | Compare |
| Sisensesisense.com | 40/100 | 2 Status page with history, Certifications named | 2 Public pricing, Uptime SLA with a figure | Compare |
| Steepsteep.app | 40/100 | 2 Data processing agreement, Status page with history | 3 Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| Countcount.co | 35/100 | 2 Status page with history, Certifications named | 2 Subprocessor list, Uptime SLA with a figure | Compare |
| Deepnotedeepnote.com | 35/100 | 2 Data location stated, security.txt (RFC 9116) | 2 Subprocessor list, Uptime SLA with a figure | Compare |
| GoodDatagooddata.com | 35/100 | 2 Certifications named, security.txt (RFC 9116) | 2 Public pricing, Uptime SLA with a figure | 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.