
Argent for Open WebUI
Open WebUI's model connections point at Argent, so every chat your people send is governed. Here is what Argent governs, how it connects and what your team sets.
What Argent does with Open WebUI
Every call Open WebUI makes to a model goes through Argent first. Argent knows which agent sent it and which person owns that agent, checks it against your policy, and writes a signed record of what it decided.
- A named agent with a human owner. Each install of Open WebUI gets its own Argent agent identity tied to an accountable person, so no call is anonymous. Identity tethering
- Only the models you allow. The agent can reach only the providers and models your policy names, and a request can be swapped to an approved model. Model control
- Sensitive data handled before it leaves. Prompts and replies are scanned for personal and secret data, then redacted or blocked as your policy says. Sensitive data redaction
- Spend priced and capped. Every request is priced and metered against budgets for the agent, its owner and the teams above them. AI spend caps
- A signed record you can replay. Each decision becomes a hash-chained, signed audit record, and requests are grouped into sessions you can replay. Session replay
How Open WebUI connects
Open WebUI reaches Argent in two ways.
- TLS-inspecting forward proxy. Open WebUI keeps its normal provider settings and sends its HTTPS traffic through the Argent forward proxy and trusts your Argent certificate; the exact settings are below. The proxy signs in with the agent's own key, so every call is attributed, then runs the same checks as the gateway. It opens only known AI hosts, and its certificate is limited to those hosts.
- Gateway base URL. Open WebUI points its model URL at your Argent route and uses an Argent agent key in place of the provider key. Argent removes that key and adds the real provider credential from your vault on the way out, so the tool never holds it.
Proven with the real tool. Argent's team has driven Open WebUI itself through a live Argent gateway and checked the signed records it produced.
The same steps are in the Argent console under Integrations > AI Clients, and each agent's Connect tab gives the copy-paste values for your tenant.
What you configure
What your team sets in Open WebUI. These are the settings the Argent console shows for this tool. Values in angle brackets come from your tenant.
- Env. OPENAI_API_BASE_URL=https://<ARGENT_GATEWAY>/<tenant>/<route>/v1, OPENAI_API_KEY=<an Argent agent key>, ENABLE_OLLAMA_API=false; or HTTP_PROXY/HTTPS_PROXY env with the Argent proxy.
Make Argent the only path
Make Argent the only path for Open WebUI. These controls are documented by the platform each one belongs to (linked); pair them with the Argent settings above.
- Service / container environment (Linux, Kubernetes, CI). Sets the variables where most production SDK code runs. Vendor docs
Same settings everywhere it runs. The Argent fleet setup script and certificate bundle give every service, container and build runner the same proxy and certificate settings.
Want to see which AI tools people already run before you push anything? Start with Shadow AI discovery in watch mode. Watch before you enforce
Check that it works
Send one request and look for the signed row. Chat in Open WebUI; LLM rows in the Argent console live stream.
Every request also appears on the live stream with the agent's name and owner, and in the session view. Session replay
Where to go next
Keep going. Pages that cover the same ground from another angle.
- Use case: Rolling out copilots and chat safely
- Goals: See all AI in your company, Data loss prevention, Budget and token spend, Model control and routing, Agent identity and ownership
- Capabilities: Keyless agents, Prompt injection defense, Response screening, One-click audit evidence
- Related integrations: Warp, Ollama, LibreChat
- All integrations: Browse every AI client, provider, vault and identity source
Want this running on your own use cases?
Book a demo