기본 콘텐츠로 건너뛰기

Open WebUI Playbook: A Private ChatGPT for a Small Team

Summary: Open WebUI is a free, self-hosted chat interface that lets a small team share one private "ChatGPT" connected to local models (through Ollama) or to the paid APIs you already use. This playbook walks through a realistic rollout for a team of up to about 50 people: install it with Docker, lock down sign-ups, connect a model, load your documents into a knowledge base, build a team assistant, and keep everything backed up. Every step and number below was checked against Open WebUI's official documentation on 2026-10-27.

The use case: one private AI workspace your team actually controls

Many small teams end up in the same spot: half the office pastes work into personal chatbot accounts, nobody knows which documents left the building, and there is no shared place to keep good prompts. Open WebUI solves the "one shared place" part. You run it on a machine you control, everyone signs in with their own account, and you decide which models and documents each group can see.

It is worth being precise about privacy, because the docs are. Open WebUI keeps chats, users and uploaded files in its own storage on your server, but where document content is processed depends on the extraction, embedding and model providers you connect. If you point it at a cloud API, your prompts still go to that provider. If you pair it with a local model through Ollama, they can stay on your hardware.

This guide assumes a team of 50 or fewer. That number matters for licensing, which is covered in the comparison section below.

Step 1: Install it with Docker (about 10 minutes)

Docker is the officially recommended route and works on macOS, Linux (including ARM boards) and Windows. Pick a machine that stays on, such as a small office server or a cloud VM, then:

  1. Generate a secret key with openssl rand -hex 32. Keep it somewhere safe. The docs warn that without a fixed WEBUI_SECRET_KEY, every time the container is recreated everyone gets logged out.
  2. Run the container:
    docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data -e WEBUI_SECRET_KEY=your-secret-key --name open-webui --restart always ghcr.io/open-webui/open-webui:main
  3. Open http://your-server:3000 in a browser. The -v open-webui:... part is the volume that holds all chats, users and settings, so never drop it.

Which image should you pick?

The default :main image includes local embedding and speech-to-text models, which is what you want if your team will chat with documents and you don't already run separate services for that. The :slim image is roughly 197 MB to download instead of 1.62 GB (the docs' figure for Linux/amd64, checked October 16, 2026), but it hands embeddings, PDF and Office extraction, and voice off to external services. If you choose slim and skip that setup, uploading a PDF returns an error. For a first team rollout, :main is the simpler choice. There is also :cuda for NVIDIA GPUs (add --gpus all) and :ollama, which bundles Ollama in the same container.

If you prefer Python, Open WebUI supports Python 3.11 and 3.12 only (3.13 is not supported yet); install with pip install open-webui and start with open-webui serve, which listens on port 8080.

Step 2: Claim the admin account and close the front door

This is the step people skip and regret. The very first account created on a fresh install automatically becomes the Admin. So create your own account immediately after the container starts, before you share the URL with anyone.

Then decide what happens when a colleague signs up. New sign-ups get the default user role, which you control with the DEFAULT_USER_ROLE environment variable:

  • pending: the account exists but cannot do anything until an admin approves it. The docs recommend this for shared instances.
  • user: immediate access with default permissions.
  • admin: every new person becomes a full administrator. Avoid this.

Add -e DEFAULT_USER_ROLE=pending to your docker command, then approve people from Admin Panel > Users. Remember that admins bypass most granular permissions, so keep the admin list short.

Step 3: Connect a model

Option A: local models through Ollama

If Ollama runs on the same machine, Open WebUI tries to connect automatically. If it doesn't, go to Settings > Admin > Connections, find Manage Ollama API Connections, and set the URL. For Docker users with Ollama on the host, the docs give http://host.docker.internal:11434, which is exactly why the install command includes the --add-host flag. The Manage button in that same section lets you download models straight from the admin UI. If Ollama itself misbehaves, our Ollama troubleshooting guide covers the usual causes.

Option B: a cloud API

Open WebUI also connects to OpenAI, Anthropic and any OpenAI-compatible endpoint. This gives your team stronger models without each person needing a subscription, but you pay per use and data goes to that provider. Many teams mix both: a local model for sensitive documents, a cloud model for heavy writing or coding.

If you've been running models on a single desktop with LM Studio, that is a good way to test which local model is good enough before you put it in front of the whole team.

Step 4: Turn your documents into a knowledge base

