← All AI agents
Open WebUI logo
Private AI workspaceOpen WebUI

Install Open WebUI
on managed AI hosting.

Give a team a private multi-user interface for local or hosted models, documents, tools, and assistants. Darwa adds the managed runtime, HTTPS, persistent storage, and lifecycle tracking around it.

One-click deploymentAlways-on runtimePersistent storage
A team working together around shared screens in an office
One private interface for every model
1 vCPU minimum2 GB RAM10 GB storageManaged container
Why Open WebUI

The chat interface your team already expects

Open WebUI gives a company the familiar chat experience without handing anyone's conversations to a consumer account. Accounts, roles, shared prompts, and document collections all live inside your deployment.

Interface
Multi-user chat workspace
Deployment
Managed container
Included configuration

Open WebUI features prepared for a managed deployment.

The visible capabilities come from the verified catalog entry; secrets and signed installer assets remain private to the backend.

01

Persistent workspace data

Accounts, conversations, and collections persist across restarts.

02

Generated session secret

Browser sessions are signed with per-deployment material, so cookies cannot be replayed elsewhere.

03

HTTPS routing

A working address with a valid certificate from the first health check, no manual TLS setup.

04

Health verification

The deployment is only marked live once the application answers a real health probe.

05

Multiple model providers

Point the deployment at hosted or local models and switch without changing the interface.

06

Team and document workspace

Shared collections and prompts with administrator-controlled access.

Connects to

What Open WebUI talks to.

A selection of what the upstream project supports. Credentials for any third-party service are yours to add and revoke.

  • Ollama
  • OpenAI
  • Anthropic
  • Groq
  • Mistral
  • LM Studio
  • OpenRouter
  • Azure OpenAI
  • Whisper
  • RAG
  • Web Search
  • Pipelines
  • Markdown
  • LaTeX
  • Code Interpreter
  • Image Gen
Workspace runtime

How Open WebUI serves a team.

A single deployment serves every account, with model access and permissions applied per user and conversation history kept on your storage.

WORKSPACE RUNTIMEMANAGED BY DARWA01AccountsIndividual sign-ins withadministrator and memberroles.02Model routingPoint users at local or hostedproviders you approve.03DocumentsUpload collections and chatagainst them with retrieval.04HistoryConversations persist peraccount on plan storage.
What teams build

Useful starting points for Open WebUI.

Private team chat

Provide one managed interface for approved models without sharing personal provider dashboards.

Document conversations

Work with internal files and collections from a persistent team environment.

Model evaluation

Compare supported models and configurations through a consistent user experience.

Managed runtime

What Darwa runs so you do not have to.

The hosting layer is the same for every agent, which is what makes a one-click install honest.

Verified manifest

Deployments run from a reviewed catalog entry rather than an arbitrary image you have to trust.

Isolated runtime

Each agent gets its own workload boundary, not a shared container with an unrelated website.

Persistent storage

Plan storage is allocated up front so application state survives restarts and releases.

Managed HTTPS

A working address with a certificate from the first health check, with custom domains where supported.

Health tracking

Runtime and resource signals come from the actual workload, so a failure is visible rather than silent.

Subscription lifecycle

Grace, suspension, retention, and restoration follow the plan instead of an untracked server.

Pricing

Plans that can run Open WebUI.

One AI Agent subscription covers the managed runtime, storage, and endpoint. Model provider usage is billed by that provider.

Live pricing is temporarily unavailable. Open WebUI needs at least 1 vCPU, 2 GB RAM, and 10 GB of storage.

View AI agent plans
One-click flow

From catalog page to a running Open WebUI service.

  1. 1

    Choose Install

    Darwa keeps Open WebUI selected when the authenticated launch flow opens.

  2. 2

    Confirm a plan

    Use an active agent subscription or choose a plan with enough compute and storage.

  3. 3

    Choose an address

    Start with an agents.darwa.co address or select an eligible verified custom domain.

  4. 4

    Launch and track

    The backend verifies the manifest, creates the runtime, and records its service and container identities.

Start installing Open WebUI
FAQ

Open WebUI questions.

Darwa hosts the open-source application independently; upstream licensing and product behavior remain with its project.

How many people can share one deployment?+

Open WebUI is multi-user by design and the practical limit is concurrency rather than accounts. Size CPU and memory to the number of people chatting at the same time, not the number registered.

Does it work without an external model provider?+

Yes, if you connect a local runtime such as Ollama. Otherwise it calls hosted providers with keys you supply, and those provider charges remain separate from Darwa hosting.

Are conversations private to each user?+

Each account has its own history, and administrators control sharing and model permissions. Everything stays inside your deployment's storage rather than a third-party workspace.

Can I restrict which models people can use?+

Yes. Administrators choose which providers and models are exposed, so a team can be limited to approved and budgeted options.

What does Darwa manage for Open WebUI?+

Darwa manages the verified deployment manifest, isolated runtime, persistent storage allocation, HTTPS endpoint, health tracking, usage visibility, and paid-plan lifecycle. You manage the agent's models, credentials, tools, content, and decisions.

How do I install Open WebUI?+

Choose Install Open WebUI, sign in, and select an AI Agent plan if the workspace does not already have one. The launch flow keeps Open WebUI selected while you choose its address and start the managed deployment.

What resources does Open WebUI require?+

The current catalog minimum is 1 vCPU, 2 GB RAM, and 10 GB of storage. Real requirements depend on concurrency, models, document volume, integrations, and enabled features.

Does Open WebUI data survive restarts?+

Darwa allocates persistent storage according to the selected plan. Important application data should still follow the backup and recovery practices required by your business.

Can Open WebUI use a custom domain?+

The application can start with a managed Darwa address. A domain you own can be selected when custom-domain support is available for the launch flow and its DNS is verified.

Is Darwa affiliated with Open WebUI?+

No affiliation is implied. Open WebUI is a third-party open-source project. Darwa provides independent managed hosting and links to the upstream repository for project information and licensing.

Ready when you are

Deploy Open WebUI in one click.

Sign in, pick a plan with enough resources, and Darwa builds the managed runtime around it.

Sign-in and an active Darwa AI Agent plan are required before deployment.