Which Open WebUI alternative fit VPS best?
Compare Open WebUI, LibreChat, Hollama and OrionChat for VPS: see RAM wey model go get, login support, remote Ollama fit, and upkeep wahala.
Which Open WebUI alternative dey belong for VPS
People almost always dey compare Open WebUI alternatives for laptop, where RAM cheap and nothing dey listen on public address. VPS dey change both facts, and that one dey change the ranking. Open WebUI remain the correct default once another person login, because e ship with real user accounts and admin panel. The lighter projects dey win when the interface dey compete with model for the last gigabyte of RAM. The price of this win na authentication: dem no get any.
Everything below come from each project's own documentation, wey dem read for August 2026, check again on 20 October 2026, and check again for Open WebUI, LibreChat, Hollama and OrionChat on 25 October 2026. Dem check Ollama documentation and browser security rules again on 29 October 2026. The four axes na the ones wey only show once the box fit reach from internet.
Four axes wey only matter for public IP
- Memory near the model. The model server na the process wey dey cost pass for the machine. Every megabyte wey the interface hold na one megabyte wey the model no fit use.
- Authentication. Some of these projects get user accounts and roles. Others assume say dem na the only thing wey dey run for your laptop, and dem no get login at all.
- Remote inference. UI wey you only ever point to
127.0.0.1:11434dey expect the model to dey for the same machine as the interface. If you put the model for another place, you need tunnel wey go forward that local port to the model host. - Upkeep. One container with a SQLite file na different work from six containers with MongoDB and a vector database behind dem.
How much RAM the model dey leave for the interface
The interface no be the biggest thing for the box. Na the model. The download sizes wey dem publish na just the base, because the weights must dey resident while the model dey answer, and the real memory wey e dey use go pass the download size once the context cache don allocate.
Di data wey dey behind dis chart
[
{
"label": "llama3.2:3b",
"download_gb": "2.0"
},
{
"label": "qwen3:4b",
"download_gb": "2.5"
},
{
"label": "gemma3:4b",
"download_gb": "3.4"
},
{
"label": "qwen3:8b",
"download_gb": "5.2"
}
]Demna the figures wey the Ollama library pages print for 25 October 2026. Na published sizes, no be measurements. For one 4 GB VPS, qwen3:4b wey be 2.5 GB go leave under 1.5 GB for the operating system and every other thing, and the context cache go chop part of that one as the conversation dey grow, na why the num_ctx wey you set na memory decision as e be quality decision. qwen3:8b wey be 5.2 GB no fit fit for that box at all. This na the situation wey laptop roundups no dey ever cover, and na here the chat interface wey dey hold few hundred megabytes go decide whether the model go run. If you dey size box for something wey pass these tags, the arithmetic for one 27B model on top CPU-only VPS go show you how quick the interface go stop to be the number wey dey decide anything.
Make you measure, no just trust any number for roundup, including this one. Run docker stats --no-stream one hour after you don start real use, no be one minute after the container start, because the memory wey matter na the one wey dem allocate for first use. Ollama self dey release the weights after five minutes of idle time, so any reading wey you take between conversations go show small pass the peak, and the next message go pay the whole load again unless you keep the model resident with keep_alive.
Open WebUI: e still be the default for more than one user
Open WebUI dey run from one image and e dey keep im data for one volume.
docker run -d -p 127.0.0.1:3000:8080 -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:mainThe command for the project README dey publish -p 3000:8080, and e dey listen on every interface. The 127.0.0.1: prefix keep am for loopback. Docker dey warn say for releases wey old pass 28.0.0, hosts for the same L2 segment fit reach ports wey publish to localhost. So use Docker Engine 28.0.0 or later before you rely on that binding for isolation. For VPS, that prefix matter pass every other thing for the line, because Docker dey write im own iptables rules and published port dey ignore your ufw deny rules.
Reach the page through tunnel or proxy, as dem describe below, then create the first account. That account go become administrator. Sign-up go then switch itself off until admin turn New Sign Ups back on. Later signups go get role pending, wey be the documented default of DEFAULT_USER_ROLE. So stranger wey reach the page still no fit use your model until admin approve am.
Open WebUI dey use more memory than the projects below because e dey do more work, and im own performance page name the parts wey dey cost memory. The default embedding engine dey load sentence-transformers model inside the container. Setting RAG_EMBEDDING_ENGINE=ollama go make the model server wey you already dey run handle that work. AUDIO_STT_ENGINE=web stop am from loading local speech-to-text model. For SQLite when DATABASE_POOL_SIZE no set, the pool go fall back to large internal size, and each connection go grow im own page cache and memory map. So for small box, set DATABASE_POOL_SIZE=8 and DATABASE_SQLITE_PRAGMA_MMAP_SIZE=0. Autocomplete dey ask the model for completion while user still dey type. E now ships switched off (ENABLE_AUTOCOMPLETE_GENERATION dey default to False), so leave am that way for small box.
LibreChat: for plenty users, with stack behind am
git clone https://github.com/danny-avila/LibreChat.git
cd LibreChat
cp .env.example .env
docker compose up -dThe interface dey answer for port 3080. LibreChat na the one to check when you need identity system instead of ordinary login box: e document LDAP and OAuth2 logins, and e default compose file also define admin panel for users, groups and roles. The panel no dey run out of the box. E refuse to start until ADMIN_PANEL_SESSION_SECRET dey set for .env, and this value must get at least 32 characters with no default. So generate one with openssl rand -hex 32 if you want am. The panel dey run as im own service, no be inside LibreChat process, and e need LibreChat v0.8.5 or later. This capability dey come with stack.
Di data wey dey behind dis chart
[
{
"label": "OrionChat",
"containers": 0,
"notes": "static files, served by a web server you already run"
},
{
"label": "Hollama",
"containers": 1,
"notes": "one container serving a browser app"
},
{
"label": "Open WebUI",
"containers": 1,
"notes": "application and SQLite in one image"
},
{
"label": "LibreChat",
"containers": 5,
"notes": "api, MongoDB, Meilisearch, pgvector, RAG API"
}
]The default compose file dey start 5 services: api, MongoDB, Meilisearch, pgvector, RAG API. Sixth one, the admin panel, dey inside the same file and e join dem once you set im secret. None of dem na the model. MongoDB and pgvector each need memory for themselves, and for 4 GB box, na memory the model want.
Two services for the file publish ports, and none of the mappings specify bind address: the API for 3080 and the admin panel for host port 3000, wey be the default of ADMIN_PANEL_PORT. So both go listen on every interface once dem run. Open WebUI above dey also use port 3000, so both go clash for shared box as soon as you enable the panel. Rebind both to 127.0.0.1 for docker-compose.override.yml before the stack face internet.
Upgrades na git operation, and na this part people dey usually get wrong.
docker compose down
git pull
docker compose pull
docker compose up -dgit pull go stop with conflict if you edit the tracked docker-compose.yml, and then the upgrade go only apply halfway. Put your changes for docker-compose.override.yml, wey the project provide for this purpose, and keep secrets for .env. Both files no dey tracked, so git pull go leave dem alone.
Point LibreChat to your own model server with custom endpoint for librechat.yaml.
endpoints:
custom:
- name: "Ollama"
apiKey: "ollama"
baseURL: "http://model-host:11434/v1/"
models:
default: ["llama3.2"]
fetch: true
titleConvo: true
titleModel: "current_model"
modelDisplayLabel: "Ollama"Replace model-host with the address of the box wey dey run Ollama. The apiKey field must dey present even though Ollama no dey use im value, so placeholder dey okay. If LibreChat dey run for Docker and Ollama dey run for the same machine, localhost inside the container mean the container itself, so use host.docker.internal there instead.
Hollama and OrionChat: browser dey do the work
Hollama dey serve one browser application from one small container. Chats dey live for your browser storage, no be for server.
docker run -d --restart unless-stopped -p 127.0.0.1:4173:4173 --name hollama ghcr.io/fmaclen/hollama:latestThe self-hosting guide version of this command dey use --rm. E dey delete the container when e stop, so the interface no go come back after reboot.
OrionChat go further, because e no get any server component at all. Clone the repository and serve the folder with the web server wey you already dey run, or open index.html from disk. API keys dey stored for browser localStorage, chat history dey remain for browser, and the app dey delete the oldest chats once the count pass 512. OrionChat Ollama address fixed for the source code (js/script.js) at http://localhost:11434, and the settings no get field wey you fit use change am.
Neither project get login. For laptop, this one no be problem. For VPS, e mean say you must never publish the page on 0.0.0.0. E also mean one thing wey easy to miss: na browser dey call the model, no be server.
Na this fact dey decide where you fit use the two projects. Your browser must reach Ollama directly. For OrionChat, this one always mean localhost:11434 for the machine wey dey run the browser. So for VPS, the SSH tunnel below na the only route to the model. Hollama dey accept any address wey you enter as the connection base URL, and its self-hosting guide cover Ollama server wey dey on another device: add Hollama origin to OLLAMA_ORIGINS for the Ollama side. So unless you forward the port through SSH, Ollama must listen beyond loopback, and Ollama API no dey ask for login or key. Two browser rules follow from this. Page wey HTTPS serve no fit call plain HTTP endpoint for public IP address, and console go print Mixed Content: The page at 'https://chat.example.com/' was loaded over HTTPS, but requested an insecure resource 'http://203.0.113.10:11434/api/tags'. This request has been blocked.. Loopback get separate exemption: Mixed Content spec only blocks URLs wey no be potentially trustworthy, and Secure Contexts spec count localhost, 127.0.0.0/8 and ::1 as potentially trustworthy. So the same HTTPS page fit call http://localhost:11434 or http://127.0.0.1:11434. Na this exemption SSH tunnel below dey rely on. Since version 142, Chrome dey add one step when the page come from public site like https://chat.example.com: request from there go loopback or local network address go wait until user allow local network access for permission prompt. Chrome also exempt permission-gated HTTP requests to local-network endpoints from mixed-content checks when hostname na private IP literal like 192.168.0.1, a .local name, or the fetch specify targetAddressSpace: "local". Page wey you open at http://localhost through the tunnel don already dey on loopback, so that prompt no apply to am. Call to any other origin go refuse with has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource until you allow that origin.
Ollama documented way to change either setting na systemd override.
sudo systemctl edit ollama.service[Service]
Environment="OLLAMA_HOST=0.0.0.0:11434"
Environment="OLLAMA_ORIGINS=https://chat.example.com"sudo systemctl daemon-reload
sudo systemctl restart ollama
sudo ss -lntp | grep 11434ss suppose now print 0.0.0.0:11434 where e print 127.0.0.1:11434 before. Only make this change when firewall or authenticating proxy already dey control who fit reach the port, because open 11434 na open model server, and mass scanners dey reach new public port quickly. The SSH tunnel below avoid the whole matter: page go then run on a localhost origin, wey Ollama permit by default, and the port no go leave the machine.
Each one fit use remote Ollama or vLLM endpoint?
Open WebUI fit do am, and na for server side the connection dey happen. OLLAMA_BASE_URL=http://model-host:11434 point am go Ollama. For vLLM, set OPENAI_API_BASE_URL=http://model-host:8000/v1, make you keep the /v1 wey vLLM dey use serve im API. Set OPENAI_API_KEY only if you start the server with key, sake of say Open WebUI vLLM guide no dey use auth by default. Other OpenAI-compatible servers go take any base path wey dia own docs give, wey no be /v1 all the time. OPENAI_API_BASE_URLS fit accept plenti backends if you separate dem with semicolon.
LibreChat fit do am, through the baseURL of the custom endpoint wey we show up so. That request sef dey leave the server, so no browser rule dey apply. The same base URL and the same placeholder key dey work outside chat window too, and na only that one you need to point coding agent go the model wey you don host.
Hollama fit point go any endpoint wey you type inside im settings. Im Ollama connection get base URL wey you fit edit, wey be http://localhost:11434 by default, and apart from that, Hollama get OpenAI-compatible connection, http://localhost:8080/v1 by default, wey be the way to reach vLLM. The request dey leave your browser, so everything wey we talk for the section up there dey apply to am. OrionChat no fit point go anywhere. Im endpoints dey hardcoded, Ollama dey fixed for http://localhost:11434/v1/chat/completions, and im README talk say requests dey go direct to each provider official API. Remote Ollama fit only reach through SSH tunnel wey go make am answer for that local port, and no setting dey for vLLM server at all.
To separate the interface from the model na the most useful thing wey remote endpoint fit give you. Put the interface for small box and the model for where memory dey. That one na also the time to decide whether Ollama or vLLM suppose serve the requests, because the two dey behave differently once plenti people start talk to the model at the same time. If the model server no exist yet, start by running Ollama for VPS, and for CPU-only box, read how Ollama compare with llama.cpp before you pick runner.
Never publish chat UI wey no get login on 0.0.0.0
Open WebUI hardening page talk say the project dey “built for private, trusted networks, similar to other self-hosted infrastructure like databases, container registries, and CI servers”, and e tell you make you put am behind VPN or reverse proxy with authentication. Project wey no get login at all deserve at least the same treatment.
Check wetin dey listen before you trust anything.
sudo ss -lntp | grep -E ':(3000|3080|4173|11434)'Line wey read 127.0.0.1:3000 na wetin you want. Line wey read 0.0.0.0:3000 mean say the service dey listen on all addresses, and Docker dey allow every external source IP reach published port by default. Unless rule for Docker's DOCKER-USER chain or your provider's firewall block am, your chat interface dey public internet. From your own machine, curl -sI http://YOUR.VPS.IP:3000 wey answer HTTP/1.1 200 OK go settle the matter more directly.
To turn off Open WebUI login with WEBUI_AUTH=False na single-user setting for machine wey nobody else fit reach. The documentation still talk say e only work for installation wey no get registered users, so you no fit apply am to installation wey already get accounts.
Pattern one: bind to loopback and reach am through SSH. Publish every port on 127.0.0.1, then forward the one wey you need: ssh -N -L 3000:127.0.0.1:3000 you@vps.example.com, and open http://localhost:3000 for your laptop. Use Docker Engine 28.0.0 or later for this pattern; older releases allow hosts for the same L2 segment reach ports wey publish to localhost. For OrionChat, forward the model port for the same command with -L 11434:127.0.0.1:11434 and leave Ollama on loopback. Hollama fit reach Ollama directly, but this same forward keep Ollama away from public internet, so na the safer route for Hollama too. This pattern only strong as your SSH setup, so pair am with key-only SSH and hardened sshd.
Pattern two: reverse proxy wey authenticate before app see the request. Keep app on loopback, make proxy own port 443, and put single sign-on in front. Traefik driven by Docker Compose labels with Authentik as identity provider give every app for the machine one login and one certificate. With Open WebUI behind TLS (transport layer security), set WEBUI_SESSION_COOKIE_SECURE=true and WEBUI_SESSION_COOKIE_SAME_SITE=strict. Shorten JWT_EXPIRES_IN from the default four weeks too, because Open WebUI documentation talk say without Redis, sign-out no invalidate the token: e remain usable until e expire by itself.
Pattern two no fit rescue projects wey browser-only. Proxy wey dey in front of the page no protect the model endpoint, and fetch from that page to different hostname no carry your session cookie, so authenticating proxy wey dey in front of Ollama answer with redirect to login form and chat fail. Either route the model endpoint under the same hostname as the page, or use pattern one.
Which one to pick
If any other person apart from you go use am, run Open WebUI. E get real accounts, new users go land for approval queue, and di maintainers dey publish hardening guidance wey you fit follow. If you need LDAP or admin panel, run LibreChat, set ADMIN_PANEL_SESSION_SECRET if you want di panel, and confirm wit docker stats say di five services, six wit di panel, plus your model actually fit before you depend on am. If na only one person for small box where di model don already take most of di RAM, serve Hollama or OrionChat over SSH tunnel and make di browser hold di state. Di wrong answer for VPS na any of dem wey you publish for 0.0.0.0 wit no login for front.
FAQ
Open WebUI safe to expose directly for public IP?
Its hardening page describe am as software for private, trusted networks, for the same category as database or CI server. E get real accounts, and the first account become administrator while later ones remain pending until approval, so e far safer pass UI wey no get login. Still put am behind reverse proxy with TLS and, where you fit, single sign-on. Publish the container port as 127.0.0.1:3000:8080 and use Docker Engine 28.0.0 or later before you rely on loopback publishing for isolation. Docker warn say for older releases, hosts for the same L2 segment fit reach ports wey publish to localhost.
Which Open WebUI alternative use the least RAM for VPS?
The browser-based ones, Hollama and OrionChat, because the application dey run for the client. The server only dey send static files, and OrionChat no need application container at all. Open WebUI keep Python process, database and, by default, local embedding model for memory. Confirm the numbers for your own box with docker stats --no-stream, because dem dey change based on the features wey you turn on.
These chat UIs fit use Ollama server for another host?
Open WebUI and LibreChat fit, and their server dey make the connection, so browser rule no apply. Set OLLAMA_BASE_URL for Open WebUI, or baseURL for custom endpoint for LibreChat. For vLLM or another OpenAI-compatible server, use OPENAI_API_BASE_URL with the base path wey that server document, which na /v1 for vLLM, and add API key only if the server require am. Hollama fit also point anywhere, but na your browser dey make the request, so the endpoint must dey reachable from your browser too. OrionChat no fit: e get Ollama address hardcoded to http://localhost:11434, so remote Ollama go work only through SSH tunnel wey forward that port.
Why my browser chat UI no fit reach Ollama?
Two causes cover nearly every case. Ollama bind to 127.0.0.1:11434 by default, so browser for another machine no fit reach am directly until OLLAMA_HOST change or SSH tunnel forward the port. And Ollama accept cross-origin requests from localhost, 127.0.0.1 and 0.0.0.0 by default, so e go refuse page wey your own domain serve with No 'Access-Control-Allow-Origin' header is present on the requested resource until you list that origin for OLLAMA_ORIGINS. If the page na HTTPS and the endpoint na plain HTTP for public IP address, browser go block the call as mixed content before Ollama ever see am. Loopback addresses (localhost, any address for 127.0.0.0/8 such as 127.0.0.2, or [::1]) dey exempt. Chrome also exempt local-network HTTP requests wey use private IP literals such as 192.168.0.1, .local hostnames, or targetAddressSpace: "local" after local-network permission don grant; Ollama CORS requirements still apply. Set both variables for systemctl edit ollama.service override, or forward the port over SSH and the problem go disappear.