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