Live in an afternoon, not a quarter
No infrastructure to stand up — redzohu sits in front of the models you already use.
What actually happens to a request
A trace of one real request through redzohu, step by step.
Ingest Request
Your app calls the redzohu endpoint instead of the model directly — no code changes beyond swapping the base URL.
Received POST /v1/chat. Schema valid, API key verified, rate limit OK (42/500 this minute).
Classify & Detect
Every field is scanned for PII, secrets, and custom sensitive patterns before anything leaves your perimeter.
Flagged 3 sensitive fields — card_number, email, ssn. Matched against 2 custom rules. 0 false positives.
Tokenize & Vault
Flagged fields are replaced with format-preserving tokens. The real values are encrypted and written to the vault — never the model.
Tokenized 3 fields, shape preserved (4242… → 8823…). Original values sealed in vault under request #8231.
Frontier Model
The model receives the tokenized payload — it never sees a real card number, email, or SSN.
Model responded in 640ms. Output references 1 token — no raw sensitive data touched the model.
Detokenize Response
Token references in the model's output are swapped back for real values via a vault lookup before your app sees them.
Rehydrated 1 token from vault. Response now matches the original data shape your app expects.
Log & Verify
Every step — detection, tokenization, detokenization — is written to a hash-chained, tamper-evident audit trail.
Logged request #8231 end to end, chained onto the tenant's audit trail. Available in audit export.