This is where Open WebUI becomes more useful than a plain chatbot. The official first-run flow:

  1. Click Workspace > Knowledge, then Create, and give it a name and description (for example "Employee handbook").
  2. Upload a small text-based PDF or text file first and wait for processing to finish before asking about it.
  3. In a chat, type # to reference the knowledge base, or attach it to a model in Workspace > Models > Edit.
  4. Ask a question whose answer you know is in the file, and ask for a quote. Compare the answer with the source before trusting it for real work.

Two practical details from the docs: focused retrieval works best with a model that supports native function calling, with the Knowledge Base tools enabled, and you can control who sees each knowledge base from its three-dot menu, under Access. Start with one small, clean collection rather than dumping a whole shared drive in on day one.

Step 5: Build team assistants with Workspace > Models

A "model" in Open WebUI's workspace is really a preset on top of a base model: you bind a system prompt, knowledge bases, tools and parameter overrides to it, then share it. Practical examples for a small business:

  • Policy helper: base model plus the handbook knowledge base, with a system prompt that says to answer only from the documents and quote the passage.
  • Proposal drafter: a stronger cloud model with your proposal template and tone guide in the system prompt.
  • Meeting summarizer: a fixed output format (decisions, owners, deadlines) so every summary looks the same.

System prompts can include variables such as {{USER_NAME}} and {{CURRENT_DATE}}, written without spaces inside the braces. The docs are honest that a system prompt is an instruction, not a guarantee: how closely it is followed depends on the base model.

Step 6: Use groups so the right people see the right things

Groups live in Admin Panel > Users > Groups and do two jobs: granting feature permissions and controlling access to private models, knowledge bases and tools. One rule to know before you design them: permissions are additive. If someone is in two groups and only one allows image generation, they get image generation. There is no "deny." The docs suggest keeping permission groups (who can use which features) separate from sharing groups (Sales, Engineering), which keeps things readable as the team grows.

Step 7: Back up before every update

All data lives in the open-webui volume. The official backup one-liner archives it to the current folder:

docker run --rm -v open-webui:/data -v $(pwd):/backup alpine tar czf /backup/openwebui-$(date +%Y%m%d).tar.gz /data

Updating means pulling a newer image and recreating the container, and your data stays in the volume. The catch: if a release runs a database migration, rolling the container back does not undo it, so you need a backup taken before the update. The docs recommend backing up before every update and on a daily or weekly schedule.

Open WebUI vs AnythingLLM vs LibreChat

All three are self-hosted, multi-user AI chat apps. The facts below come from each project's own README, license and pricing pages, checked on 2026-10-27.

Open WebUI AnythingLLM LibreChat
Self-hosting cost Free Free (Docker) Free
License Open WebUI License (BSD-3 plus a branding clause since v0.6.6) MIT MIT
Rebranding Allowed with 50 or fewer users in a 30-day period; above that, branding must stay unless you have permission or an enterprise license White-labeling in the Docker version MIT, no branding clause
Hosted option Self-hosted (enterprise licensing available) Cloud Basic $50/month, Pro $99/month, Enterprise by quote Self-hosted
Strength Knowledge bases, model presets, groups and permissions, SSO/LDAP, SCIM Desktop app for Mac, Windows and Linux; workspaces; agents; multi-user only in Docker Multi-provider chat, agents with MCP, admin panel for users, groups and roles; OAuth2 and LDAP login

In short: choose Open WebUI if documents and fine-grained team access are the point; AnythingLLM if you want a no-server desktop app or a hosted plan someone else maintains; LibreChat if you mainly want one clean interface for many paid model providers with an MIT license.

Editor's note

Who this is for: small teams, clinics, agencies or workshops with someone comfortable running a Docker container, who want one controlled place for AI chat and internal documents. Not for: a solo user who just wants a chatbot (a desktop app is simpler), or anyone who needs a vendor to own uptime and support without an enterprise contract.

Gotchas I verified in the docs: the first account becomes admin, so create yours before sharing the link; forgetting WEBUI_SECRET_KEY logs everyone out after each container rebuild; the slim image returns errors on PDF uploads unless you connect an extraction service; and group permissions only add, never subtract.

Common errors and fixes: "can't reach Ollama" from inside Docker is usually a localhost problem, so use http://host.docker.internal:11434; a knowledge base that seems ignored often means the model doesn't support tool calling well, so test with a stronger model before rewriting prompts; and a rollback that won't start after an update usually needs the pre-update backup because of a database migration.

