Transparency alternatives to Botpress
Other Conversational AI vendors we measure, sorted by how much we found at them and not at Botpress. This is a comparison of disclosure, not of features or fitness.
12 shown of 41 that differ from Botpress on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Botpress has 5 gaps in what we could measure: Subprocessor list, Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Botpress” is the one that closes them.
| Vendor | Score | Found there, not found at Botpress | Found at Botpress, not found there | |
|---|---|---|---|---|
| MessageBirdbird.comSee also Transparency alternatives to MessageBird | 87/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 1 Uptime SLA with a figure | Compare |
| Sendbirdsendbird.comSee also Transparency alternatives to Sendbird | 52/100 | 3 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Data location stated, Uptime SLA with a figure | Compare |
| Netominetomi.comSee also Transparency alternatives to Netomi | 48/100 | 3 Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | Compare |
| Infobipinfobip.comSee also Transparency alternatives to Infobip | 43/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data location stated, Certifications named, Uptime SLA with a figure, +2 | Compare |
| Witivio AI Desk Prowitivio.comSee also Transparency alternatives to Witivio AI Desk Pro | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 6 Data processing agreement, Data location stated, Certifications named, +3 | Compare |
| Forethoughtforethought.aiSee also Transparency alternatives to Forethought | 61/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Public pricing, Uptime SLA with a figure | Compare |
| Sinchsinch.comSee also Transparency alternatives to Sinch | 57/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, Uptime SLA with a figure | Compare |
| Moveworksmoveworks.comSee also Transparency alternatives to Moveworks | 35/100 | 2 Status page with history, HTTPS enforced with HSTS | 5 Data processing agreement, Public pricing, Uptime SLA with a figure, +2 | Compare |
| Landbotlandbot.ioSee also Transparency alternatives to Landbot | 30/100 | 2 Status page with history, HTTPS enforced with HSTS | 5 Data processing agreement, Data location stated, Certifications named, +2 | Compare |
| Chatfuelchatfuel.comSee also Transparency alternatives to Chatfuel | 26/100 | 2 Status page with history, HTTPS enforced with HSTS | 6 Data processing agreement, Data location stated, Certifications named, +3 | Compare |
| Leena AIleena.aiSee also Transparency alternatives to Leena AI | 22/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| Yellow.aiyellow.aiSee also Transparency alternatives to Yellow.ai | 55/100 | 1 HTTPS enforced with HSTS | 1 Data location stated | 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.