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