Skip to content
MetaioLab MetaioLab Docs
Open metaiolab.com

Open WebUI

Best for: teams that want a browser-based, self-hosted AI workspace.

Why people use it

Section titled "Why people use it"

Open WebUI is popular because it gives you:

  • a strong web interface
  • team and admin workflows
  • multiple connection support
  • broad compatibility with OpenAI-style backends
Section titled "Recommended MetaioLab setup"

Use MetaioLab through the OpenAI-compatible connection path.

In the admin UI

Section titled "In the admin UI"

Go to Settings → Connections and add or edit an OpenAI connection.

Fill in:

  • Base URL: your MetaioLab API URL, usually ending in /v1
  • API key: your MetaioLab API key
  • Model IDs: use the models exposed by your gateway

Then verify the connection and save it.

Environment-variable setup

Section titled "Environment-variable setup"

If you prefer deployment-level configuration, Open WebUI also supports environment variables such as:

  • ENABLE_OPENAI_API=true
  • OPENAI_API_BASE_URL
  • OPENAI_API_BASE_URLS

The key point

Section titled "The key point"

Open WebUI works especially well when you want one shared portal for many users, not just a single-user desktop client.

Common mistakes

Section titled "Common mistakes"

Forgetting /v1

Section titled "Forgetting /v1"

Most OpenAI-compatible Open WebUI setups expect the API base URL to include /v1.

Model list confusion

Section titled "Model list confusion"

If the connection is valid but no model works, check what your gateway returns from /v1/models.

Wrong audience fit

Section titled "Wrong audience fit"

If the user just wants a desktop client, Cherry Studio is often easier.

References

Section titled "References"