Transparency alternatives to Steep
Other Business intelligence vendors we measure, sorted by how much we found at them and not at Steep. This is a comparison of disclosure, not of features or fitness.
12 shown of 39 that differ from Steep on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Steep has 8 gaps in what we could measure: Data location stated, Status page with history, 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 Steep” is the one that closes them.
| Vendor | Score | Found there, not found at Steep | Found at Steep, not found there | |
|---|---|---|---|---|
| Databoxdatabox.comSee also Transparency alternatives to Databox | 57/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Countcount.coSee also Transparency alternatives to Count | 48/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Metabasemetabase.comSee also Transparency alternatives to Metabase | 43/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Jettijetti.comSee also Transparency alternatives to Jetti | 39/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Hexhex.techSee also Transparency alternatives to Hex | 35/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Cluviocluvio.comSee also Transparency alternatives to Cluvio | 48/100 | 3 Data location stated, Status page with history, Certifications named | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Sisensesisense.comSee also Transparency alternatives to Sisense | 43/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 Data processing agreement, Public pricing | Compare |
| Deepnotedeepnote.comSee also Transparency alternatives to Deepnote | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Presetpreset.ioSee also Transparency alternatives to Preset | 35/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| GoodDatagooddata.comSee also Transparency alternatives to GoodData | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Subprocessor list, Public pricing | Compare |
| Growgrow.comSee also Transparency alternatives to Grow | 26/100 | 3 Data location stated, Status page with history, Named privacy contact | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | Compare |
| Yellowfinyellowfinbi.comSee also Transparency alternatives to Yellowfin | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | 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.