Using Ace Data Cloud in Open WebUI
Open WebUI (formerly Ollama WebUI) is an open-source AI client designed for team/enterprise scenarios, natively supporting multi-user and RBAC, knowledge base and RAG, model parallel comparison, and Pipelines extension, and can be fully privately deployed. It natively supports custom OpenAI-compatible endpoints, allowing access to Ace Data Cloud, with one API Token accessing over 60 large models including Claude, GPT, Gemini, Grok, DeepSeek, Kimi, GLM, etc. This article describes the configuration process.
¶ Application Process
To access Ace Data Cloud in Open WebUI, first go to the Ace Data Cloud Console to obtain your API Token for backup.

If you are not logged in or registered, you will be automatically redirected to the login page inviting you to register and log in. After logging in or registering, you will be automatically returned to the current page.
There is a free quota available for first-time applicants, allowing you to experience Ace Data Cloud's model services for free.
¶ Deploying and Configuring Ace Data Cloud
Open WebUI connects to OpenAI-compatible endpoints through environment variables, and can be deployed with a single Docker command (replace {token} with your Token):
docker run -d \
--name open-webui \
-p 3000:8080 \
-e WEBUI_SECRET_KEY=$(openssl rand -base64 32) \
-e OPENAI_API_BASE_URL=https://api.acedata.cloud/v1 \
-e OPENAI_API_KEY={token} \
-v open-webui:/app/backend/data \
ghcr.io/open-webui/open-webui:main
| Environment Variable | Function |
|---|---|
OPENAI_API_BASE_URL |
Ace Data Cloud entry, must end with /v1 |
OPENAI_API_KEY |
Your Token |
WEBUI_SECRET_KEY |
Session encryption key, automatically generated |
-v open-webui:/app/backend/data |
Persistent conversation/user data |
Open http://your-server-IP:3000, and the first registered account will automatically become the administrator. Note the path rules for the Base URL:
| OPENAI_API_BASE_URL | Actual Request | Result |
|---|---|---|
https://api.acedata.cloud/v1 |
https://api.acedata.cloud/v1/chat/completions |
Correct |
https://api.acedata.cloud/openai |
https://api.acedata.cloud/openai/chat/completions |
Also available |
https://api.acedata.cloud/openai/v1 |
https://api.acedata.cloud/openai/v1/chat/completions |
404 (/openai does not have /v1) |
After logging in, go to Admin Panel → Settings → Connections and click "Verify Connection" to validate; in Settings → Models, you can filter and pin commonly used models.
In addition to using environment variables, Open WebUI also supports adding connections directly in the interface: go to Admin Settings → Connections, click ➕ and fill in the URL (
https://api.acedata.cloud/v1) and API Key, and Open WebUI will automatically call/modelsto fetch the model list. For more details, see the official documentation Starting With OpenAI-Compatible Servers.
¶ Recommended Models
The following model IDs have been verified as available through Ace Data Cloud GET /v1/models and POST /v1/chat/completions:
| Family | Model ID | Notes |
|---|---|---|
| GPT | gpt-5, gpt-5-mini, gpt-4o |
OpenAI flagship / cost-effective / classic multimodal |
| Claude | claude-opus-4-8, claude-sonnet-4-6 |
Anthropic flagship / balanced |
| Gemini | gemini-3.1-pro, gemini-3-flash-preview |
Google multimodal / fast |
| Grok | grok-4 |
xAI, natively connected |
| DeepSeek | deepseek-v3 |
High cost-performance, Chinese-friendly |
| Kimi | kimi-k2.5 |
Long text |
Open WebUI will automatically call /v1/models to fetch all models by default. For a complete list of models, please refer to the Ace Data Cloud Service Documentation.
¶ Verification of Integration
If you are unsure whether the issue lies with Open WebUI or the network, you can first verify the endpoint directly using curl (replace {token} with your Token):
curl -X POST 'https://api.acedata.cloud/v1/chat/completions' \
-H 'Authorization: Bearer {token}' \
-H 'Content-Type: application/json' \
-d '{
"model": "gpt-5",
"messages": [{"role": "user", "content": "ping"}]
}'
Returning an OpenAI-compatible chat.completion object indicates that both the Token and endpoint are ready; if you receive HTTP 403 used_up, it means the Token is valid but the balance is insufficient, and you can recharge at the console.
¶ Advanced: Knowledge Base and Multi-User
The knowledge base (RAG) in Open WebUI uses ChromaDB by default to store vectors, and the embedding model can be specified as text-embedding-3-large (via Ace Data Cloud). The original document only exists on your server, and only the matched segments will be sent to the model. In Admin Panel → Users, you can manage user roles (Pending / User / Admin); it is recommended to set the "Default User Role" to pending, requiring new users to be reviewed before they can use it, to prevent unauthorized registrations from consuming quotas. If using nginx as a reverse proxy, please add proxy_buffering off; and client_max_body_size 100M;.
¶ Frequently Asked Questions
¶ Prompt Connection error / 404
This is usually because OPENAI_API_BASE_URL is written as .../openai/v1 or is missing /v1. Change it to https://api.acedata.cloud/v1.
¶ Unable to chat after uploading documents
In the RAG settings of the Admin Panel, set the embedding model to text-embedding-3-large (OpenAI provider).
¶ Data loss after container restart
You need to mount the data volume -v open-webui:/app/backend/data at startup.
