Transparency alternatives to Dagster
Other Data integration vendors we measure, sorted by how much we found at them and not at Dagster. This is a comparison of disclosure, not of features or fitness.
12 shown of 47 that differ from Dagster on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Dagster has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Dagster” is the one that closes them.
| Vendor | Score | Found there, not found at Dagster | Found at Dagster, not found there | |
|---|---|---|---|---|
| Estuaryestuary.devSee also Transparency alternatives to Estuary | 78/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | nothing | Compare |
| Keboolakeboola.comSee also Transparency alternatives to Keboola | 65/100 | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | nothing | Compare |
| Prefectprefect.ioSee also Transparency alternatives to Prefect | 65/100 | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 1 Named privacy contact | Compare |
| Astronomerastronomer.ioSee also Transparency alternatives to Astronomer | 61/100 | 4 Data processing agreement, Status page with history, Uptime SLA with a figure, +1 | nothing | Compare |
| Matillionmatillion.comSee also Transparency alternatives to Matillion | 61/100 | 4 Data processing agreement, Data location stated, Status page with history, +1 | 1 Public pricing | Compare |
| Redpandaredpanda.comSee also Transparency alternatives to Redpanda | 52/100 | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | 2 Public pricing, Named privacy contact | Compare |
| Snowplowsnowplow.ioSee also Transparency alternatives to Snowplow | 48/100 | 4 Data processing agreement, Subprocessor list, security.txt (RFC 9116), +1 | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Weldweld.appSee also Transparency alternatives to Weld | 57/100 | 3 Data processing agreement, Data location stated, Status page with history | 1 Named privacy contact | Compare |
| Hevo Datahevodata.comSee also Transparency alternatives to Hevo Data | 52/100 | 3 Data location stated, Status page with history, security.txt (RFC 9116) | nothing | Compare |
| Nimblewaynimbleway.comSee also Transparency alternatives to Nimbleway | 48/100 | 3 Data processing agreement, Data location stated, Uptime SLA with a figure | 1 HTTPS enforced with HSTS | Compare |
| Riveryrivery.ioSee also Transparency alternatives to Rivery | 43/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| Striimstriim.comSee also Transparency alternatives to Striim | 41/100 | 3 Subprocessor list, Data location stated, Uptime SLA with a figure | 3 Public pricing, Certifications named, Named privacy contact | 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.