Skip to main content
Open WebUI is a self-hosted AI workspace — chat, RAG over your documents, and tools, for a whole team. It is built around standard protocols and connects to any server that implements the OpenAI Chat Completions API.

​
Setup

1

Open the connections settings

In Open WebUI, go to Admin Settings → Connections → OpenAI, then click Add Connection.
2

Fill in the connection

3

Filter the model list

Opper’s catalog is large. Under Model IDs (Filter), add the IDs you want your users to see — type each one and click +. Save.
Or set it at startup with environment variables:
Running Open WebUI in Docker? The gateway is a public endpoint, so no host.docker.internal rewriting is needed — that caveat only applies to model servers on your host machine.

​
Choosing a model

Open WebUI verifies a connection by calling /models, which Opper implements, so auto-detection works and the picker fills itself. Because the catalog runs to hundreds of entries, the Model IDs (Filter) allowlist is strongly recommended — the same advice Open WebUI gives for any large gateway.

​
Multi-user usage

Open WebUI is multi-user by design. Forward per-user tags with the X-Opper-Tags header to break usage down in Opper analytics — see Tags and usage attribution.

​
Troubleshooting

Verification calls /models with a bearer token. If it errors while chat completions succeed, add your model IDs to the Model IDs (Filter) allowlist manually and carry on.
Expected without a filter. Add an allowlist under Model IDs (Filter), or narrow the key’s project with model access rules so the filter happens server-side.
Check the key is an Opper key (they start with op-) and that it’s on the OpenAI connection, not Ollama.

Model access rules

Filter the catalog server-side, per project.

LibreChat

The other self-hosted chat platform.