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