Privileged in five minutes.
One DPA, one firewall rule, one API. Everything below ships as an engineered default — nothing to negotiate, nothing persists by default.
Sign the DPA
One Data Processing Agreement covering zero retention by default, no training on your data, and tenant isolation. Signed in days, not months.
Whitelist static egress
Traffic exits through a fixed infrastructure identity. Add it to your firewall once. Default egress posture is deny unless explicitly allowed.
Call the API
Point your existing OpenAI-compatible client at the Privileged gateway. The runtime provisions, streams, and is destroyed when the session closes.
curl https://api.privilegedinfra.com/v1/chat/completions \ -H "Authorization: Bearer pi_live_•••" \ -H "Content-Type: application/json" \ -d '{"model":"privileged/legal-large","messages":[…],"stream":true}'
Ephemeral runtime
Environments provision on demand, run in RAM, and are destroyed on session close. No persistent disk is attached to a privileged workload.
Static egress
All traffic exits through controlled, static egress with a fixed identity your firewall can whitelist. Deny by default.
Private models
Host private and fine-tuned models in isolated environments, or run open models — all through one logical identifier. LoRA adapters supported.
Zero retention by default
Prompts, responses, and documents are not written to durable storage in the paths Privileged controls. Persistent workflows are opt-in.
Zero retention applies within the boundaries Privileged controls. Persistent workflows are opt-in. No certification is claimed.