Evidence boundary: Open WebUI documents OpenAI-compatible connections and provider configuration. That proves an integration path exists; it does not prove which provider any particular installation uses.
Documented integration pattern
- Choose an OpenAI-compatible provider endpoint.
- Store credentials in the deployment secret system.
- Configure the base URL and model identifier.
- Test streaming, tool calls, limits, and error behavior before rollout.
Relevant provider records
- OpenAI API · official channel
- OpenRouter · router channel
First-party evidence
- Open WebUI connections documentationFirst-party connection guide.
What this page does not claim
It does not claim that the project's hosted service uses these providers in production, that the integration handles every feature, or that any private cost or revenue figure is known.
Questions developers ask
Does this page prove Open WebUI's private production stack?
No. It documents only the linked public repository or first-party documentation evidence and makes no private deployment claim.
Does APIDir know this project's provider spend or revenue?
No. APIDir does not infer private usage, cost, customer, or revenue information from a public integration.
How should I reuse this integration pattern?
Open the cited source, confirm its current license and configuration, then test the relevant provider record against your own workload.