Ran Open WebUI on a 2 GB box for a while. Chat was fine, PDFs were not.

Been running Open WebUI on a little 2 GB / 1 vCPU VPS, API models only, no local LLM. Sharing because the RAM story wasn’t what I expected. Just chatting? Totally fine. It mostly sits there forwarding requests and streaming replies back. The thing that bit me was document upload. The default image does embeddings locally (a small MiniLM model), so the moment someone drops a stack of PDFs into a knowledge base the CPU pins and memory climbs. On 2 GB that was where I started seeing the container get OOM-killed. What helped: - pointing embeddings at an API instead of computing them locally - just going to 4 GB once uploads became a daily thing - setting WEBUI_SECRET_KEY to a fixed value. before that, every redeploy logged everybody out and I thought I’d broken something Still on SQLite. Has anyone squeezed Postgres onto the same tiny box, or is that asking for trouble?