Transparency alternatives to Camunda
Other Workflow automation vendors we measure, sorted by how much we found at them and not at Camunda. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Camunda on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Camunda has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, 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 Camunda” is the one that closes them.
| Vendor | Score | Found there, not found at Camunda | Found at Camunda, not found there | |
|---|---|---|---|---|
| Tray.aitray.aiSee also Transparency alternatives to Tray.ai | 91/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | nothing | Compare |
| Zapierzapier.comSee also Transparency alternatives to Zapier | 65/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | nothing | Compare |
| Trigger.devtrigger.devSee also Transparency alternatives to Trigger.dev | 61/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | 1 Named privacy contact | Compare |
| Pipedreampipedream.comSee also Transparency alternatives to Pipedream | 52/100 | 5 Data processing agreement, Status page with history, Public pricing, +2 | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| Mergemerge.devSee also Transparency alternatives to Merge | 61/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | nothing | Compare |
| Boomiboomi.comSee also Transparency alternatives to Boomi | 52/100 | 4 Subprocessor list, Status page with history, Public pricing, +1 | nothing | Compare |
| Tallyfytallyfy.comSee also Transparency alternatives to Tallyfy | 48/100 | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | nothing | Compare |
| Nangonango.devSee also Transparency alternatives to Nango | 43/100 | 4 Subprocessor list, Data location stated, Public pricing, +1 | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| Automation Anywhereautomationanywhere.comSee also Transparency alternatives to Automation Anywhere | 52/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | nothing | Compare |
| Kissflowkissflow.comSee also Transparency alternatives to Kissflow | 52/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | nothing | Compare |
| Knitgetknit.devSee also Transparency alternatives to Knit | 48/100 | 3 Data location stated, Public pricing, Notice before subprocessors change | nothing | Compare |
| Process Streetprocess.stSee also Transparency alternatives to Process Street | 48/100 | 3 Data location stated, Status page with history, Public pricing | nothing | 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.