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