Transparency alternatives to BLAZE
Other Cannabis retail and compliance vendors we measure, sorted by how much we found at them and not at BLAZE. This is a comparison of disclosure, not of features or fitness.
12 shown of 30 that differ from BLAZE on at least one criterion we measured for both. Public transparency score, not a product or security rating.
BLAZE has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, 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 BLAZE” is the one that closes them.
| Vendor | Score | Found there, not found at BLAZE | Found at BLAZE, not found there | |
|---|---|---|---|---|
| Flowhubflowhub.comSee also Transparency alternatives to Flowhub | 39/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 Certifications named, Uptime SLA with a figure | Compare |
| Weedmapsweedmaps.comSee also Transparency alternatives to Weedmaps | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 2 Certifications named, Uptime SLA with a figure | Compare |
| Greenlinegetgreenline.coSee also Transparency alternatives to Greenline | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | 2 Certifications named, Uptime SLA with a figure | Compare |
| BakedBotbakedbot.aiSee also Transparency alternatives to BakedBot | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 2 Certifications named, Uptime SLA with a figure | Compare |
| LeafLinkleaflink.comSee also Transparency alternatives to LeafLink | 22/100 | 2 Data location stated, Public pricing | 2 Certifications named, Uptime SLA with a figure | Compare |
| POSaBITposabit.comSee also Transparency alternatives to POSaBIT | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Certifications named, Uptime SLA with a figure | Compare |
| Trymtrym.ioSee also Transparency alternatives to Trym | 22/100 | 2 Data location stated, Public pricing | 2 Certifications named, Uptime SLA with a figure | Compare |
| AIQaiq.comSee also Transparency alternatives to AIQ | 17/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 Uptime SLA with a figure | Compare |
| Canixcanix.comSee also Transparency alternatives to Canix | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Certifications named, Uptime SLA with a figure | Compare |
| Confident LIMSconfidentlims.comSee also Transparency alternatives to Confident LIMS | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Certifications named, Uptime SLA with a figure | Compare |
| GrowFlowgrowflow.comSee also Transparency alternatives to GrowFlow | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Certifications named, Uptime SLA with a figure | Compare |
| Meadowgetmeadow.comSee also Transparency alternatives to Meadow | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 2 Certifications named, Uptime SLA with a figure | 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.