FAQ

Is Open WebUI really free for a business?

Yes, self-hosting is free. The license asks you to keep the Open WebUI branding visible, unless you have 50 or fewer users in a 30-day period, are a substantive contributor with written permission, or hold an enterprise license.

Does my data stay private?

Chats, users and files are stored on your server. Prompts and document content go wherever your connected providers are: a cloud API sees what you send it, while a local Ollama model keeps processing on your hardware.

Can I automate things around it, like sending chat results to other apps?

Open WebUI has tools, MCP support and webhooks, and many teams pair it with an automation tool. If you go that route with n8n and local models, our n8n AI Agent errors guide covers the connection problems you're likely to hit.

Start with one clean knowledge base, one shared assistant and approval-only sign-ups, and you'll have a private team AI that's easy to grow.

Official Open WebUI documentation screenshots are attached at the end of this post. Image credit: Open WebUI Docs (docs.openwebui.com).

Last verified: 2026-10-27

Sources:
Open WebUI Docs: Quick Start
Open WebUI Docs: Roles
Open WebUI Docs: Groups
Open WebUI Docs: Starting with Ollama
Open WebUI Docs: Knowledge
Open WebUI Docs: Models
Open WebUI Docs: Updating and Backup
Open WebUI License
AnythingLLM on GitHub
AnythingLLM Pricing
LibreChat on GitHub

Uploaded Image Uploaded Image Uploaded Image Uploaded Image

댓글

이 블로그의 인기 게시물

브루(Vrew) 요금제 정리: 무료 200크레딧으로 어디까지 쓸 수 있나

요약: 영상 자막 편집기 브루(Vrew)는 2026년 4월 22일부터 기능별 사용량 대신 '통합 크레딧' 하나로 요금을 매겨요. 무료 플랜은 매달 200크레딧이 들어오는데, 음성 분석(자동 자막)만 쓰면 최대 200분 분량이라 짧은 영상 몇 편은 충분하지만, 영상 초반의 Vrew 마크를 지우려면 유료 플랜이 필요해요. 이 글은 브루 공식 가격 페이지와 고객센터 공지를 2026년 10월 23일에 다시 확인해, 크레딧 계산법과 플랜 고르는 기준을 정리했어요. 목차 브루 요금 구조: 통합 크레딧이란 1크레딧으로 할 수 있는 일 무료 플랜으로 되는 것과 안 되는 것 유료 플랜 4종 비교표 월 구독·연 구독·기간 이용권, 무엇이 이득일까 상황별 추천: 학생·직장인·유튜버 크레딧이 모자랄 때: 사용 기록 지우개 업그레이드·환불 전에 알아둘 규칙 운영자 메모, 자주 묻는 질문 1. 브루 요금 구조: 통합 크레딧이란 예전 브루는 플랜마다 음성 분석 몇 분, AI 목소리 몇 자, 번역 몇 자처럼 기능별 한도를 따로 줬어요. 그런데 보이저엑스(브루 운영사)가 실제 이용 데이터를 보니 한두 가지 기능만 집중해서 쓰는 사람이 훨씬 많았다고 해요. 그래서 2026년 4월 22일 업데이트부터는 플랜마다 정해진 크레딧을 받고, 어떤 기능에 쓸지는 내가 정하는 방식으로 바뀌었어요. 플랜별 매달 지급량은 Free 200 · Light 2,000 · Standard 10,000 · Business 12,000크레딧 이에요. 공식 공지에 따르면 무료 사용자는 매달 1일에, 유료 사용자는 매월 결제일에 충전되고, 남은 크레딧은 다음 달로 넘어가지 않아요. 바뀐 뒤 무엇이 좋아졌나 공지에 나온 예시가 이해하기 쉬워요. Standard 플랜에서 AI 목소리만 쓰면 예전에는 최대 50만 자였지만, 지금은 1만 크레딧을 모두 AI 목소리에 몰아 쓸 수 있어 최대 100만 자가 돼요. 반대로 여러 기능을 골고루 쓰는 사람은 크레딧이 기능끼리 ...

에이닷 전화 vs 익시오: 통화 녹음·AI 요약, 내 통신사·폰에 맞는 앱 고르기

