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