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