AI apps & knowledge · Setup service
Open WebUI, configured for your work.
Give your team a straightforward place to use selected AI models and company knowledge. We configure the workspace, connect providers, organize access and test it with the intended users.
How the setup goes
From first call to a working Open WebUI.
The exact configuration is agreed around your requirements. This is how we get there.
Agree the task
Before anything is installed, we agree what it should do and what it needs from you.
Scope for Open WebUI
- The intended users and knowledge collections
- The model or hardware you want to use
- A workspace administrator and document owner
Set it up
We install and configure Open WebUI where you decide it runs.
Deploying to open-webui.yourcompany.com
- Install the workspace and configure browser access
- Connect model and document-processing services
- Set up users, groups and selected knowledge
- Test retrieval and restricted access with regular user accounts
Put it to work
Open WebUI is configured around the task you agreed, connected to the accounts it needs.
What the platform can do
- Chat with connected local or hosted models
- Ask questions across selected documents
- Reference retrieved document sources
- Configure access to models and knowledge collections
Connections we can set up
- Notion
- Google Drive
- Microsoft OneDrive
- PostgreSQL
- OpenAI
- Anthropic Claude
Hand it over
Your team gets the access, the notes and a clear way to run it.
Handover
- Administrator access Your team
- Configuration and operating notes Your team
- Accounts and connected services Your team
Make an informed choice
Hosting, access and running costs.
- Self-hosted on your server or suitable local infrastructure
- Local models where hardware and performance fit
- Hosted models or processing services where selected
- Your deployment, provider accounts and workspace data remain under your control
- Administrator access, backups and updates are documented
- Workspace setup and any custom connections
- Hosting or local hardware, plus external provider usage where used
- Applicable enterprise or branding permissions if required
- Optional maintenance and support
Put it to work
Build around the result you want.
Connections to discuss
Before we start
Questions about Open WebUI.
Can everything run locally?
A local setup is possible when the chosen models, document processing and hardware support it. We identify external dependencies and test the intended data path.
Can different users access different knowledge?
Yes, with the appropriate groups and resource grants. We verify the result using regular user accounts and review administrator visibility separately.
Can it use our branding?
Branding changes depend on Open WebUI's current license and your deployment. We check those requirements before including rebranding in the scope.
Start with a conversation
Let’s get Open WebUI working for you.
Tell us what you want to use it for. We will agree the configuration, account access, handover and support before starting.