Transparency alternatives to Pory
Other Low-code and internal tools vendors we measure, sorted by how much we found at them and not at Pory. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Pory on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Pory has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Pory” is the one that closes them.
| Vendor | Score | Found there, not found at Pory | Found at Pory, not found there | |
|---|---|---|---|---|
| Retoolretool.comSee also Transparency alternatives to Retool | 61/100 | 6 Subprocessor list, Status page with history, Certifications named, +3 | 2 Data location stated, No third-party tracking before consent | Compare |
| Forest Adminforestadmin.comSee also Transparency alternatives to Forest Admin | 70/100 | 5 Subprocessor list, Status page with history, Certifications named, +2 | 1 No third-party tracking before consent | Compare |
| Mendixmendix.comSee also Transparency alternatives to Mendix | 52/100 | 4 Status page with history, Certifications named, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Pegapega.comSee also Transparency alternatives to Pega | 52/100 | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | 2 Public pricing, No third-party tracking before consent | Compare |
| OutSystemsoutsystems.comSee also Transparency alternatives to OutSystems | 24/100 | 4 Status page with history, Certifications named, security.txt (RFC 9116), +1 | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | Compare |
| Caspiocaspio.comSee also Transparency alternatives to Caspio | 57/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 1 HTTPS enforced with HSTS | Compare |
| Teableteable.ioSee also Transparency alternatives to Teable | 57/100 | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 1 No third-party tracking before consent | Compare |
| Superblockssuperblocks.comSee also Transparency alternatives to Superblocks | 52/100 | 3 Subprocessor list, Certifications named, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Betty Blocksbettyblocks.comSee also Transparency alternatives to Betty Blocks | 48/100 | 3 Status page with history, Certifications named, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Budibasebudibase.comSee also Transparency alternatives to Budibase | 48/100 | 3 Status page with history, Certifications named, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Jet Adminjetadmin.ioSee also Transparency alternatives to Jet Admin | 48/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 2 Data location stated, No third-party tracking before consent | Compare |
| DronaHQdronahq.comSee also Transparency alternatives to DronaHQ | 35/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | 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.