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