Transparency alternatives to Orq
Other LLM tooling and evaluation vendors we measure, sorted by how much we found at them and not at Orq. This is a comparison of disclosure, not of features or fitness.
12 shown of 48 that differ from Orq on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Orq has 6 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Orq” is the one that closes them.
| Vendor | Score | Found there, not found at Orq | Found at Orq, not found there | |
|---|---|---|---|---|
| Langfuselangfuse.comSee also Transparency alternatives to Langfuse | 74/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Lunarylunary.aiSee also Transparency alternatives to Lunary | 52/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Openlayeropenlayer.comSee also Transparency alternatives to Openlayer | 48/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Fiddlerfiddler.aiSee also Transparency alternatives to Fiddler | 43/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Zepgetzep.comSee also Transparency alternatives to Zep | 43/100 | 2 Subprocessor list, Status page with history | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Braintrustbraintrust.devSee also Transparency alternatives to Braintrust | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | Compare |
| Mastramastra.aiSee also Transparency alternatives to Mastra | 39/100 | 2 Data processing agreement, Notice before subprocessors change | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | Compare |
| Vectorizevectorize.ioSee also Transparency alternatives to Vectorize | 39/100 | 2 Subprocessor list, Status page with history | 4 Data location stated, Certifications named, security.txt (RFC 9116), +1 | Compare |
| Confident AIconfident-ai.comSee also Transparency alternatives to Confident AI | 48/100 | 1 Data processing agreement | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Lakeralakera.aiSee also Transparency alternatives to Lakera | 35/100 | 1 Status page with history | 2 Data location stated, security.txt (RFC 9116) | Compare |
| HiddenLayerhiddenlayer.comSee also Transparency alternatives to HiddenLayer | 26/100 | 1 Notice before subprocessors change | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| LangWatchlangwatch.aiSee also Transparency alternatives to LangWatch | 26/100 | 1 No third-party tracking before consent | 3 Data location stated, HTTPS enforced with HSTS, 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.