Persistent workspace data
Accounts, conversations, and collections persist across restarts.
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.
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.
The visible capabilities come from the verified catalog entry; secrets and signed installer assets remain private to the backend.
Accounts, conversations, and collections persist across restarts.
Browser sessions are signed with per-deployment material, so cookies cannot be replayed elsewhere.
A working address with a valid certificate from the first health check, no manual TLS setup.
The deployment is only marked live once the application answers a real health probe.
Point the deployment at hosted or local models and switch without changing the interface.
Shared collections and prompts with administrator-controlled access.
A selection of what the upstream project supports. Credentials for any third-party service are yours to add and revoke.
A single deployment serves every account, with model access and permissions applied per user and conversation history kept on your storage.
Provide one managed interface for approved models without sharing personal provider dashboards.
Work with internal files and collections from a persistent team environment.
Compare supported models and configurations through a consistent user experience.
The hosting layer is the same for every agent, which is what makes a one-click install honest.
Deployments run from a reviewed catalog entry rather than an arbitrary image you have to trust.
Each agent gets its own workload boundary, not a shared container with an unrelated website.
Plan storage is allocated up front so application state survives restarts and releases.
A working address with a certificate from the first health check, with custom domains where supported.
Runtime and resource signals come from the actual workload, so a failure is visible rather than silent.
Grace, suspension, retention, and restoration follow the plan instead of an untracked server.
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 plansDarwa keeps Open WebUI selected when the authenticated launch flow opens.
Use an active agent subscription or choose a plan with enough compute and storage.
Start with an agents.darwa.co address or select an eligible verified custom domain.
The backend verifies the manifest, creates the runtime, and records its service and container identities.
Darwa hosts the open-source application independently; upstream licensing and product behavior remain with its project.
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.
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.
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.
Yes. Administrators choose which providers and models are exposed, so a team can be limited to approved and budgeted options.
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.
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.
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.
Darwa allocates persistent storage according to the selected plan. Important application data should still follow the backup and recovery practices required by your business.
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.
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.
Sign in, pick a plan with enough resources, and Darwa builds the managed runtime around it.