Alternatives to Keboola
Other Data integration vendors we measure, sorted by how much they publish that Keboola does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from Keboola on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Keboola has 4 gaps in what we could measure: Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent. The column “publishes and Keboola does not” is the one that closes them.
| Vendor | Score | Publishes, and Keboola does not | Keboola publishes, and they do not | |
|---|---|---|---|---|
| Segmentsegment.com | 57/100 | 3 Subprocessor list, Status page with history, Uptime SLA with a figure | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Estuaryestuary.dev | 80/100 | 2 Subprocessor list, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Prefectprefect.io | 80/100 | 2 Subprocessor list, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Striimstriim.com | 58/100 | 2 Subprocessor list, Uptime SLA with a figure | 2 Data processing agreement, Certifications named | Compare |
| Weldweld.app | 57/100 | 1 Status page with history | 3 security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact | Compare |
| Hevo Datahevodata.com | 55/100 | 1 Status page with history | 1 Data processing agreement | Compare |
| Hightouchhightouch.com | 55/100 | 1 Subprocessor list | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Matillionmatillion.com | 55/100 | 1 Status page with history | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Astronomerastronomer.io | 52/100 | 1 Uptime SLA with a figure | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Snowplowsnowplow.io | 43/100 | 1 Subprocessor list | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| dbt Labsgetdbt.com | 35/100 | 1 Status page with history | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | Compare |
| Riveryrivery.io | 35/100 | 1 Status page with history | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +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.