I got tired of pasting work questions into a browser tab and wondering who else had a copy. So last year I stood up my own private ChatGPT at home. It took one evening, and I haven't logged back into the browser one since. Here's the honest version of how it works, and where you'll actually hit friction.
Quick before I forget: by 'private ChatGPT' I mean a chat interface that runs on hardware I control, talking to a model that also runs on hardware I control. No API calls out, no prompt logging on someone else's server, no account tied to my email.
What a self-hosted ChatGPT actually is
It's two pieces. The engine is the model, and the face is a web UI. For the face I use Open WebUI, because it looks and behaves like the thing everyone grew up clicking. Threads, markdown, regenerating answers, a model picker in the corner. Nobody in my house needed a tutorial.
Underneath sits a local model. The bundle I run uses LM Studio to manage and serve quantized models, which sounds fancy until you realize a quantized model is just the same model with the weights rounded off so it fits in your VRAM. Q4 is the usual sweet spot. You lose a little edge case reasoning and keep most of the useful answers.
The one-command start
Open WebUI and a local model engine run fine as a Docker pair. If you already have anything running on port 11434, that's likely Ollama or LM Studio's server — let the container talk to the host instead of fighting over the port:
docker run -d -p 3000:8080 \n --add-host=host.docker.internal:host-gateway \n -v open-webui:/app/backend/data \n --name open-webui --restart always \n ghcr.io/open-webui/open-webui:main
Open http://localhost:3000, claim the first account (it becomes admin), point it at your local model, done. That's the whole setup. Most of the evening is spent pulling models and deciding which quant to bother with.
Where it's actually better
The privacy is the point. My team's questions, my half-finished notes, the slightly embarrassing drafting — none of it leaves the desk. When the internet dropped during a storm last month, my chat kept working. A local model can't be rate-limited, and it won't change its behavior because thousands of other people hammered the same endpoint.
Where it's honestly worse
A 7B or 8B model is not a frontier flagship. It'll write competent drafts, summarize, explain code, and do the 90% of work I actually ask it for. It will occasionally be confidently wrong in ways a bigger cloud model wouldn't. I keep the cloud account around for the rare genuinely hard question.
I put all the defaults I learned into one place so you don't relive the wrong-quant-and-restart hour: my Self-Hosted AI Home Lab bundle covers the Docker stack, Open WebUI, and the quantized model picks that actually fit a home GPU: https://symshah.gumroad.com/l/selfhosted-ai-homelab
It's pay-what-you-want from nine bucks. If you'd rather just tinker with the two commands above, honestly, that works too.
FAQ
Is a private ChatGPT as smart as ChatGPT?
No. A home GPU runs a small quantized model that's good at drafting, summarizing and coding help, not a frontier model. For my daily work it's close enough that I stopped going back.
Do I need an expensive graphics card?
An 8GB card runs a solid 7B quantized model. 12GB opens up the 13B class. The better VRAM headroom buys larger models, not necessarily faster ones.
Does Open WebUI cost anything?
No. It's open source, and it talks to any local model engine — LM Studio, Ollama, or anything OpenAI-compatible. Your hardware and electricity are the only thing you pay for.
Top comments (0)