One chat interface over local models for a household or a team
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Two or more users log in, chat with the same local model concurrently, and an administrator can see per-user access; the model answers with the attached knowledge where asked.
Measured, for our own tests: a network monitor sees no prompt text leave the machine. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: set up a private ChatGPT for my family
, give staff a chat over our internal documents on our own server
, a chat UI for the model running on my home server
, deploy private LLM chat for a few hundred users
Does the job, with a limit 3
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| AnythingLLM E Mintplex Labs, Inc. | Docker build has multi-user mode, invites, admin and rule-based access to workspaces. API keys are admin-equivalent with no scopes. One account rejected it for the install size and setup. source |
| LocalAI B Ettore Di Giacinto and the LocalAI team | The README's 4.1.0 notes announce a multi-user platform with OIDC, API keys and per-user quotas, and saved chats with agents. The multi-user docs page was not read, so accounts and groups rest on release notes. source |
| Open WebUI D Open WebUI Inc. | Roles, groups, permissions and per-user API keys (admin must enable them, no expiry). Deployments for 700 to 800 users exist. Accounts report persona prompts drifting after a few turns and configuration effort. source |
Couldn't check 2
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Core F ZMJ, Inc., doing business as Ghost, 325 9th Street, San Francisco, CA 94103, United States | The FAQ says desktop and phone clients connect; no accounts, per-user access or concurrency is documented. |
| Khoj E Khoj Inc. | Setup docs cover anonymous mode and per-user kk- API keys, but the authentication and multi-user page was not read, so per-user access could not be confirmed. |
Doesn't do this job 19
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Berth B Trevin Tindall (T-Crypt on GitHub) | One bearer key; no accounts. source |
| BitRun E Abhishek Khanra (IshekKhal on GitHub) | No key or accounts; one process serves one model. source |
| Docker Model Runner C Docker, Inc. | No credential or accounts; any client that reaches the socket can pull and run models. source |
| Foundry Local B Microsoft Corporation | The FAQ says it is single-user inference for one device and not a server stack; no concurrency or accounts. source |
| GPT4All F Nomic, Inc. | Localhost-only server with no authentication or accounts. source |
| HyperQwen C syv.ai (Copenhagen, CVR DK44671247) | VLLM_API_KEY only; no accounts. source |
| Jan C Menlo Research Pte Ltd | Desktop app for one user; the server has an optional single API key and no accounts. source |
| KoboldCpp B LostRuins (Concedo) | --multiuser queues several clients and --password is one shared key for text routes; no accounts or per-user view. source |
| Lemonade B Advanced Micro Devices, Inc. | One optional LEMONADE_API_KEY and an admin key; no accounts or groups. source |
| llama.cpp D ggml.ai, part of Hugging Face since 2026 | Parallel slots and --api-key exist, but no accounts, groups or per-user view. The home-server account puts Open WebUI in front for the family. source |
| LM Studio C Element Labs, Inc. | One bearer token with Require Authentication; no accounts or groups. A desktop app and headless daemon for one owner. source |
| LocalGhost F LocalGhost.ai Ltd (company number 17213100, registered in England and Wales, incorporated 12 May 2026) | One box, one phone, no browser client or accounts. source |
| MLX LM C Apple Inc. | No API key option and --allowed-origins defaults to *; no accounts. source |
| Ollama D Ollama Inc. | No accounts, groups or credentials; the FAQ says to put an authenticating proxy in front. Ollama is the backend that Open WebUI deployments sit on, not the chat interface. source |
| PrivateGPT C PriBAI Technology Spain S.L. | One shared static secret when auth is on; no per-user accounts. source |
| screenpipe C Negentropy Labs, Inc. (dba Screenpipe) | Per-person recorder; Teams shares task configs, not a chat interface. source |
| TextGen E oobabooga | One --api-key at launch; no accounts or groups. source |
| Underdog F Conway Research | A personal assistant for one Mac over the owner's mail and calendar. source |
| vLLM D The Linux Foundation (vLLM is a PyTorch Foundation project) | --api-key only; no accounts or groups. source |
What stops agents finishing
- API keys off by default and only an administrator can switch them on
- the model drops the system prompt after a few turns, so a persona or rule set does not hold
- a 500 MB desktop install or Docker stack is more than the person will set up
Around it
Before: local-ai.fit-model-to-hardware. After: local-ai.chat-with-own-files, search.search-with-text.
Where this comes from
Weight 13 of 100 in Local AI: 9 of 50 accounts, all Open WebUI or llama.cpp plus Open WebUI; two were deployments for hundreds of users
The same as data: /api/v1/use-cases/local-ai.household-or-team-chat.json, or the MCP tool get_use_case with id local-ai.household-or-team-chat. Other jobs in this category: /api/v1/niches?category=local-ai.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.