Alternatives to John Galt
Other Demand planning vendors we measure, sorted by how much they publish that John Galt does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from John Galt on at least one criterion we measured for both. Public transparency score, not a product or security rating.
John Galt has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and John Galt does not” is the one that closes them.
| Vendor | Score | Publishes, and John Galt does not | John Galt publishes, and they do not | |
|---|---|---|---|---|
| RELEXrelexsolutions.com | 30/100 | 2 Public pricing, Certifications named | 1 HTTPS enforced with HSTS | Compare |
| Slimstockslimstock.com | 30/100 | 2 Certifications named, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| Kinaxiskinaxis.com | 26/100 | 2 Certifications named, security.txt (RFC 9116) | 1 HTTPS enforced with HSTS | Compare |
| Peakpeak.ai | 26/100 | 2 Public pricing, Certifications named | 1 Data location stated | Compare |
| o9 Solutionso9solutions.com | 30/100 | 1 Certifications named | nothing | Compare |
| Flieberflieber.com | 22/100 | 1 Public pricing | 1 Data location stated | Compare |
| Onebeatonebeat.co | 17/100 | 1 No third-party tracking before consent | 2 Data location stated, Named privacy contact | Compare |
| Intuendiintuendi.com | 13/100 | 1 Data processing agreement | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Netstocknetstock.com | 9/100 | 1 Public pricing | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Inventory Plannerinventory-planner.com | 4/100 | 1 security.txt (RFC 9116) | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Lokadlokad.com | 4/100 | 1 security.txt (RFC 9116) | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | Compare |
| Cogsycogsy.com | 9/100 | nothing we found there and not here | 2 Data location stated, 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.