Transparency alternatives to PlanBase
Other Project management vendors we measure, sorted by how much we found at them and not at PlanBase. This is a comparison of disclosure, not of features or fitness.
12 shown of 75 that differ from PlanBase on at least one criterion we measured for both. Public transparency score, not a product or security rating.
PlanBase has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, 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 PlanBase” is the one that closes them.
| Vendor | Score | Found there, not found at PlanBase | Found at PlanBase, not found there | |
|---|---|---|---|---|
| Airtableairtable.comSee also Transparency alternatives to Airtable | 91/100 | 8 Data processing agreement, Subprocessor list, Status page with history, +5 | nothing | Compare |
| Smartsheetsmartsheet.comSee also Transparency alternatives to Smartsheet | 91/100 | 8 Data processing agreement, Subprocessor list, Status page with history, +5 | nothing | Compare |
| monday.commonday.comSee also Transparency alternatives to monday.com | 74/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | nothing | Compare |
| Linearlinear.appSee also Transparency alternatives to Linear | 70/100 | 5 Data processing agreement, HTTPS enforced with HSTS, No third-party tracking before consent, +2 | nothing | Compare |
| Miromiro.comSee also Transparency alternatives to Miro | 70/100 | 5 Subprocessor list, Status page with history, Uptime SLA with a figure, +2 | nothing | Compare |
| Oraora.pmSee also Transparency alternatives to Ora | 70/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | 1 Certifications named | Compare |
| Plutioplutio.comSee also Transparency alternatives to Plutio | 70/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | 1 Certifications named | Compare |
| Edworkingedworking.comSee also Transparency alternatives to Edworking | 57/100 | 5 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +2 | 2 Data location stated, Certifications named | Compare |
| Teamworkteamwork.comSee also Transparency alternatives to Teamwork | 57/100 | 5 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| OpenProjectopenproject.orgSee also Transparency alternatives to OpenProject | 48/100 | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | 2 Data location stated, Certifications named | Compare |
| Breezebreeze.pmSee also Transparency alternatives to Breeze | 61/100 | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | nothing | Compare |
| GanttPROganttpro.comSee also Transparency alternatives to GanttPRO | 52/100 | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | 2 Data location stated, Certifications named | 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.