Pinned Tweet
One interface. Every model. That's the idea behind Open WebUI + OpenRouter.
Instead of juggling multiple vendors, API keys, and UIs, organizations can now get a single platform with 600+ models ready to go out of the box.
Interface and inference, together.
5
4
58
160,602
More local compute. Put it to work.
We’re an early access partner for @NVIDIARTXSpark.
Build agents in Open WebUI that work with your files, run code, and return results on infrastructure you control.
Get started: openwebui.com/blog/open-webu…
3
18
1,325
Open WebUI retweeted
OpenWebUI × SearXNGで無料のDeepResearch。
同時に2~4クエリ同時検索して、それを繰り返すから、実質DeepResearch。
1
2
337
Open WebUI retweeted
社内だけで使える「自社専用のChatGPT」、作れるって知っていますか？💬
✅ Open WebUIでできること
✅ 業務で役立つ4つの機能
✅ 導入のおおまかな流れ
✅ つまずいたときの確認ポイント
▶ 続きはブログで
harmonic-society.co.jp/open-…
#OpenWebUI #ローカルLLM
1
2
279
やばすぎｗｗｗ
自分のサーバーで使うAIチャット基盤「Open WebUI」がv0.12.3を公開。チームの会話を探して、資料の気になる一文をAIに渡す流れがかなり便利に。
🔎 自分のチャット、自分に共有されたチャット、チャンネル、DM、ノートをまとめて検索。種類やフォルダで絞り込める
👥 同じ共有チャットを今見ているメンバーが表示される
📄 ターミナルのファイルブラウザで文章を選んで「Ask or edit…」。選択部分とファイルを添えてAIに質問・編集を頼める
☁️ Google Driveのファイル選択は、選んだファイルだけにアクセスする方式へ。利用環境でのDrive連携設定は必要
利用にはOpen WebUIの設置・更新と、使うAIモデルの接続設定が必要。共有チャットの編集や回答の再生成は、返信が許可された共有フォルダ内で編集権限がある人が対象。
「あの話、AIの会話？DM？ノート？」で迷子になってた人、ようやく捜索本部を閉じられるｗ
#AI #OpenWebUI
1
2
300
localhost:tokyo
Introducing our new event series: Localhost Lounge. First stop: Tokyo, with @FabCafe
Local AI + talks from Tokyo’s creative, research & startup communities.
Nov 11 · 6–9pm JST
Request to join: luma.com/ox9lohvz
5
3
85
1,901,072
Open WebUI retweeted
What if you could run your own private ChatGPT at home?
Learn from @Tailscale how to build a local AI setup with Ollama and Open WebUI, then access it securely from anywhere: hackernoon.com/self-host-a-l…
14
21
243
1,358,670
Open WebUI retweeted
Build a private AI lab with Proxmox, NixOS, an NVIDIA GPU, Ollama, and Open WebUI, with automated deployment and secure remote access through Tailscale.
#selfhostedllms #localailabsetup...Show more
1
2
3
1,094
Open WebUI retweeted
setup and self hosted codex for my entire family (8 family members)
- @OpenWebUI running harness and environment (docker container)
- @concentrateai router providing model (deepseek v4 flash)
- @Cloudflare dns + tunnel + access, with https handled at Cloudflare’s edge
- @ChatGPT + @Tailscale remote session and make changes to the docker container
- old gaming desktop running debian in my flat in london
this cost me basically nothing but some electricity and credits on @concentrateai which I am migration from @OpenRouter today
making it easy for my family to become ai pilled in a way where I can help guide them - basically setup enterprise ai for my family
helps out a ton by the fact I can setup skills and mcp connectors for my family and they dont have to worry about what skills are good etc
will make a youtube video soon about how @Cloudflare made this setup super fucking easy with cf access helping out with email otp and tunneling
3
1
12
2,134
iPad connected over WiFi AP to the Spark running DeepSeek V4 Flash.
Imagine rolling up to the coffee shop with this naughty little setup.
Harness on the iPad time 👀😅
@NVIDIAAI @vllm_project @OpenWebUI @Apple
19
14
293
49,103
Local AI is very practical.
One prompt: download this arXiv paper PDF and save it into my AI Knowledge. Then summarize the core idea.
That is a real workflow. A tool call, a fetch, a file written into my knowledge base, then a read and a summary. Not a toy prompt.
Running deepseek-v4-flash locally in Open WebUI, with tools and web access on. Start to finish, from my first message to the finished summary, two minutes. I recorded it unedited so nobody has to take my word on the speed.
That is the part people still get wrong about running models on your own hardware. The assumption is that you trade away everything for privacy. Slow tokens, weak reasoning, no tools. That was true a year ago. It is not true now.
No API bill. No rate limits. The paper never touched a third party server, and neither did anything I asked about it.
Two minutes, on my own box (dgx spark).
5
4
22
1,866
Open WebUI retweeted
Interface + inference, in one place.
@OpenWebUI now runs on OpenRouter.
Give your team one chat interface, one unified bill, and access to 400+ frontier and open models through a single API.
10
13
241
18,831
One interface. Every model. That's the idea behind Open WebUI + OpenRouter.
Instead of juggling multiple vendors, API keys, and UIs, organizations can now get a single platform with 600+ models ready to go out of the box.
Interface and inference, together.
5
4
58
160,602
Generating images shouldn’t mean API keys, credits, or sending prompts to the cloud.
This shows how to run image generation locally with Docker Model Runner + Open WebUI, with a chat UI and API on your own machine.
No cloud required.
Read → bit.ly/49HYMmD
3
4
48
6,746
Open WebUI retweeted
Open WebUI native app without Docker setup
github.com/open-webui/deskto…
7
34
385
21,899
Open WebUI retweeted
Another super trick for Hermes Agent, you can create multiple profiles/gateway.
Connect each of them to Open WebUI and grant access to your family members to their own Hermes Agent.
Thanks me later.
26
23
405
21,865