요약: 통화 녹음과 AI 요약을 쓰고 싶다면 먼저 내 통신사와 휴대폰 종류부터 확인해야 해요. LG유플러스 고객은 무료 앱 익시오, SKT 고객은 에이닷 전화가 가장 기능이 많고, 다른 통신사의 아이폰 사용자는 iOS에 들어 있는 기본 통화 녹음·전사 기능이 현실적인 선택이에요. 이 글은 2026-10-30에 SKT·LG유플러스·Apple 공식 페이지와 도움말을 직접 확인해 세 가지를 비교했어요. 왜 '앱 기능'보다 '내 조건'을 먼저 봐야 할까요 통화 요약 앱 비교 글을 보면 기능 목록부터 나열하는 경우가 많아요. 그런데 실제로 써 보려는 사람에게 가장 먼저 걸리는 건 기능이 아니라 이용 조건 이에요. 익시오는 LG유플러스 고객 전용이고, 에이닷 전화는 누구나 설치할 수 있지만 통역콜·baro 같은 기능은 SKT 고객에게만 열려 있어요. 아이폰은 운영체제 구조상 앱이 통화를 마음대로 녹음하기 어려워서, 통신사 앱이 안 되면 iOS 기본 기능에 기대야 해요. 그래서 이 글은 "어떤 앱이 제일 좋은가"보다 "내 통신사·내 폰에서 무엇을 쓸 수 있나" 순서로 정리했어요. 기능 차이는 그다음이에요. 한눈에 비교: 에이닷 전화 vs 익시오 vs 아이폰 기본 통화 녹음 구분 에이닷 전화 (SKT) 익시오 ixi-O (LG유플러스) 아이폰 기본 통화 녹음 (Apple) 누가 쓸 수 있나 통신사 구분 없이 앱 설치 가능. 단, 통역콜·baro·그룹통화 발신 등은 SKT 고객 전용 U+ 모바일 고객. 타 통신사, 만 14세 미만, 선불요금제 고객은 제한 (공식 사이트 FAQ상 알뜰폰 중 KB리브엠은 예외) 지원 국가·언어의 iPhone 사용자. 1명과 통화할 때만 녹음 가능 지원 OS·기기 Android 10 이상, iOS 16 이상 iOS 17 이상 iPhone 12 이상 / Android...

타입캐스트 vs 클로바더빙: 수익 나는 채널에 쓸 때 무료·유료 조건 비교

요약 타입캐스트와 클로바더빙은 둘 다 글만 입력하면 한국어 AI 목소리를 만들어 주는 서비스지만, 무료로 쓸 수 있는 범위가 꽤 다릅니다. 클로바더빙 무료는 매달 15,000자까지 쓸 수 있는 대신 수익이 생기는 채널에는 쓸 수 없고, 타입캐스트 무료는 처음에 주는 약 5분 분량의 다운로드로 끝나는 체험판에 가깝습니다. 광고 수익이 붙은 유튜브나 쇼핑몰 영상에 넣을 목소리라면 처음부터 유료 플랜 조건을 보고 고르는 편이 안전합니다. 왜 이 두 서비스를 같이 비교하나 쇼츠 내레이션, 수업 자료 더빙, 상품 소개 영상처럼 "내 목소리 대신 AI 목소리"가 필요할 때 한국 사용자들이 가장 많이 찾는 곳이 네오사피엔스의 타입캐스트 와 네이버의 클로바더빙 입니다. 기능 소개만 보면 비슷해 보이지만, 실제로 문제가 되는 건 음질보다 "이 목소리를 내 채널에 써도 되나" 입니다. 그래서 이 글은 기능 나열보다 무료 사용 범위, 출처 표기 의무, 유료 플랜 가격과 다운로드 한도를 중심으로 정리했습니다. 모든 수치는 2026년 10월 25일에 두 서비스의 공식 요금 페이지와 고객센터 도움말에서 직접 다시 확인한 내용입니다. 한눈에 보는 비교표 항목 타입캐스트 무료 타입캐스트 베이직 클로바더빙 Free 클로바더빙 Standard 월 요금 0원 9,900원 (연간 결제 시 10% 할인) 0원 19,900원 (네이버 클라우드 플랫폼에서 결제) 무료·포함 사용량 음성 생성·재생 무제한, 다운로드는 최초 3,000크레딧(약 5분) 1회 지급 월 30,000크레딧(약 60분) 월 15,000자, 다운로드 월 20회, 프로젝트 누적 5개 (매월 1일 갱신) 월 30,000자, 다운로드 월 40회, 프로젝트 누적 20개 쓸 수 있...