Compliance & Audit: Self-Hosted, Redaction, Logging, Retention
Request and response logging (off by default), deterministic secret & PII detection on the request path, log bodies redacted at every egress surface, login and permission audit, retention and deletion — data never leaves your network; SOC 2 controls aligned (certification in preparation), GDPR ready.
What the community actually complains about
Zhihu and Reddit: "finance / healthcare / government data can't leave the country," "calling an LLM requires an algorithm filing," "how do I redact PII," "how do I keep audit logs."
A SaaS gateway routes requests through its own servers, so compliance audits are hard; relays add data-exfiltration and resale risk.
How GateLLM does it
GateLLM deploys fully inside your network — data never leaves, satisfying data-export compliance. Request and response logs are off by default and exportable for audit; deterministic secret & PII detection runs on the request path, with log, mask (reversibly) or block per scope; stored log bodies are redacted at every egress surface and raw reveal is admin-only and audited; login and permission audit (SSO via OIDC / SAML 2.0); retention and deletion are configurable.
BYOK keys live in memory, never on disk. GDPR ready; SOC 2 Type II / ISO 27001 controls aligned (certification in preparation).
5 levers that actually land
- Request and response logging (off by default), exportable to audit systems, bodies redacted at every egress surface
- Deterministic secret & PII detection on the request path — log, mask (reversibly), or block, per scope
- Login and permission audit (SSO via OIDC / SAML 2.0)
- Configurable retention and deletion policy
- Fully self-hosted: data never leaves the network, keys in memory only