Pinned official revision
The deployment tracks a reviewed upstream release rather than a moving latest tag.
Use agents, MCP, tools, RAG, and multiple model providers from a secure self-hosted team workspace. Darwa adds the managed runtime, HTTPS, persistent storage, and lifecycle tracking around it.
LibreChat is for teams that refuse to standardise on one provider. Compare answers across vendors in the same thread, attach tools and MCP servers, and keep the whole history under your own account system.
The visible capabilities come from the verified catalog entry; secrets and signed installer assets remain private to the backend.
The deployment tracks a reviewed upstream release rather than a moving latest tag.
Every service in the stack gets its own signing secret at deploy time.
Every container in the stack is recorded in the backend, not just the entrypoint.
A working address with a valid certificate from the first health check, no manual TLS setup.
Attach tool servers over the Model Context Protocol so a capability added once works across conversations.
One workspace fronts many providers, with per-account permissions.
A selection of what the upstream project supports. Credentials for any third-party service are yours to add and revoke.
One workspace fronts many providers, so switching models does not mean switching tools, history, or accounts.
Offer approved providers through one consistent interface instead of separate consumer accounts.
Connect supported tools and MCP servers within a controlled team deployment.
Combine conversation, documents, retrieval, and model choice for internal knowledge work.
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. LibreChat needs at least 1 vCPU, 2 GB RAM, and 20 GB of storage.
View AI agent plansDarwa keeps LibreChat 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.
Yes. LibreChat supports switching provider and model within a conversation, which makes side-by-side comparison part of normal use rather than a separate exercise.
Model Context Protocol lets the workspace call external tool servers through a common interface, so a capability added once is available to the agents you configure.
No. Configure only the providers you intend to use. Unconfigured ones simply do not appear, and provider usage is billed by that vendor separately.
Each account keeps its own history by default. Administrators control registration and which providers and features are available.
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 LibreChat, sign in, and select an AI Agent plan if the workspace does not already have one. The launch flow keeps LibreChat selected while you choose its address and start the managed deployment.
The current catalog minimum is 1 vCPU, 2 GB RAM, and 20 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. LibreChat 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.