Independent testing Updated April 2026 387 self-hosting guides 5 VPS providers tested

comparison

Best VPS for Open WebUI (2026): Light App, Heavy Backend

Find the best VPS for Open WebUI in 2026. We compare providers on speed, storage, and price to help you self-host Open WebUI smoothly and affordably today.

Best VPS for Open WebUI (2026): Light App, Heavy Backend

Open WebUI keeps growing in popularity as the ChatGPT-replacement UI for self-hosted LLMs. The hosting confusion comes from people conflating Open WebUIโ€™s needs with the inference backendโ€™s needs. Open WebUI is light, the model is what eats the resources.

Here is the realistic VPS shortlist after running Open WebUI in production for six months across personal and team deployments.

The Honest Resource Picture

Open WebUI is two pieces: a SvelteKit frontend that compiles to static assets and a Python (FastAPI) backend that handles user management, chat history, and the proxy to your inference endpoint. Total resident memory at idle: 250 to 400 MB.

For a 10-user team with active chat usage, expect 500 MB to 1 GB resident memory plus the database (SQLite for hobby, Postgres for production). The app scales to many users without significant additional resources because the heavy lifting happens on the inference backend.

The disk story is mostly about chat history. Active users accumulate 10 to 50 MB per month of chat logs. Plan for the volume to be predictable and small unless you have heavy ingestion of long documents.

VPS Comparison for Open WebUI

ProviderPlanvCPURAMDiskMonthlyBest fit
Hetzner CPX11CPX1122 GB40 GB SSD5.18 EURSolo or small team, external model
Hetzner CPX21CPX2134 GB80 GB SSD5.83 EUR10 to 30 user team
Contabo VPS SVPS S48 GB100 GB NVMe4.50 EURBudget team setup
Hetzner CCX23CCX23416 GB160 GB NVMe29.74 EUROpen WebUI + Ollama co-hosted

Hetzner CPX11: For solo and small team use

At 5.18 EUR a month, the CPX11 is enough for Open WebUI when your inference happens elsewhere (external API, separate GPU machine, hosted model). 2 GB RAM holds the app, the SQLite database, and a small user count comfortably.

This is the right pick for personal use or small teams (under 5 users) that point Open WebUI at OpenAI, Anthropic, or a separately hosted Ollama instance.

Pros:

Get Hetzner: Hetzner Cloud.

Hetzner CPX21: For active team use

For teams of 10 to 30 users, the CPX21 with 4 GB RAM gives headroom for the chat history database and concurrent web connections. Still cheap at 5.83 EUR a month.

Pick this when Open WebUI is the daily AI tool for a small team and inference happens on a separate machine.

Contabo VPS S: Best value for team setups with co-located Postgres

4.50 EUR for 4 vCPU and 8 GB RAM is hard to beat when you want Open WebUI plus a co-located Postgres for production user management. The shared CPU is fine because Open WebUI is mostly I/O bound on the inference backend, not CPU-bound on its own.

Pros:

Real negative: provisioning takes hours, network egress can be slow at peak times.

Get Contabo: Contabo VPS.

Hetzner CCX23: For Open WebUI + Ollama on one machine

When you want everything on one machine (Open WebUI plus Ollama plus models), the CCX23 with 16 GB RAM hits the sweet spot. A 7B model takes 8 GB, Open WebUI plus Postgres takes 1 to 2 GB, leaving headroom.

For team setups where everything needs to live on one machine for simplicity or for privacy. The downside is that you cannot scale the inference and the UI independently.

What I Would Pick

For solo personal use with external model: Hetzner CPX11. For team use with separately hosted Ollama: Hetzner CPX21 or Contabo VPS S. For everything on one machine: Hetzner CCX23. The right split depends entirely on your inference strategy, Open WebUI itself is almost free to host.

Full VPS context lives at the SelfHostVPS comparison. Open WebUI pairs naturally with Ollama, see that guide for the inference-side recommendations.

Frequently asked questions

What VPS specs does Open WebUI need on its own?

Open WebUI itself is a SvelteKit frontend plus a Python backend that idles at around 250 to 400 MB resident memory. With SQLite for chat history and a small Postgres for user management, you fit easily in 2 GB RAM. The 2 vCPU, 2 GB RAM tier on Hetzner CPX11 at 5.18 EUR a month handles 10 to 20 concurrent users without complaint.

Do I need GPU on the same VPS as Open WebUI?

No, the GPU need is on the inference backend (Ollama, vLLM, OpenAI-compatible endpoint). Open WebUI just talks to that backend over HTTP. Most production deployments run Open WebUI on a small CPU VPS and point it at a separate GPU machine, an external API, or a hosted inference provider. This separation simplifies scaling and reduces cost.

Can Open WebUI serve as a multi-user ChatGPT replacement for my team?

Yes, this is its primary use case. The user management, role-based access, and chat history features are production-ready. For 5 to 20 users with a shared Ollama backend, a 4 GB RAM VPS handles the Open WebUI tier comfortably. The bottleneck moves to your inference backend long before it hits the web UI.

Should I run Open WebUI and Ollama on the same VPS?

For personal use yes, for team use no. Co-hosting works fine when one person uses it occasionally, the latency between Open WebUI and Ollama is negligible. For team deployments, separating them lets you scale the inference backend independently and avoid the UI becoming unresponsive when the model is processing a long generation.