Transparency alternatives to BakedBot
Other Cannabis retail and compliance vendors we measure, sorted by how much they publish that BakedBot does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 30 that differ from BakedBot on at least one criterion we measured for both. Public transparency score, not a product or security rating.
BakedBot 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, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and BakedBot does not” is the one that closes them.
| Vendor | Score | Publishes, and BakedBot does not | BakedBot publishes, and they do not | |
|---|---|---|---|---|
| Flowhubflowhub.com | 39/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Weedmapsweedmaps.com | 35/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Greenlinegetgreenline.co | 26/100 | 2 Data location stated, Public pricing | 1 security.txt (RFC 9116) | Compare |
| LeafLinkleaflink.com | 22/100 | 2 Data location stated, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| POSaBITposabit.com | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Trymtrym.io | 22/100 | 2 Data location stated, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| AIQaiq.com | 17/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Canixcanix.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Confident LIMSconfidentlims.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Meadowgetmeadow.com | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Nabisnabis.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| BLAZEblaze.me | 9/100 | 2 Certifications named, Uptime SLA with a figure | 2 security.txt (RFC 9116), Named privacy contact | 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.