Alternatives to Grist
Other Low-code and internal tools vendors we measure, sorted by how much they publish that Grist does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Grist on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Grist has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, 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 “publishes and Grist does not” is the one that closes them.
| Vendor | Score | Publishes, and Grist does not | Grist publishes, and they do not | |
|---|---|---|---|---|
| Forest Adminforestadmin.com | 65/100 | 5 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Mendixmendix.com | 52/100 | 5 Status page with history, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Pegapega.com | 52/100 | 5 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +2 | 1 Public pricing | Compare |
| Superblockssuperblocks.com | 52/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Budibasebudibase.com | 48/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | nothing | Compare |
| OutSystemsoutsystems.com | 38/100 | 4 Status page with history, Certifications named, security.txt (RFC 9116), +1 | nothing | Compare |
| Caspiocaspio.com | 48/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | nothing | Compare |
| Betty Blocksbettyblocks.com | 39/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Rowsrows.com | 39/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | nothing | Compare |
| Appianappian.com | 26/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 1 Data location stated | Compare |
| Ninoxninox.com | 35/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| DronaHQdronahq.com | 30/100 | 2 Data processing agreement, Notice before subprocessors change | 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.