Alternatives to n8n
Other Workflow automation vendors we measure, sorted by how much they publish that n8n does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 that differ from n8n on at least one criterion we measured for both. Public transparency score, not a product or security rating.
n8n has 4 gaps in what we could measure: Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent. The column “publishes and n8n does not” is the one that closes them.
| Vendor | Score | Publishes, and n8n does not | n8n publishes, and they do not | |
|---|---|---|---|---|
| Zapierzapier.com | 85/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Tray.aitray.ai | 75/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Boomiboomi.com | 52/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | Compare |
| Celigoceligo.com | 45/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | Compare |
| Tallyfytallyfy.com | 61/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Pipefypipefy.com | 59/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Public pricing, Certifications named | Compare |
| Process Streetprocess.st | 50/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Subprocessor list, security.txt (RFC 9116) | Compare |
| IFTTTifttt.com | 45/100 | 2 Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | Compare |
| Prismaticprismatic.io | 43/100 | 2 Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Subprocessor list, Public pricing | Compare |
| Paragonuseparagon.com | 35/100 | 2 Status page with history, HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | Compare |
| Cyclrcyclr.com | 30/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | Compare |
| Pipedreampipedream.com | 30/100 | 2 Status page with history, HTTPS enforced with HSTS | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 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.