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.
3
4
53
159,956
0.9.0, take it or leave it.
github.com/open-webui/open-w…
3
3
34
2,647
How Okta Deploys and Secures AI for its Employees
okta.com/blog/ai/okta-ai-sec…
9
2,074
Available Now: github.com/open-webui/open-w…
2
2
24
4,799
HuggingChat was a huge inspiration for us, thank you and the whole team at @huggingface for leading the way and showing what’s possible for open source AI. You inspired and brought together the entire community, including us. We’re truly grateful for everything you built and shared. 💜
If there’s ever a chance to work together to empower users and democratize AI, we’d be happy to support and collaborate closely with your team at HF. The impact you’ve made will last a long time! 🤗
12
1,080
You don't have to! See more: docs.openwebui.com/license
1
5
481
Available now: github.com/open-webui/open-w…
2
5
42
4,842
Now you can directly record your voice, capture audio from meetings like Google Meet or Zoom (browser only, dedicated apps may have limitations), or upload an audio file—get the transcription and enhance your notes.
1
4
42
5,856
zoom in. stop. ENHANCE.
with the right combination of algorithms...we can read the meaning between the lines.
introducing: notes
7
4
96
13,550
Available now: github.com/open-webui/open-w…
2
27
7,025
Amazing write-up by @vykthur, GenAI/HCI researcher from Microsoft 🙌 Clear, grounded take on MCP’s current challenges—dev experience, deployment, and security all still evolving.
At @OpenWebUI, we believe @OpenApiSpec is all you need ⚡️
We natively support OpenAPI-based servers—easier to build, easier to secure, and ready for real-world apps.
Bonus: We also provide an MCP → OpenAPI bridge to help teams transition with ease.
👉 Learn more: github.com/open-webui/openap…
Controversial take:
🧵
No, MCP's have NOT Won (Yet)
TLDR;
I find much of the recent MCP conversation very puzzling. On one hand, there are articles that make broad claims like “Why MCP Won” but on the other hand, there are too few examples of 3rd party demos or production apps where the MCP infrastructure is integrated with clear benefits (e.g., dev experience, perf etc) over existing approaches.
Full post.
MCP is a great idea, but the reality (IMO) is that it is early and rife with challenges:
- Developer Experience Limitations: The complexity of implementing MCP servers is substantial, with basic examples requiring hundreds of lines of code and limited testing options.
- Deployment and Integration Constraints: MCP clients must run within host applications, creating technical hurdles with performance impacts and transport compatibility issues (most deployment environments have constraints).
- Security Considerations: Building secure MCP-integrated applications requires addressing existing threat vectors, from token theft to prompt injection attacks, especially critical as the protocol gains wider adoption. These issues are not automatically solved or easier as some may have suggested.
All of this is written with humility knowing that the MCP protocol is early and any of the criticisms here will be likely addressed (see the MCP roadmap). Its just worth staying connected to the reality.
2
5
26
5,420