AI chat
Operate LibreChat, configuration and user interface on controlled versions.
WZ-IT operates LibreChat as a central AI interface, connects approved models and tools and secures identities, data flows and updates.
The following are trademarks of their respective owners: LibreChat (the LibreChat project). WZ-IT is an independent service provider and has no business, partnership, or contractual relationship with these companies. We offer independent migration, installation, hosting, and operations services.
LibreChat can combine local inference and external model APIs in one interface. Where data flows depends on every configured endpoint and tool.
We configure the application, database, search, RAG components, authentication and model access and document the permitted data paths.
A self-hosted interface does not make external models local. We label local and external endpoints and restrict models, agents and MCP tools by user group.
Model costs, usage terms and business suitability remain dependent on the respective provider and are not covered by the hosting price.
Application, MongoDB, search, RAG, model access, agents and MCP tools form one security-relevant stack.
Operate LibreChat, configuration and user interface on controlled versions.
Expose approved local and external endpoints, tools and agents.
Connect knowledge data and tools with explicit permissions.
Protect secrets, databases, updates, monitoring and backups.
WZ-IT operates the technical stack; approved data, models, tools and business usage are governed with the customer.
| Area | Responsibility | Scope and boundaries |
|---|---|---|
| LibreChat platform | WZ-IT | Application, databases, proxy, monitoring, backup and updates. |
| Secrets and model endpoints | WZ-IT | Protected credentials and controlled network routes. |
| Models and user groups | Shared | We configure access; the customer approves models and roles. |
| RAG and MCP tools | Shared | WZ-IT integrates technically; data owners approve sources and actions. |
| Content and AI governance | Customer | The customer owns permitted input, output review and internal policy. |
| Custom agents and tools | Optional WZ-IT service | MCP servers, APIs and workflows are developed separately. |
Provide a familiar chat interface with history, files and approved capabilities.
Configure assistants, tools and automation for clearly defined tasks.
Make local inference and supported external model providers available through one controlled platform.
Connect documents and knowledge repositories through the intended RAG components.
Protect authentication, groups, secrets and administrative access for the target architecture.
Connect approved MCP servers and APIs with limited permissions and documented data flows.
Assess existing data and configuration, migrate them in a test run and move to managed operations through a controlled cutover.
Secure SSO, roles, administrative paths and external access for the application and existing infrastructure.
Back up all stateful components consistently and document the recovery path for the agreed scope.
Monitor and update the application and its technical dependencies and operate them under the agreed service level.
A clearly defined operating scope instead of an opaque hosting flat fee.
We set up a test instance for you, usually on the next business day. No payment details required. After seven days it is deleted unless you continue.
We combine the right compute size with ongoing operations, backups, monitoring and a service level appropriate for the criticality of LibreChat. High availability and recovery targets are designed separately where needed.
We also design custom hosting architectures, integrations and migrations around LibreChat. Contact us for a technical assessment.
One managed standard LibreChat application is included in the Starter workload. Business and higher levels add a flexible operations allowance for planned work during regular service hours. Select compute, additional applications, storage and the appropriate service level.
A workload is one compute instance with the applications agreed for it.
One standard app per workload is already included. Additional dedicated servers count as separate workloads.
€79.90 per started TB and month, including daily encrypted offsite backup with 7-day retention.
Enquiry
Briefly describe the current state and objective for LibreChat. We assess infrastructure, integration, and ongoing operations.
The interface is lightweight; local inference, concurrent chats, files, RAG and tools determine the overall platform.
| Usage scenario | Technical starting point | Key factors |
|---|---|---|
| External model APIs and small team | M | Application, MongoDB, search and normal file processing. |
| Several teams with RAG | M or L plus storage | Documents, embeddings, search and background jobs are considered. |
| Local models | GPU assessment | Model, quantisation, context and concurrency determine inference. |
| Many agents and MCP tools | Security and load assessment | Permissions, execution time and external actions are reviewed. |
The standard calculator covers the application; GPUs, model usage, large RAG stores and custom tools are quoted separately.
Interface, models and knowledge sources can run together or in separate controlled locations.
AI interface with approved external or connected local models.
Operate in your account with existing model endpoints.
Local platform with local models or the WZ-IT AI Cube.
Local data and approved external models through controlled routes.
Every model endpoint, knowledge source and MCP tool receives a documented data and permission path.
Chat, files, agents and approved APIs.
Proxy, SSO, groups and restricted administration.
Access to models, agents and tools by group.
Chat, model routing, agents, RAG and MCP.
Chats, configuration, indexes and platform state.
Local inference, external APIs and knowledge services.
Tools with minimum permissions and traceable actions.
Self-hosting the interface does not automatically mean local model processing; external data paths are documented per endpoint.
Answers about models, RAG, MCP and data protection.
Yes, when application, inference, RAG and tools are deployed locally. External endpoints are only added when approved.
LibreChat strongly supports multiple providers, agents and MCP. Open WebUI remains our AI Cube default; selection follows the use case.
Yes. We assess actions, credentials, network routes, user permissions and logging.
No. External API usage and dedicated GPU resources are shown separately.
We back up agreed databases, indexes, configuration and file stores consistently.
As an alternative to managed hosting in the data centre, WZ-IT provides the hardware, configures LibreChat, and handles hardening, monitoring, updates, backup and technical support. Access can be limited to the internal network or enabled through VPN and existing identities.
from EUR 349 excl. VAT / month · plus one-time provisioning and initial setup

08.11.2025
The use of Large Language Models (LLMs) such as GPT-4, Claude or Llama has evolved from experimental applications to mission-critical tools in recent years. However,...
09.11.2025
Local AI inference means running a language or multimodal model on owned hardware rather than through a public API. Organisations gain control over data paths,...
24.11.2025
OpenAI released GPT-OSS 120B as an open-weight reasoning model on 5 August 2025. Its native MXFP4 quantisation allows OpenAI to position the model for a...
These solutions are often used together with LibreChat
These solutions offer similar functionalities and can be evaluated together
These solutions are direct alternatives with similar use cases
No risk: worst case, you leave with a clearer understanding of your project than before.


“WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.”
Whether a specific IT challenge or just an idea - we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.