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