Alternatives to Fluxicon
Other Business process management vendors we measure, sorted by how much they publish that Fluxicon does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 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 “publishes and Fluxicon does not” is the one that closes them.
| Vendor | Score | Publishes, and Fluxicon does not | Fluxicon publishes, and they do not | |
|---|---|---|---|---|
| Sorocosoroco.com | 52/100 | 6 Data processing agreement, Data location stated, Certifications named, +3 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Signaviosignavio.com | 35/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Skanskan.ai | 35/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Temporaltemporal.io | 35/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 1 No third-party tracking before consent | Compare |
| Flowableflowable.com | 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 |
| Aureaaurea.com | 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 |
| Decisionsdecisions.com | 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 |
| Celoniscelonis.com | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Mehrwerkmehrwerk.eu | 22/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 No third-party tracking before consent | Compare |
| Apromoreapromore.org | 17/100 | 2 Data location stated, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Intelliorintellior.com | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Ofeliaofelia.com | 13/100 | 2 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.