docs: Revamp Enterprise section and add Customer Stories page #920
Conversation
Re-write of Open WebUI for Enterprise doc
ℹ️ Documentation PR Guidelines👋 Welcome! This is an automated message posted on all new documentation PRs to help guide our contributors. Just because this comment appeared doesn't mean you have done anything wrong! Please ensure you're using the correct branches: Target branch (where you're merging TO):
Source branch (where you're merging FROM):
If your docs PR depends on a pending PR in open-webui/open-webui:
Please adjust your PR target branch, source branch, and/or draft status accordingly if needed. |
|
|
||
| --- | ||
|
|
||
| ## Why Enterprises Choose Open WebUI |
|
|
||
| **sales@openwebui.com** — Send us your deployment **end user count (seats)**, and let’s explore how we can work together! | ||
|
|
||
| :::info |
There was a problem hiding this comment.
we definitely need these warnings on this page, perhaps not as it currently stands but should at least be briefly mentioned
| | Channel | Description | | ||
| | :--- | :--- | | ||
| | **Private Discord** | A dedicated, real-time communication channel for your team's engineers to chat with ours. | | ||
| | **Email Support** | Ticket-based support for tracking issues, troubleshooting, and formal guidance. | |
There was a problem hiding this comment.
Email Support is incorrect, should be more general here
| | :--- | :--- | | ||
| | **Custom Theming** | White-label Open WebUI to reflect your enterprise identity and brand standards. | | ||
| | **Model Integration** | Engineering assistance to integrate proprietary or third-party AI models tailored for your workflows. | | ||
| | **Private Features** | Work directly with our team to build custom features specific to your organization's needs. | |
There was a problem hiding this comment.
we do not provide this as we're not a dev shop, we can provide high level guidance during consulting hours.
|
|
||
| --- | ||
|
|
||
| ## Built for Open Access |
3 participants
Description
Comprehensive revamp of the "Open WebUI for Enterprise" documentation. The goal was to communicate OWUI values for decision makers, and create a scalable structure for future partners and case studies.
Changes
index.mdxto focus on Enterprise value props.architecture.mddetailing scalability and HA.security.mdcovering compliance (SOC2/HIPAA) and IAM.support.mdto clearly define paid support tiers vs. community help.customization.mdto explain white-labeling and extension boundaries.partners.mdto funnel Agencies/Resellers away from direct sales pipelines.customersfolder to use anindex.mdxlanding page, featuring the Samsung case study and a call-to-action for new stories._category_.jsonin the customers folder to support the new index page.