Transparency alternatives to Flowable
Other Business process management vendors we measure, sorted by how much we found at them and not at Flowable. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Flowable on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Flowable has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, 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 Flowable” is the one that closes them.
| Vendor | Score | Found there, not found at Flowable | Found at Flowable, not found there | |
|---|---|---|---|---|
| Sorocosoroco.comSee also Transparency alternatives to Soroco | 52/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 1 Status page with history | Compare |
| Temporaltemporal.ioSee also Transparency alternatives to Temporal | 39/100 | 3 Public pricing, Uptime SLA with a figure, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| Cardanitcardanit.comSee also Transparency alternatives to Cardanit | 35/100 | 2 Data location stated, Public pricing | 2 Status page with history, Certifications named | Compare |
| Signaviosignavio.comSee also Transparency alternatives to Signavio | 35/100 | 2 Data location stated, security.txt (RFC 9116) | 1 Status page with history | Compare |
| Kestra Cloudkestra.ioSee also Transparency alternatives to Kestra Cloud | 30/100 | 2 Data processing agreement, security.txt (RFC 9116) | 2 Status page with history, Named privacy contact | Compare |
| Solvediosolvedio.comSee also Transparency alternatives to Solvedio | 22/100 | 2 Data location stated, Public pricing | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Fluxiconfluxicon.comSee also Transparency alternatives to Fluxicon | 13/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Emakinemakin.comSee also Transparency alternatives to Emakin | 30/100 | 1 Data location stated | 1 Status page with history | Compare |
| Aureaaurea.comSee also Transparency alternatives to Aurea | 26/100 | 1 Data location stated | 2 Status page with history, Certifications named | Compare |
| Qprqpr.comSee also Transparency alternatives to Qpr | 26/100 | 1 Data location stated | 2 Status page with history, Certifications named | Compare |
| Skanskan.aiSee also Transparency alternatives to Skan | 22/100 | 1 Public pricing | 2 Status page with history, Named privacy contact | Compare |
| Viflowviflow.deSee also Transparency alternatives to Viflow | 22/100 | 1 security.txt (RFC 9116) | 1 Status page with history | 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.