Skip to content

Agent-readable comparison

LibreChat vs meinGPT

Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI.

This comparison has 44 criteria with sourced findings for both products, including 44 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. No winner is declared. A missing sourced finding is not evidence that a capability is absent.

Same facts as Markdown and JSON. Methodology.

Models

MOD-01 Model catalogue and providers

Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan.

LibreChat

Agent cross-checked Support: partial

The model catalog is configured by the customer across first-party provider integrations and custom endpoints.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • providers: Documented routes include OpenAI, Anthropic, Google, Azure OpenAI, AWS Bedrock and custom compatible services; selection requires enabled credentials and model access.
  • current_models: v0.8.8 release notes mention GPT-6/GPT-6.1 Sol, Claude Opus/Sonnet 5.5 and Gemini 3.8 Flash support. Actual selectable IDs still depend on the installed configuration and provider account.
  • auto_routing: Does the product route between models automatically, and is the chosen model shown? No automatic routing policy showing a chosen model was established, and no configured endpoint was exercised.
  • multimodal_input: Provider-native files support images/PDFs and some providers accept additional Office/audio/video types. Exact acceptance depends on the selected model and transport; no matrix was tested.
  • providers Which model providers are available? [partial]: Documented routes include OpenAI, Anthropic, Google, Azure OpenAI, AWS Bedrock and custom compatible services; selection requires enabled credentials and model access. Sources: librechat:librechat:custom, librechat:librechat:azure, librechat:librechat:bedrock, librechat:librechat:vertex.
  • current_models Which current models are selectable on this plan? [partial]: v0.8.8 release notes mention GPT-6/GPT-6.1 Sol, Claude Opus/Sonnet 5.5 and Gemini 3.8 Flash support. Actual selectable IDs still depend on the installed configuration and provider account. Sources: librechat:librechat:releases.
  • user_choice Can users pick the model per chat? [supported]: Users choose an endpoint/model unless admins enforce model specs or a fixed Agent. Sources: librechat:librechat:modelspec, librechat:librechat:agents.
  • auto_routing Does the product route between models automatically, and is the chosen model shown? [unknown]: auto_routing: Does the product route between models automatically, and is the chosen model shown? No automatic routing policy showing a chosen model was established, and no configured endpoint was exercised.
  • multimodal_input Which models accept images, audio or files? [partial]: Provider-native files support images/PDFs and some providers accept additional Office/audio/video types. Exact acceptance depends on the selected model and transport; no matrix was tested. Sources: librechat:librechat:ocr.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:custom, librechat:librechat:azure, librechat:librechat:bedrock, librechat:librechat:vertex, librechat:librechat:releases, librechat:librechat:modelspec, librechat:librechat:agents, librechat:librechat:ocr.

meinGPT

Agent cross-checked Support: partial

Curated multi-provider models are selected per chat or by context-length routing; the signed DPA and admin approvals affect availability.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business and individually contracted Enterprise web workspace; permitted models depend on workspace approval and DPA; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • auto_routing: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established.
  • providers Which model providers are available? [supported]: Model authors include OpenAI, Anthropic, Google, Mistral, DeepSeek, Moonshot, Qwen, GLM and MiniMax. Hosts are separate from authors. Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2.
  • current_models Which current models are selectable on this plan? [supported]: Active table lists GPT-4.1, GPT-4o/Mini, GPT-5/mini/Nano/Thinking/5.2/5.4/5.5/5.6 Luna/Sol/Terra, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol; o3; Claude Haiku 5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.6/5/5.5; Gemini 3.5 Flash/Flash-Lite, 3.6/3.7/3.8 Flash and 4 Argon; MeinGPT Web; Mistral Medium 3.5/CodeStral; GPT-OSS 120B; Kimi K2.6/K3; DeepSeek V3.2/V4 Flash/V4 Pro/V4.1 Flash; GLM-5.3/Flash, MiniMax-M3 and Qwen3.8 Max. Duplicate EU/provider routes exist. GPT-6 Astra requires accepted AVV 2.0. Model labels do not guarantee one-to-one public provider variant names. Sources: meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:models-rev2, meingpt:meingpt:rates.
  • user_choice Can users pick the model per chat? [supported]: Users select and switch a permitted model per chat. Sources: meingpt:meingpt:models-rev2.
  • auto_routing Does the product route between models automatically, and is the chosen model shown? [partial]: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established. Sources: meingpt:meingpt:models-rev2.
  • multimodal_input Which models accept images, audio or files? [supported]: GPT-4o/5, Claude, Gemini and Mistral Medium/Magistral accept JPEG/PNG/GIF/WEBP; DeepSeek, GPT-OSS, CodeStral and older Kimi K2 do not. Audio uses separate transcription. Sources: meingpt:meingpt:models-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:rates.

MOD-02 Model freshness

Judgment rule: Measure the days from a provider's general release to availability in the product for the last three major releases from OpenAI, Anthropic and Google (and Mistral where offered). Use dated changelogs or observation. Record deprecation notice for retired models.

LibreChat

Agent cross-checked Support: partial

Dated releases document model updates, but measured availability lags and retirement notice periods remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • release_lag_days: What was the lag for each of the last three major releases, per provider? No paired general-release/LibreChat-availability dates for the last three major releases per provider, or binding retirement-notice period, were established.
  • deprecation_notice: How much notice is given before a model is removed? No paired general-release/LibreChat-availability dates for the last three major releases per provider, or binding retirement-notice period, were established.
  • version_pinning: Admins can name explicit model IDs in endpoints/model specs; continuing remote availability remains under provider control.
  • release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: release_lag_days: What was the lag for each of the last three major releases, per provider? No paired general-release/LibreChat-availability dates for the last three major releases per provider, or binding retirement-notice period, were established.
  • changelog Is there a dated public model changelog? [supported]: Public releases and the LibreChat changelog date model updates; v0.8.8 was published 2026-10-01. Sources: librechat:librechat:releases.
  • deprecation_notice How much notice is given before a model is removed? [unknown]: deprecation_notice: How much notice is given before a model is removed? No paired general-release/LibreChat-availability dates for the last three major releases per provider, or binding retirement-notice period, were established.
  • version_pinning Can an admin keep an older model version? [partial]: Admins can name explicit model IDs in endpoints/model specs; continuing remote availability remains under provider control. Sources: librechat:librechat:modelspec, librechat:librechat:custom.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:releases, librechat:librechat:modelspec, librechat:librechat:custom.

meinGPT

Agent cross-checked Support: partial

A dated changelog and explicit retirement rules exist; comparative release-lag medians were not established.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • version_pinning: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded.
  • Unverified release_lag_days: Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted.
  • release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted.
  • changelog Is there a dated public model changelog? [supported]: Public releases include v2.67.0 dated 2026-10-18. Sources: meingpt:meingpt:changes.
  • deprecation_notice How much notice is given before a model is removed? [supported]: Normally four weeks, then reminders at two and one week; provider short notice can shorten this. Opus 4.5 is listed for 23 November retirement; other future dates are in the table. Sources: meingpt:meingpt:lifecycle.
  • version_pinning Can an admin keep an older model version? [partial]: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded. Sources: meingpt:meingpt:lifecycle.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:changes, meingpt:meingpt:lifecycle.

MOD-03 Bring-your-own keys and provider contracts

Judgment rule: Record customer-held API keys, customer cloud accounts (Azure OpenAI, Bedrock, Vertex), and aggregator routes (OpenRouter, LiteLLM) as separate routes. Record what still works without a vendor-provided model, whether prices change with BYO, and documented restrictions. API-key support does not imply support for the customer's own Azure contract.

LibreChat

Agent cross-checked Support: partial

Customer-held provider keys, customer Azure/AWS/Vertex configurations and custom endpoints are documented.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • byo_restrictions: File modalities, tools and other capabilities depend on provider/model support and optional services. A universal BYO feature-parity guarantee was not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:firstchat, librechat:librechat:custom, librechat:librechat:azure, librechat:librechat:bedrock, librechat:librechat:vertex, librechat:librechat:license, librechat:librechat:ocr, librechat:librechat:code.

meinGPT

Agent cross-checked Support: partial

Customer LLM API keys, cloud contracts and arbitrary model endpoints are explicitly excluded from the hosted catalogue.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • own_api_keys: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate.
  • own_cloud_contract: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts.
  • custom_endpoint: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints.
  • byo_pricing: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL.
  • byo_restrictions: Only DeepL has a documented BYOK exception; it does not replace the workspace model route.
  • own_api_keys Can the customer use its own provider API keys? [unsupported]: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate. Sources: meingpt:meingpt:models.
  • own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unsupported]: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts. Sources: meingpt:meingpt:models.
  • custom_endpoint Can an admin add any OpenAI-compatible endpoint? [unsupported]: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints. Sources: meingpt:meingpt:models.
  • byo_pricing Does BYO change the licence price? [partial]: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL. Sources: meingpt:meingpt:models, meingpt:meingpt:translation.
  • byo_restrictions Which features stop working with BYO? [partial]: Only DeepL has a documented BYOK exception; it does not replace the workspace model route. Sources: meingpt:meingpt:models.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:models, meingpt:meingpt:translation.

MOD-04 Local and self-hosted models

Judgment rule: Record support for models running in the customer's environment (vLLM, Ollama, TGI or similar) and which features work with them: chat, RAG, tools, embeddings. Distinguish a documented, supported route from a generic endpoint that happens to work.

LibreChat

Agent cross-checked Support: partial

Local compatible inference and Ollama embeddings are documented; optional services must also be local for a fully private stack.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • feature_parity: Chat and retrieval can use local endpoints. Tool calling and vision depend on the model; external OCR/search/code services are separate. No complete offline fixture was run.
  • vendor_hosted_open_models: Does the vendor host open-weight models in EU/CH? A vendor-hosted EU/Swiss open-weight model service was not established for the MIT self-hosted project.
  • self_hosted_chat Can chat use a customer-hosted model? [supported]: Custom endpoints can point at customer-hosted compatible model servers, including Ollama-compatible setups. Sources: librechat:librechat:custom.
  • self_hosted_embeddings Can retrieval use customer-hosted embeddings? [supported]: The RAG configuration documents Ollama embeddings and local Hugging Face through the appropriate full image. Sources: librechat:librechat:ragcfg.
  • feature_parity Which features fail with self-hosted models? [partial]: Chat and retrieval can use local endpoints. Tool calling and vision depend on the model; external OCR/search/code services are separate. No complete offline fixture was run. Sources: librechat:librechat:ragcfg, librechat:librechat:ocr, librechat:librechat:code.
  • vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [unknown]: vendor_hosted_open_models: Does the vendor host open-weight models in EU/CH? A vendor-hosted EU/Swiss open-weight model service was not established for the MIT self-hosted project.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:custom, librechat:librechat:ragcfg, librechat:librechat:ocr, librechat:librechat:code.

meinGPT

Agent cross-checked Support: partial

Vendor-operated open-model routes exist; customer-hosted LLM and embedding routes were not verified.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • vendor_hosted_open_models: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious.
  • Unverified self_hosted_chat, self_hosted_embeddings, feature_parity: Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
  • self_hosted_chat Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
  • self_hosted_embeddings Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
  • feature_parity Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
  • vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [partial]: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious. Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors.

MOD-05 Model control and usage limits

Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use.

LibreChat

Agent cross-checked Support: partial

Model specs and scoped configuration can limit choices; optional user credit reservations provide a blocking mechanism.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • model_allowlist_by_group: Enforced model specs and role/group configuration overrides can restrict available endpoints/models. The separate management UI is preview; a two-group fixture was not run.
  • data_bound_models: Can admins restrict which models receive connector or knowledge content? A hard binding between each enterprise content source and a permitted model provider was not established in the Agent and access-control guides.
  • user_limits: Balance tracking, initial credits/refills and message moderation limits are operator-configurable, rather than a universal vendor allowance.
  • model_allowlist_by_group Can admins limit models per group? [partial]: Enforced model specs and role/group configuration overrides can restrict available endpoints/models. The separate management UI is preview; a two-group fixture was not run. Sources: librechat:librechat:modelspec, librechat:librechat:admin, librechat:librechat:access.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: data_bound_models: Can admins restrict which models receive connector or knowledge content? A hard binding between each enterprise content source and a permitted model provider was not established in the Agent and access-control guides.
  • default_model Can admins set the default model? [supported]: Model-spec presets can define default endpoint/model configurations. Sources: librechat:librechat:modelspec.
  • user_limits What per-user message or token limits apply, and are they published? [partial]: Balance tracking, initial credits/refills and message moderation limits are operator-configurable, rather than a universal vendor allowance. Sources: librechat:librechat:balance, librechat:librechat:mod.
  • limit_behaviour What happens when a limit is reached? [supported]: Pinned checkBalance reserves credits and throws a TOKEN_BALANCE error when insufficient. This establishes a blocking code path, not an observed end-to-end quota test. Sources: librechat:librechat:balance-pin.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:modelspec, librechat:librechat:admin, librechat:librechat:access, librechat:librechat:balance, librechat:librechat:mod, librechat:librechat:balance-pin.

meinGPT

Agent cross-checked Support: partial

Admins set model access and defaults; personal category limits have documented exceptions.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • limit_behaviour: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories.
  • Unverified data_bound_models: A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run.
  • model_allowlist_by_group Can admins limit models per group? [supported]: Per-team/person allow and deny rules are documented. Workspace admins and free models are exempt; denied chat models fall back, denied API models fail. Sources: meingpt:meingpt:config.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? Unknown. A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run.
  • default_model Can admins set the default model? [supported]: Workspace admins set the default model and chat standards. Sources: meingpt:meingpt:config.
  • user_limits What per-user message or token limits apply, and are they published? [supported]: Six usage levels set monthly EUR limits for text, images, API, other services and meeting bots; no single universal message cap. Sources: meingpt:meingpt:limits.
  • limit_behaviour What happens when a limit is reached? [partial]: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:config, meingpt:meingpt:limits, meingpt:meingpt:api.

Company knowledge

KNOW-01 Files in chat

Judgment rule: Record supported formats, size and count limits, scanned-PDF OCR, tables and spreadsheets, images inside documents, and whether a file is read in full or retrieved in chunks. Upload the shared fixture set (long German PDF, scanned contract, Excel with formulas, PowerPoint) and record failures.

LibreChat

Agent cross-checked Support: partial

Files can be indexed, injected as extracted text or sent directly to compatible model providers.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=New spreadsheet finding at development source a378657583567310c841d652b0f6b00c83e2bd6b; earlier accepted facts retain their cited release pins; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • File counts, sizes and provider acceptance depend on deployment settings.
  • Spreadsheet parsing yields named sheets and CSV values; layout/formula fidelity and the shared fixture remain untested.
  • formats Which formats are accepted? [supported]: Documents include PDF/text/Office formats through configured extraction; provider-native acceptance varies, including Bedrock Office formats and Google audio/video. Sources: librechat:librechat:ocr, librechat:librechat:filecfg.
  • limits What size and count limits apply per file and chat? [partial]: File counts, sizes and MIME patterns are operator/endpoint settings; provider limits may be stricter. The shared fixture was not uploaded. Sources: librechat:librechat:filecfg, librechat:librechat:ocr.
  • ocr Are scanned PDFs read? [supported]: Optional Mistral OCR, Azure/Vertex Mistral OCR and provider-native file processing are documented. Sources: librechat:librechat:ocr.
  • spreadsheets Are Excel tables read with structure intact? [partial]: The inspected built-in XLSX/XLS/ODS parser emits each sheet name and CSV values. The current guide lists a 15 MB built-in parser limit. Workbook formatting, formula recalculation and shared-fixture accuracy were not established. Sources: librechat:librechat:r4-spreadsheet-parser, librechat:librechat:r4-text-current.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [supported]: RAG retrieves indexed chunks; Upload as Text and Agent File Context inject extracted full text, subject to context limits. Sources: librechat:librechat:rag, librechat:librechat:text, librechat:librechat:ocr.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: librechat:librechat:ocr, librechat:librechat:filecfg, librechat:librechat:rag, librechat:librechat:text, librechat:librechat:r4-spreadsheet-parser, librechat:librechat:r4-text-current.

meinGPT

Agent cross-checked Support: partial

Chat uploads and direct sandbox processing have different document behavior.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • spreadsheets: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed.
  • full_vs_chunked: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context.
  • Unverified ocr: No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test.
  • formats Which formats are accepted? [supported]: Text/PDF, images, Word, PowerPoint, Excel, CSV, TXT and URLs are listed; sandbox is needed to read archives and raw mail formats. Sources: meingpt:meingpt:flow.
  • limits What size and count limits apply per file and chat? [supported]: 50 files per chat, 50 MB per non-image file; JPEG/PNG/WEBP/GIF are model-readable images. Provider PDF/page/image limits still apply. Sources: meingpt:meingpt:chat, meingpt:meingpt:models.
  • ocr Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test.
  • spreadsheets Are Excel tables read with structure intact? [partial]: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed. Sources: meingpt:meingpt:chat, meingpt:meingpt:sandbox.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [partial]: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context. Sources: meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:pools.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:flow, meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:sandbox, meingpt:meingpt:pools.

KNOW-02 Knowledge bases and shared collections

Judgment rule: Record curated document collections that persist across chats, who can create and share them, size limits, and how they attach to assistants. Distinguish personal, group and organisation-wide scope.

LibreChat

Agent cross-checked Support: partial

Agents and personal Projects keep files across chats; shared Agent access is distinct from personal Project ownership.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • sharing_scope: Agents can share files/knowledge with permitted users/groups/roles; Projects themselves are personal and cannot be shared or transferred.
  • size_limits: What are the collection limits? No universal collection storage/size allowance was established; limits are deployment and file-configuration dependent.
  • persistent_collections Can users keep document collections across chats? [supported]: Agent File Search/File Context and Project reference files persist for later chats. Sources: librechat:librechat:agents, librechat:librechat:projects.
  • sharing_scope Can collections be shared with users, groups or the whole organisation? [partial]: Agents can share files/knowledge with permitted users/groups/roles; Projects themselves are personal and cannot be shared or transferred. Sources: librechat:librechat:access, librechat:librechat:agents, librechat:librechat:projects.
  • size_limits What are the collection limits? [unknown]: size_limits: What are the collection limits? No universal collection storage/size allowance was established; limits are deployment and file-configuration dependent.
  • assistant_binding Can collections be bound to an assistant? [supported]: Agent File Search and File Context bind retrieved or extracted knowledge to an Agent. Sources: librechat:librechat:agents, librechat:librechat:ocr.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:projects, librechat:librechat:access, librechat:librechat:ocr.

meinGPT

Agent cross-checked Support: supported

Cloud pools persist across chats and attach to assistants; Outpost is a separate local index.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

  • persistent_collections Can users keep document collections across chats? [supported]: Persistent cloud data sources index SharePoint/OneDrive, Drive, Confluence, S3, WebDAV and web content. Sources: meingpt:meingpt:pools.
  • sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Admins share data sources with teams; workspace admins have broad visibility. Sources: meingpt:meingpt:pools.
  • size_limits What are the collection limits? [supported]: Standard cloud raw-data budget is 300 GB across the workspace; indexing new content stops when full. Sources: meingpt:meingpt:pools.
  • assistant_binding Can collections be bound to an assistant? [supported]: Pools bind to assistants or can be selected in a chat; projects themselves cannot bind pools. Sources: meingpt:meingpt:assistants, meingpt:meingpt:projects.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools, meingpt:meingpt:assistants, meingpt:meingpt:projects.

KNOW-03 Enterprise connectors

Judgment rule: List each connector separately with plan, availability and setup owner: SharePoint, OneDrive, Outlook, Teams, Google Drive, Gmail, Confluence, Jira, Notion, Box, Salesforce, ServiceNow, file shares. Record whether the vendor or a third party (or the customer via MCP) provides it, and whether it needs admin consent. A connector listed on a roadmap or partner page is `announced`. An on-prem connector or gateway proves access to local data, not a self-hosted platform (DATA-02).

LibreChat

Agent cross-checked Support: partial

SharePoint and OneDrive have a documented delegated file picker. Other enterprise systems require separately verified tools or connectors.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • microsoft_365: SharePoint Online and OneDrive for Business can be browsed and attached through Entra token reuse/OBO, delegated AllSites.Read and Files.Read.All, and admin consent. Outlook/Teams source access was not established.
  • google_workspace: Which Google sources are connected? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog.
  • atlassian: Confluence and Jira? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog.
  • other_systems: Which other business systems? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog.
  • on_prem_sources: Custom local MCP stdio servers can reach systems available to the deployment, but a maintained file-share/database connector and its permissions were not verified.
  • microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint Online and OneDrive for Business can be browsed and attached through Entra token reuse/OBO, delegated AllSites.Read and Files.Read.All, and admin consent. Outlook/Teams source access was not established. Sources: librechat:librechat:sharepoint.
  • google_workspace Which Google sources are connected? [unknown]: google_workspace: Which Google sources are connected? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog.
  • atlassian Confluence and Jira? [unknown]: atlassian: Confluence and Jira? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog.
  • other_systems Which other business systems? [unknown]: other_systems: Which other business systems? Google Drive/Gmail, Confluence/Jira and other named business-system connectors were not verified from first-party maintained connector documentation; generic MCP compatibility is not a connector catalog.
  • on_prem_sources Can on-prem file shares or databases be connected? [partial]: Custom local MCP stdio servers can reach systems available to the deployment, but a maintained file-share/database connector and its permissions were not verified. Sources: librechat:librechat:mcpcfg.
  • connector_provider Who builds and maintains each connector? [supported]: LibreChat documents the Microsoft picker. Other MCP tool integrations are separately configured and maintained by their respective server authors/operators. Sources: librechat:librechat:sharepoint, librechat:librechat:mcp.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:sharepoint, librechat:librechat:mcpcfg, librechat:librechat:mcp.

meinGPT

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

KNOW-04 Permission-aware retrieval

Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation.

LibreChat

Agent cross-checked Support: partial

Product resource ACLs and delegated Microsoft file selection are documented. Continuing source permissions for copied content remain untested.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • source_permissions_respected: Are source permissions enforced per user? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified.
  • enforcement_point: LibreChat ACLs control Agent/file resources; Microsoft delegated OBO limits source downloads as the signed-in user. No query-time source ACL check for previously copied chunks was established.
  • revocation_delay: How quickly does a removed permission take effect? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified.
  • admin_scope_controls: Operators can scope Agent/resource grants and its selected files. Site/folder/label exclusion across sources was not established.
  • sensitivity_labels: Are Microsoft Purview or similar labels respected? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified.
  • source_permissions_respected Are source permissions enforced per user? [unknown]: source_permissions_respected: Are source permissions enforced per user? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [partial]: LibreChat ACLs control Agent/file resources; Microsoft delegated OBO limits source downloads as the signed-in user. No query-time source ACL check for previously copied chunks was established. Sources: librechat:librechat:access, librechat:librechat:sharepoint.
  • revocation_delay How quickly does a removed permission take effect? [unknown]: revocation_delay: How quickly does a removed permission take effect? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified.
  • admin_scope_controls Can admins exclude sites, folders or labels? [partial]: Operators can scope Agent/resource grants and its selected files. Site/folder/label exclusion across sources was not established. Sources: librechat:librechat:access, librechat:librechat:agents.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: sensitivity_labels: Are Microsoft Purview or similar labels respected? No restricted-document two-user fixture or grant/revocation test was run. Source permission enforcement, revocation delay and Purview label handling remain unverified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:access, librechat:librechat:sharepoint, librechat:librechat:agents.

meinGPT

Agent cross-checked Support: partial

Live OAuth preserves source access; indexed permissions require a separate, default-off setting.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • source_permissions_respected: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run.
  • Unverified revocation_delay, sensitivity_labels: No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown.
  • source_permissions_respected Are source permissions enforced per user? [partial]: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run. Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: Live tools execute under user OAuth. Indexed SharePoint/Drive permissions are mirrored and fail closed when stale; source-permission mode is off by default. Sources: meingpt:meingpt:pool-controls.
  • revocation_delay How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown.
  • admin_scope_controls Can admins exclude sites, folders or labels? [supported]: Admins select imported sources/folders and control team sharing. Sources: meingpt:meingpt:pools.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls, meingpt:meingpt:pools.

KNOW-05 Freshness and sync model

Judgment rule: Record live (federated) search versus a copied index, sync interval, deletion propagation, and where the index is stored. Edit and delete one fixture document and record when answers change. A copied index adds storage location to DATA-01.

LibreChat

Agent cross-checked Support: partial

The RAG API copies uploaded content into PGVector; imported files do not by themselves establish live enterprise synchronization.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • sync_interval: How often does an index refresh? No periodic enterprise-source sync contract, source edit/delete propagation bound or timed fixture was established from the RAG and Microsoft import guides.
  • deletion_propagation: How quickly does a deleted document disappear? No periodic enterprise-source sync contract, source edit/delete propagation bound or timed fixture was established from the RAG and Microsoft import guides.
  • live_or_indexed Is content searched live or copied into an index? [supported]: The RAG API indexes uploaded documents into PostgreSQL/PGVector; file-context mode stores extracted text in Agent instructions. Sources: librechat:librechat:rag, librechat:librechat:ocr.
  • sync_interval How often does an index refresh? [unknown]: sync_interval: How often does an index refresh? No periodic enterprise-source sync contract, source edit/delete propagation bound or timed fixture was established from the RAG and Microsoft import guides.
  • deletion_propagation How quickly does a deleted document disappear? [unknown]: deletion_propagation: How quickly does a deleted document disappear? No periodic enterprise-source sync contract, source edit/delete propagation bound or timed fixture was established from the RAG and Microsoft import guides.
  • index_location Where is indexed content stored? [supported]: The operator chooses the RAG database and its location, independently of the inference provider. Sources: librechat:librechat:rag, librechat:librechat:compose-pin.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:rag, librechat:librechat:ocr, librechat:librechat:compose-pin.

meinGPT

Agent cross-checked Support: partial

Live connectors query the source; cloud pools copy an index to Germany.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • Unverified deletion_propagation: No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified.
  • live_or_indexed Is content searched live or copied into an index? [supported]: Native connectors fetch live; cloud data pools index imported documents. Sources: meingpt:meingpt:pools.
  • sync_interval How often does an index refresh? [supported]: Cloud import runs every 15 minutes. Sources: meingpt:meingpt:pools.
  • deletion_propagation How quickly does a deleted document disappear? [unknown]: How quickly does a deleted document disappear? Unknown. No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified.
  • index_location Where is indexed content stored? [supported]: Cloud pools run at Hetzner in Germany; local Outpost pools stay in the customer network. Sources: meingpt:meingpt:pools.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools.

KNOW-06 Grounding and retrieval quality

Judgment rule: Run the shared question set over the fixture corpus: factual lookups, cross-document questions, German document with an English question, a question with no answer in the corpus. Record citation presence, link accuracy, correct answers and refusals to invent. Disclose model, settings, attempt count and failures. Single runs support a case study, not a ranking.

LibreChat

Agent cross-checked Support: partial

File-search citations are documented; retrieval accuracy remains unmeasured.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • citation_accuracy: Do the cited passages support the answer? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown.
  • cross_language: Does a question in one language find documents in another? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown.
  • no_answer_behaviour: Does it say when the corpus has no answer? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown.
  • observed_accuracy: How many of the question set were answered correctly? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown.
  • citations Are answers linked to specific sources? [supported]: RAG/File Search provides retrieved source references and citation controls. Sources: librechat:librechat:rag, librechat:librechat:access.
  • citation_accuracy Do the cited passages support the answer? [unknown]: citation_accuracy: Do the cited passages support the answer? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown.
  • cross_language Does a question in one language find documents in another? [unknown]: cross_language: Does a question in one language find documents in another? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown.
  • no_answer_behaviour Does it say when the corpus has no answer? [unknown]: no_answer_behaviour: Does it say when the corpus has no answer? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: observed_accuracy: How many of the question set were answered correctly? The shared multilingual factual/cross-document/no-answer question set was not run. Citation correctness, cross-language success, no-answer reliability and observed accuracy remain unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:rag, librechat:librechat:access.

meinGPT

Agent cross-checked Support: partial

Source display is documented; grounding quality remains untested.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • no_answer_behaviour: The guide says source search reports no matching result; actual refusals were not tested.
  • Unverified citation_accuracy, cross_language, observed_accuracy: The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.
  • citations Are answers linked to specific sources? [supported]: Cloud source answers always display sources and this cannot be disabled. Sources: meingpt:meingpt:pool-controls.
  • citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.
  • cross_language Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.
  • no_answer_behaviour Does it say when the corpus has no answer? [partial]: The guide says source search reports no matching result; actual refusals were not tested. Sources: meingpt:meingpt:pools.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pool-controls, meingpt:meingpt:pools.

KNOW-07 Memory and personal context

Judgment rule: Record personal custom instructions, cross-chat memory, project or workspace context, and user controls to view, edit, delete or disable memory. Record whether admins can disable memory organisation-wide.

LibreChat

Agent cross-checked Support: supported

Opt-in user memory stores editable key/value context across chats; Projects and Agents provide additional persistent instructions.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

  • custom_instructions Can users set persistent instructions? [supported]: Projects retain instructions across their chats; Agents retain system instructions. Sources: librechat:librechat:projects, librechat:librechat:agents.
  • cross_chat_memory Does the product remember facts across chats? [supported]: User Memory injects configured key/value entries across chats and is not semantic search over all past conversations. Sources: librechat:librechat:memory.
  • user_memory_controls Can users view, edit and delete memories? [supported]: Users add/edit/remove entries and can toggle memory when permitted. Sources: librechat:librechat:memory.
  • admin_memory_controls Can admins turn memory off? [supported]: Memory is disabled until configured and its feature permissions can be restricted by role. Sources: librechat:librechat:memory, librechat:librechat:access.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:projects, librechat:librechat:agents, librechat:librechat:memory, librechat:librechat:access.

meinGPT

Agent cross-checked Support: partial

Personal instructions and user-specific assistant memory are documented.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • user_memory_controls: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries.
  • custom_instructions Can users set persistent instructions? [supported]: Preferences store a persistent system instruction applied with workspace and assistant context. Sources: meingpt:meingpt:preferences.
  • cross_chat_memory Does the product remember facts across chats? [supported]: Enabled assistants share a personal user memory store across chats, not a team store. Sources: meingpt:meingpt:memory.
  • user_memory_controls Can users view, edit and delete memories? [partial]: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries. Sources: meingpt:meingpt:memory.
  • admin_memory_controls Can admins turn memory off? [supported]: Admins can disable or remove Memory from the permitted tools. Sources: meingpt:meingpt:memory.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:preferences, meingpt:meingpt:memory.

Assistants and agents

AGT-01 Custom assistants

Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here.

LibreChat

Agent cross-checked Support: supported

Agents combine instructions, a model, knowledge and tools, with version history and a permissioned internal catalog.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

  • create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: The Agent Builder creates reusable instructions/model/files/tools/skills configurations. Sources: librechat:librechat:agents.
  • creator_permissions Can admins limit who creates them? [supported]: AGENTS CREATE and sharing permissions can be restricted by role; resource grants control access. Sources: librechat:librechat:access.
  • sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Agent ACLs support users, groups, roles and all authenticated users when public sharing is permitted. Sources: librechat:librechat:access.
  • catalogue Is there an internal assistant directory? [supported]: Agents have a marketplace/catalog and searchable builder tool library. Sources: librechat:librechat:agents.
  • prompt_library Are shared prompt templates available? [supported]: Prompt resources have use/create/share/share-public permissions and ACLs. Sources: librechat:librechat:access.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:access.

meinGPT

Agent cross-checked Support: supported

Assistants combine model, instructions, tools and knowledge, with governed creation and sharing.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

  • create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: The editor supports instructions, model, files, pools, connectors and built-in tools. Sources: meingpt:meingpt:assistants.
  • creator_permissions Can admins limit who creates them? [supported]: Request-enabled permissions restrict assistant creation/sharing/publication by team or person; admins are exempt. Sources: meingpt:meingpt:permissions.
  • sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Team and direct-person assistant sharing are documented; workspace-wide publication is admin-only by default. Sources: meingpt:meingpt:permissions, meingpt:meingpt:roles.
  • catalogue Is there an internal assistant directory? [supported]: The navigation lists personal assistants and shared resources. Sources: meingpt:meingpt:assistants.
  • prompt_library Are shared prompt templates available? [supported]: Prompt folders can be personal, workspace or department scoped. Sources: meingpt:meingpt:prompts.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:assistants, meingpt:meingpt:permissions, meingpt:meingpt:roles, meingpt:meingpt:prompts.

AGT-02 Tools, actions and MCP

Judgment rule: Record built-in tools, custom actions (OpenAPI), MCP client support (local and remote servers), authentication model per tool (shared service account or per-user OAuth), and admin approval of tools. Verify one external-tool call and its access boundary.

LibreChat

Agent cross-checked Support: partial

Agent tools include file search, code, web and Actions, with local/remote MCP and configurable approval boundaries.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Customer-operated or third-party MCP servers, Optional separate Code Interpreter service; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • tool_approval: Agent/code environments document approval modes and individual tool-call approvals. The default policy and every external side-effect boundary were not exercised.
  • builtin_tools Which tools are built in? [supported]: Agent capabilities include file search/context, web search, memory and optionally configured code execution/image tools. Sources: librechat:librechat:agents, librechat:librechat:images.
  • custom_actions Can admins add API actions? [supported]: Agents support custom API Actions configured in the tool library. Sources: librechat:librechat:agents.
  • mcp_client Can it use remote MCP servers, and with what admin control? [supported]: Configured MCP transports include stdio, SSE and Streamable HTTP; YAML and permissioned UI setup are documented. Sources: librechat:librechat:mcp, librechat:librechat:mcpcfg.
  • tool_auth Do tools act as the user or as a shared account? [supported]: MCP supports configured credentials/headers and OAuth; credential and resource ownership scope depends on each server configuration. Sources: librechat:librechat:mcp, librechat:librechat:mcpcfg.
  • tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Agent/code environments document approval modes and individual tool-call approvals. The default policy and every external side-effect boundary were not exercised. Sources: librechat:librechat:agents, librechat:librechat:code.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:images, librechat:librechat:mcp, librechat:librechat:mcpcfg, librechat:librechat:code.

meinGPT

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

AGT-03 Web search and deep research

Judgment rule: Record web search on/off control per organisation and group, search provider, citation of web sources, deep or multi-step research, and whether queries leave the residency boundary. Admins of regulated companies often need web search off.

LibreChat

Agent cross-checked Support: partial

Web search combines configured search, scraping and optional reranking services; source queries can leave the installation boundary.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • deep_research: Agents can perform repeated tool operations and web research. No dedicated report fixture, quality result or preset research SLA was verified.
  • web_search Is web search available? [supported]: Tool-capable chats/Agents can use the configured web search capability. Sources: librechat:librechat:web, librechat:librechat:agents.
  • admin_toggle Can admins disable it per organisation or group? [supported]: WEB_SEARCH feature permissions control use; operators configure whether its provider stack is available. Sources: librechat:librechat:access, librechat:librechat:web.
  • search_provider Which search provider handles queries, and where? [supported]: Documented choices include Serper, SearXNG, Tavily and Keenable, with Firecrawl/Tavily/Keenable scraping and optional Jina/Cohere reranking. Geography depends on the chosen services. Sources: librechat:librechat:web.
  • deep_research Is multi-step research with a report available? [partial]: Agents can perform repeated tool operations and web research. No dedicated report fixture, quality result or preset research SLA was verified. Sources: librechat:librechat:agents, librechat:librechat:web.
  • web_citations Are web sources cited? [supported]: The web-search guide documents source references/citations from search and fetched content. Sources: librechat:librechat:web.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:web, librechat:librechat:agents, librechat:librechat:access.

meinGPT

Agent cross-checked Support: supported

Linkup powers cited web search and Deep Research; admins can restrict app access.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

  • web_search Is web search available? [supported]: Search can be switched on in chat, is always on in MeinGPT Web and runs in the Recherche app. Sources: meingpt:meingpt:web.
  • admin_toggle Can admins disable it per organisation or group? [supported]: Request-enabled per-team/person app controls include Web search. Sources: meingpt:meingpt:permissions.
  • search_provider Which search provider handles queries, and where? [supported]: Linkup processes search; the register lists Azure France. Prompt terms can enter generated search queries. Sources: meingpt:meingpt:web, meingpt:meingpt:subprocessors.
  • deep_research Is multi-step research with a report available? [supported]: The research app has a user-controlled multi-step Deep Research mode. Sources: meingpt:meingpt:web.
  • web_citations Are web sources cited? [supported]: Results include source previews and page references. Sources: meingpt:meingpt:web.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:web, meingpt:meingpt:permissions, meingpt:meingpt:subprocessors.

AGT-04 Workflows and automation

Judgment rule: Record no-code or low-code workflows, scheduled prompts, triggers from email, forms or business systems, and multi-step chains. Name where they run and who can build them. A shared prompt template is not a workflow.

LibreChat

Agent cross-checked Support: partial

Experimental Scheduled Chats run saved Agents on cron schedules; beta Agent Events can receive external deliveries.

Availability: beta · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Experimental schedules explicitly enabled, Beta Agents API for external Agent Events; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • workflow_builder: Agent Builder supports tool workflows and subagent configurations; no general business no-code flow editor was established.
  • event_triggers: The beta Agents API includes authenticated Agent Events. A built-in email/form trigger catalog was not verified.
  • workflow_builder Is there a workflow or chain builder? [partial]: Agent Builder supports tool workflows and subagent configurations; no general business no-code flow editor was established. Sources: librechat:librechat:agents.
  • scheduled_tasks Can prompts or assistants run on a schedule? [supported]: Scheduled Chats supports hourly/daily/weekly/custom cron with time zones, owner scope and execution checks; it is experimental and off by default. Sources: librechat:librechat:schedule.
  • event_triggers Can external events start a workflow? [partial]: The beta Agents API includes authenticated Agent Events. A built-in email/form trigger catalog was not verified. Sources: librechat:librechat:api.
  • builder_audience Is building aimed at business users, IT or developers? [supported]: Agent Builder is a user UI; API-event and runtime configuration require technical deployment work. Sources: librechat:librechat:agents, librechat:librechat:schedule, librechat:librechat:api.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:schedule, librechat:librechat:api.

meinGPT

Agent cross-checked Support: supported

Multi-step workflows are documented; scheduled/event automations are request-enabled beta.

Availability: beta · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • Workflow editor is documented separately from request-enabled beta scheduled tasks; beta is not universal plan availability.
  • workflow_builder Is there a workflow or chain builder? [supported]: A project editor chains prompts with variables and per-step models, or Buddy drafts the workflow. Sources: meingpt:meingpt:workflows.
  • scheduled_tasks Can prompts or assistants run on a schedule? [supported]: Support enables beta tasks with daily, weekly, monthly or selected calendar schedules. Sources: meingpt:meingpt:scheduled.
  • event_triggers Can external events start a workflow? [supported]: Beta tasks accept tokenized webhooks and task-specific email addresses. Sources: meingpt:meingpt:scheduled.
  • builder_audience Is building aimed at business users, IT or developers? [supported]: Members can build with natural-language Buddy help or manual steps, subject to admin rights. Sources: meingpt:meingpt:workflows.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:workflows, meingpt:meingpt:scheduled.

AGT-05 Agentic task execution

Judgment rule: Record an agent mode that plans and carries out multi-step tasks with tools (browser, files, connectors), with visible steps, user confirmation of side effects and stop control. Run one fixture task (gather three documents, draft a summary, propose an email). Record interventions and what ran. A final claim of success is not proof.

LibreChat

Agent cross-checked Support: partial

Agent runs expose reasoning/tool activity and optional approval, interruption and cooperative stop controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • No gather-documents, draft-summary and propose-email task was run.
  • Highly experimental attached workspaces are distinct from ordinary Agent tool use.
  • agent_mode Is there an agent mode for multi-step tasks? [supported]: Agents execute multi-step tool workflows; code/workspace capabilities require a compatible separately deployed service. Sources: librechat:librechat:agents, librechat:librechat:code.
  • visible_steps Are steps and tool calls shown? [supported]: Activity groups and tool cards distinguish preparation, execution, completion, cancellation and failure. Sources: librechat:librechat:agents.
  • side_effect_confirmation Must the user confirm actions with side effects? [partial]: Attached environments can expose Ask before changes/Accept edits/Full access, bounded by operator tool rules. This is configurable, not a guarantee that all side effects require confirmation. Sources: librechat:librechat:agents, librechat:librechat:code.
  • stop_control Can the user stop a running task? [partial]: The release documents interruption/steering; ordinary background-tool cancellation is optional and cooperative, so an uncooperative tool may still finish. Sources: librechat:librechat:agents, librechat:librechat:releases.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:code, librechat:librechat:releases.

meinGPT

Agent cross-checked Support: partial

Assistants can execute successive tool calls, show progress and stop; per-action confirmation is absent.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • side_effect_confirmation: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog.
  • agent_mode Is there an agent mode for multi-step tasks? [supported]: Assistant tools run multiple sequential steps within a response and stop at a bounded tool-call budget. Sources: meingpt:meingpt:assistants.
  • visible_steps Are steps and tool calls shown? [supported]: Tool/reasoning steps and progress are shown in chat. Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat.
  • side_effect_confirmation Must the user confirm actions with side effects? [unsupported]: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog. Sources: meingpt:meingpt:tools.
  • stop_control Can the user stop a running task? [supported]: The input button changes to Abbrechen and stops response generation while preserving text. Sources: meingpt:meingpt:chat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat, meingpt:meingpt:tools.

AGT-06 Programmable access

Judgment rule: Record a public API for chat, assistants and knowledge, SDKs, API authentication, rate limits and whether API use counts against the same governance (audit, budgets, model restrictions). Being an MCP client is different from exposing the product over MCP.

LibreChat

Agent cross-checked Support: partial

The beta Agents API provides inference, Agent management and authenticated events; deployment guards and limitations are explicit.

Availability: beta · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • knowledge_api: The beta management surface includes Agent/Skill management. A complete public knowledge-ingestion contract and fixture were not verified.
  • api_governance: Agent access and remote-agent permissions gate APIs, with source identity bound for events. Complete logging/budget/model parity across routes was not tested.
  • mcp_server: Does the product expose itself to other agents over MCP? A native product-wide MCP server was not established; being an MCP client does not establish that interface.
  • chat_api Is there an API for chat and assistants? [supported]: Chat Completions and Open Responses interfaces expose saved Agents, with API-key or configured OIDC authentication. Sources: librechat:librechat:api.
  • knowledge_api Can documents be loaded through an API? [partial]: The beta management surface includes Agent/Skill management. A complete public knowledge-ingestion contract and fixture were not verified. Sources: librechat:librechat:api.
  • api_governance Do audit, budgets and model rules apply to API use? [partial]: Agent access and remote-agent permissions gate APIs, with source identity bound for events. Complete logging/budget/model parity across routes was not tested. Sources: librechat:librechat:api, librechat:librechat:access.
  • mcp_server Does the product expose itself to other agents over MCP? [unknown]: mcp_server: Does the product expose itself to other agents over MCP? A native product-wide MCP server was not established; being an MCP client does not establish that interface.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:api, librechat:librechat:access.

meinGPT

Agent cross-checked Support: partial

Enterprise-enabled APIs cover chat, assistants and workflows with model and budget enforcement.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Enterprise API, explicitly enabled; no public add-on price; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • api_governance: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established.
  • Unverified knowledge_api, mcp_server: A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide.
  • chat_api Is there an API for chat and assistants? [supported]: Bearer-key chat completions, assistants, workflow runs, embeddings and transcription are documented; personal keys require Enterprise enablement. Sources: meingpt:meingpt:api, meingpt:meingpt:outlook.
  • knowledge_api Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide.
  • api_governance Do audit, budgets and model rules apply to API use? [partial]: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established. Sources: meingpt:meingpt:api, meingpt:meingpt:config, meingpt:meingpt:audit.
  • mcp_server Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:api, meingpt:meingpt:outlook, meingpt:meingpt:config, meingpt:meingpt:audit.

Daily work

WORK-01 Clients and access points

Judgment rule: List web, desktop (Windows, macOS), iOS, Android, mobile browser and browser extension separately. For each, record login with company SSO, feature gaps against web, and MDM/Intune deployability. An installable app is different from a mobile website.

LibreChat

Agent cross-checked Support: partial

The main deployment is a responsive browser client. Native clients, MDM and a supported sidebar extension were not verified.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • desktop_apps: Windows and macOS apps? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration.
  • mobile_apps: Docs describe mobile navigation and temporary-chat controls in the web UI. No native iOS/Android client with company SSO was established.
  • browser_extension: Is there a browser extension or sidebar? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration.
  • managed_deployment: Can IT deploy and configure clients through MDM? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration.
  • client_feature_gaps: Desktop/mobile layouts expose different navigation controls; no comprehensive parity matrix was tested.
  • web Is a full web client available? [supported]: A Docker/npm deployment serves a browser application at the configured server URL. Sources: librechat:librechat:firstchat, librechat:librechat:local.
  • desktop_apps Windows and macOS apps? [unknown]: desktop_apps: Windows and macOS apps? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration.
  • mobile_apps iOS and Android apps with SSO? [partial]: Docs describe mobile navigation and temporary-chat controls in the web UI. No native iOS/Android client with company SSO was established. Sources: librechat:librechat:retention, librechat:librechat:insights.
  • browser_extension Is there a browser extension or sidebar? [unknown]: browser_extension: Is there a browser extension or sidebar? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration.
  • managed_deployment Can IT deploy and configure clients through MDM? [unknown]: managed_deployment: Can IT deploy and configure clients through MDM? The self-host installation and client docs did not establish native Windows/macOS apps, a first-party browser extension or Intune/MDM configuration.
  • client_feature_gaps Which features are missing on mobile? [partial]: Desktop/mobile layouts expose different navigation controls; no comprehensive parity matrix was tested. Sources: librechat:librechat:retention, librechat:librechat:insights.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:firstchat, librechat:librechat:local, librechat:librechat:retention, librechat:librechat:insights.

meinGPT

Agent cross-checked Support: partial

The platform is browser-based; Outlook has a separate centrally deployed add-in.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace, meinGPT Outlook add-in, meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Business/Enterprise web workspace; Outlook add-in requires Enterprise API enablement and personal API key; add_ons=Enterprise API enabled for Outlook add-in; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • managed_deployment: The Outlook add-in can be assigned to users or groups in Microsoft 365 integrated apps; general desktop/mobile MDM configuration was not found.
  • Unverified desktop_apps, mobile_apps, browser_extension, client_feature_gaps: No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
  • web Is a full web client available? [supported]: The terms define a browser-accessible workspace. Sources: meingpt:meingpt:terms.
  • desktop_apps Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
  • mobile_apps iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
  • browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
  • managed_deployment Can IT deploy and configure clients through MDM? [partial]: The Enterprise API-enabled Outlook add-in can be assigned to users/groups through Microsoft365 integrated apps. It supports Outlook web, Windows classic/new and Mac; each user needs a personal meinGPT API key. General desktop/mobile MDM configuration was not established. Sources: meingpt:meingpt:outlook.
  • client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:outlook.

WORK-02 Office suite and Teams integration

Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02.

LibreChat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

meinGPT

Agent cross-checked Support: partial

A documented Outlook add-in operates in the received-message view and needs Enterprise API access.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT Outlook add-in; version=Public documentation checked 2026-10-21; plan=Enterprise API enabled workspace; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • licence_prerequisites: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated.
  • Unverified word_excel_powerpoint, teams, google_workspace_apps: Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
  • word_excel_powerpoint Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
  • outlook Does it work inside Outlook? [supported]: Outlook Web, Windows classic/new and Mac support summarizing the selected received email and drafting replies; compose view is excluded. Sources: meingpt:meingpt:outlook.
  • teams Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
  • google_workspace_apps Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
  • licence_prerequisites Which licences or consents are needed? [partial]: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated. Sources: meingpt:meingpt:outlook.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:outlook.

WORK-03 Translation and writing

Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results.

LibreChat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

meinGPT

Agent cross-checked Support: partial

Dedicated text/document translation uses EU Google/DeepL routes and managed glossaries.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • document_translation: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested.
  • writing_tools: Quick Actions rewrite answers, including more formal and improve options.
  • Unverified formality_and_variants: Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated.
  • document_translation Can whole documents be translated with formatting kept? [partial]: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested. Sources: meingpt:meingpt:translation.
  • translation_engine Which engine translates? [supported]: Default Google Cloud Translate for text and DeepL for documents; own DeepL key switches both to DeepL. Sources: meingpt:meingpt:translation.
  • glossaries Are company glossaries supported? [supported]: Workspace admins create per-language-pair glossaries and import CSV; exact word forms must match. Sources: meingpt:meingpt:translation.
  • formality_and_variants Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated.
  • writing_tools Are dedicated rewrite and proofreading tools available? [partial]: Quick Actions rewrite answers, including more formal and improve options. Sources: meingpt:meingpt:chat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:translation, meingpt:meingpt:chat.

WORK-04 Image generation and editing

Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images.

LibreChat

Agent cross-checked Support: partial

Configured Agent image tools generate and edit images; model service rights/costs remain separate.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • admin_control: Operators control tool credentials/configuration and Agent creation/access permissions. A dedicated per-group image-spend switch was not established.
  • usage_terms: What usage rights apply to output? Generated-output rights and complete per-image cost visibility were not established as a LibreChat software entitlement.
  • image_generation Can users generate images, with which models? [supported]: OpenAI Image Tools and additional documented provider tools attach to an Agent; the current guide defaults OpenAI tools to gpt-image-2.5-flare. Sources: librechat:librechat:images.
  • image_editing Can users edit uploaded images? [supported]: The image guide documents editing/remixing uploaded images using image IDs and compatible tools. Sources: librechat:librechat:images.
  • admin_control Can admins restrict image generation? [partial]: Operators control tool credentials/configuration and Agent creation/access permissions. A dedicated per-group image-spend switch was not established. Sources: librechat:librechat:images, librechat:librechat:access.
  • usage_terms What usage rights apply to output? [unknown]: usage_terms: What usage rights apply to output? Generated-output rights and complete per-image cost visibility were not established as a LibreChat software entitlement.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:images, librechat:librechat:access.

meinGPT

Agent cross-checked Support: partial

Twelve named image variants include reference editing with administrator model controls.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • image_editing: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing.
  • usage_terms: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output.
  • image_generation Can users generate images, with which models? [supported]: FLUX.2 Klein/Pro/Flex/Max, FLUX 1.1 Pro, FLUX.1 Kontext Max; GPT Image 1/Mini/1.5/2; Gemini 2.5 Flash Image and 3 Pro Image. Sources: meingpt:meingpt:images.
  • image_editing Can users edit uploaded images? [partial]: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing. Sources: meingpt:meingpt:images.
  • admin_control Can admins restrict image generation? [supported]: Admins enable models and default; request-enabled permissions can restrict Image app use by teams or persons. Sources: meingpt:meingpt:image-admin, meingpt:meingpt:permissions.
  • usage_terms What usage rights apply to output? [partial]: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output. Sources: meingpt:meingpt:terms, meingpt:meingpt:images.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:images, meingpt:meingpt:image-admin, meingpt:meingpt:permissions, meingpt:meingpt:terms.

WORK-05 Voice and meetings

Judgment rule: Record dictation, read-aloud, live voice conversation, meeting transcription and summarisation, supported languages including Swiss German speech, and where audio is processed.

LibreChat

Agent cross-checked Support: partial

LibreChat documents STT, TTS and a hands-free conversation mode that chains them. Real-time speech-to-speech behavior, meeting outcomes and Swiss German recognition remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Current self-hosted LibreChat Speech Settings documentation retrieved 2026-10-21; no voice-latency or dialect fixture performed; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Optional configured STT/TTS engines and provider credentials; self-hosted speech services need allowedAddresses; deployment_mode=on-premise; region=Customer-selected app infrastructure; audio processing depends on browser or configured external/self-hosted speech engines, with no universal region verified; os=not specified.

Limitations

  • Conversation mode is a chain of transcription, text generation and playback; real-time audio-to-audio behavior, interruption and latency were not verified.
  • Audio location depends on the chosen engine. No meeting or Swiss German fixture was run.
  • dictation Can users dictate prompts? [supported]: Speech configuration provides STT for audio input. Sources: librechat:librechat:speech.
  • read_aloud Can answers be read aloud? [supported]: Speech configuration provides TTS for model responses. Sources: librechat:librechat:speech.
  • voice_conversation Is a live voice mode available? [partial]: speechTab.conversationMode chains STT and TTS for hands-free turns: autoSendText sends the transcript after a configured delay, and automaticPlayback reads a completed response. Microphone recording is initially started by the user. Real-time speech-to-speech, interruption behavior and end-to-end latency were not tested. Sources: librechat:librechat:speech-conversation-r2.
  • meeting_summaries Are meetings transcribed and summarised? [unknown]: No meeting capture/integration, speaker diarization or meeting-summary fixture was verified in the reviewed speech documentation.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Swiss German recognition and transcript quality were not tested; a language setting does not establish dialect accuracy.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:speech, librechat:librechat:speech-conversation-r2.

meinGPT

Agent cross-checked Support: partial

Dictation and meeting transcription are documented; speech quality was not tested.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • Unverified read_aloud, voice_conversation, swiss_german_speech: No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.
  • dictation Can users dictate prompts? [supported]: A microphone transcribes prompts into the input field. Sources: meingpt:meingpt:chat.
  • read_aloud Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.
  • voice_conversation Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.
  • meeting_summaries Are meetings transcribed and summarised? [supported]: Audio/video/transcript uploads and meeting-bot notes are documented; storage Hetzner Germany, Gladia transcription France, Vertex EU summaries. Sources: meingpt:meingpt:meeting.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:chat, meingpt:meingpt:meeting.

WORK-06 Data analysis and document output

Judgment rule: Record code execution for data analysis, charts, and generation of downloadable Word, Excel, PowerPoint and PDF files. Analyse the fixture Excel and request a PowerPoint summary. Record where code runs and whether files are editable.

LibreChat

Agent cross-checked Support: partial

The separate Code Interpreter runs analysis and produces downloadable files; artifacts provide code/HTML/diagram previews.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Separately operated compatible Code Interpreter service, Experimental stateful workspaces only if explicitly configured; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • charts: Code execution and generated-file downloads support chart artifacts, but the shared spreadsheet/chart fixture was not run.
  • office_file_output: Generated files are downloadable; editable Word/Excel/PowerPoint fidelity was not established with a fixture.
  • canvas_editing: Artifacts render React/HTML/Mermaid content and source; a rich Office document editor was not established.
  • data_analysis Can it analyse spreadsheets with executed code? [supported]: Configured Code Interpreter executes programs against uploaded files in its separate sandbox. Sources: librechat:librechat:code.
  • charts Can it produce charts? [partial]: Code execution and generated-file downloads support chart artifacts, but the shared spreadsheet/chart fixture was not run. Sources: librechat:librechat:code.
  • office_file_output Can it create Word, Excel or PowerPoint files? [partial]: Generated files are downloadable; editable Word/Excel/PowerPoint fidelity was not established with a fixture. Sources: librechat:librechat:code.
  • canvas_editing Is there a document or canvas editor for iterating on output? [partial]: Artifacts render React/HTML/Mermaid content and source; a rich Office document editor was not established. Sources: librechat:librechat:artifacts.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:code, librechat:librechat:artifacts.

meinGPT

Agent cross-checked Support: partial

An isolated EU sandbox executes analysis code and generates downloadable Office files.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • canvas_editing: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original.
  • data_analysis Can it analyse spreadsheets with executed code? [supported]: Python/JavaScript sandbox reads original spreadsheets with pandas/openpyxl and executes code. Sources: meingpt:meingpt:sandbox.
  • charts Can it produce charts? [supported]: Executed matplotlib charts can be returned as PNG. Sources: meingpt:meingpt:sandbox.
  • office_file_output Can it create Word, Excel or PowerPoint files? [supported]: Sandbox libraries support DOCX/XLSX/PPTX; workflows also generate Word/PDF/Excel/CSV/PowerPoint/JSON. Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows.
  • canvas_editing Is there a document or canvas editor for iterating on output? [partial]: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original. Sources: meingpt:meingpt:sandbox.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows.

WORK-07 Sharing and team spaces

Judgment rule: Record chat sharing (link, user, group), shared projects or team spaces, channels or group chat with AI, and commenting. Test sharing a chat with a colleague in another group and record what the recipient sees, including knowledge they lack access to.

LibreChat

Agent cross-checked Support: partial

Shared chat links publish transcript snapshots and optional files. Projects are personal, and shared source permission boundaries need care.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • group_chat: Can several people chat together with the AI? Simultaneous multi-person AI group chat was not established from Projects and shareable-link documentation; link continuation creates a separate personal copy.
  • share_permission_boundary: Published file snapshots are served independently of the owner’s live file ACL. Sharing grants access to the published copy, not continuing source-system authorization; no restricted-source fixture was run.
  • share_chats Can chats be shared inside the organisation? [supported]: Authenticated shared links are supported, with optional public viewing; public unauthenticated access is off by default. Sources: librechat:librechat:share.
  • team_spaces Are shared projects or workspaces available? [unsupported]: Projects specifically cannot be shared or transferred and are personal to the creator. Shared Agents/resources are a separate capability. Sources: librechat:librechat:projects.
  • group_chat Can several people chat together with the AI? [unknown]: group_chat: Can several people chat together with the AI? Simultaneous multi-person AI group chat was not established from Projects and shareable-link documentation; link continuation creates a separate personal copy.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [partial]: Published file snapshots are served independently of the owner’s live file ACL. Sharing grants access to the published copy, not continuing source-system authorization; no restricted-source fixture was run. Sources: librechat:librechat:share.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:share, librechat:librechat:projects.

meinGPT

Agent cross-checked Support: partial

Chat links and shared projects exist; projects preserve private member chat histories.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • group_chat: Each project member has a separate private chat list; shared project chats are not a simultaneous group conversation.
  • Unverified share_permission_boundary: No cross-group chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified.
  • Project chat privacy does not prove absence of every group-chat surface.
  • share_chats Can chats be shared inside the organisation? [supported]: A share toggle creates a link displaying the shared conversation. Sources: meingpt:meingpt:chat.
  • team_spaces Are shared projects or workspaces available? [supported]: Projects share instructions and workflows with Owner/Editor/Member roles. Sources: meingpt:meingpt:projects.
  • group_chat Can several people chat together with the AI? [partial]: Within Projects,each member has a separate private chat list. Simultaneous multi-user group conversation elsewhere was not established. Sources: meingpt:meingpt:projects.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? Unknown. No cross-group chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:chat, meingpt:meingpt:projects.

WORK-08 Interface languages and accessibility

Judgment rule: Record UI languages, focusing on German, French, Italian and English, with translation quality observed (complete, partial, machine-translated). Record response language handling and WCAG conformance statements.

LibreChat

Agent cross-checked Support: partial

English, German, French and Italian UI resources are registered in the pinned client; quality and accessibility conformance were not evaluated.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • dach_language_quality: Are German, French and Italian UIs complete and natural? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified.
  • accessibility_statement: Is there a WCAG conformance statement? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified.
  • admin_ui_languages: Is the admin interface available in German? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified.
  • ui_languages Which UI languages are offered? [supported]: The client i18n implementation registers en, de, fr and it among community-maintained translations. Sources: librechat:librechat:i18n-pin.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: dach_language_quality: Are German, French and Italian UIs complete and natural? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: accessibility_statement: Is there a WCAG conformance statement? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified.
  • admin_ui_languages Is the admin interface available in German? [unknown]: admin_ui_languages: Is the admin interface available in German? No complete DE/FR/IT walkthrough, German separate-admin-panel coverage test or WCAG conformance statement/report was verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:i18n-pin.

meinGPT

Agent cross-checked Support: partial

Platform-language choice exists, but the full UI and accessibility matrix remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • ui_languages: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page.
  • Unverified dach_language_quality, accessibility_statement, admin_ui_languages: No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.
  • ui_languages Which UI languages are offered? [partial]: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page. Sources: meingpt:meingpt:preferences.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.
  • admin_ui_languages Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:preferences.

Administration and governance

ADM-01 Single sign-on and authentication

Judgment rule: Record SAML, OIDC, Microsoft Entra ID, Google, LDAP, MFA enforcement, conditional-access compatibility, domain verification and plan restrictions. Test one SSO login on a trial where possible.

LibreChat

Agent cross-checked Support: partial

Self-hosted authentication supports OAuth/OIDC, SAML and LDAP; local/LDAP TOTP can be enforced.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • conditional_access: Entra authentication and token reuse are documented, but an actual conditional-access/device-policy login was not tested.
  • domain_capture: Can the company claim its email domain? Registration/domain filters were not established as a tenant-wide company-domain ownership claim.
  • sso_protocols Which SSO protocols and identity providers work? [supported]: OIDC/OAuth providers include Entra, Google, Keycloak and Auth0; SAML and LDAP are documented separately. Sources: librechat:librechat:openid, librechat:librechat:saml, librechat:librechat:auth.
  • sso_plan Which plan includes SSO? [supported]: The authentication configuration belongs to the MIT self-hosted project, with no separate SSO licence tariff. Sources: librechat:librechat:license, librechat:librechat:auth.
  • mfa Can MFA be enforced? [supported]: ENFORCE_TWO_FACTOR_AUTHENTICATION requires local/LDAP enrollment and prevents disabling it; federated accounts depend on IdP MFA. Sources: librechat:librechat:auth.
  • conditional_access Do Entra conditional-access policies apply? [partial]: Entra authentication and token reuse are documented, but an actual conditional-access/device-policy login was not tested. Sources: librechat:librechat:entra.
  • domain_capture Can the company claim its email domain? [unknown]: domain_capture: Can the company claim its email domain? Registration/domain filters were not established as a tenant-wide company-domain ownership claim.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:openid, librechat:librechat:saml, librechat:librechat:auth, librechat:librechat:license, librechat:librechat:entra.

meinGPT

Agent cross-checked Support: partial

Microsoft/Google login is included; custom OIDC is enabled on request and SAML is excluded.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • sso_plan: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated.
  • sso_protocols Which SSO protocols and identity providers work? [supported]: Google and Microsoft sign-in plus custom OpenID Connect for Entra, Keycloak, Okta, PingFederate and Authentik. SAML is not supported. Sources: meingpt:meingpt:sso.
  • sso_plan Which plan includes SSO? [partial]: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated. Sources: meingpt:meingpt:sso, meingpt:meingpt:prices.
  • mfa Can MFA be enforced? [supported]: MFA is enforced at the customer IdP; disabling a user prevents new sign-ins but does not immediately invalidate an existing session. Sources: meingpt:meingpt:sso.
  • conditional_access Do Entra conditional-access policies apply? [supported]: Customer IdP controls Conditional Access. Existing sessions expire normally unless separately removing the membership. Sources: meingpt:meingpt:sso.
  • domain_capture Can the company claim its email domain? [supported]: DNS TXT verification enables domain auto-join and optional rejection of invitations into other workspaces; existing external memberships remain. Sources: meingpt:meingpt:sso.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:sso, meingpt:meingpt:prices.

ADM-02 User provisioning and lifecycle

Judgment rule: Record SCIM, just-in-time provisioning, group sync from the identity provider, deprovisioning effects (chats, assistants, knowledge ownership transfer) and licence assignment. Deprovision a test user and record what happens to their content.

LibreChat

Agent cross-checked Support: partial

Entra group synchronization and federated account creation are documented; SCIM and leaver content transfer remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • scim: Is SCIM provisioning supported? SCIM was not established in the authentication/access docs or pinned repository path review. No two-user deprovisioning fixture was run.
  • deprovisioning: The docs provide user deletion scripts, but content ownership transfer and revocation behavior were not fixture-tested.
  • seat_assignment: Operators manage accounts/roles under an MIT licence; there is no per-seat licence entitlement in the scoped source.
  • scim Is SCIM provisioning supported? [unknown]: scim: Is SCIM provisioning supported? SCIM was not established in the authentication/access docs or pinned repository path review. No two-user deprovisioning fixture was run.
  • group_sync Are identity-provider groups synced? [supported]: With Entra OIDC token reuse, Graph groups sync at login; resource ACL principal membership has a documented cache. Sources: librechat:librechat:access, librechat:librechat:entra.
  • jit_provisioning Are users created at first login? [supported]: Federated login creates accounts according to the authentication configuration; OpenID/SAML registration cannot be independently disabled. Sources: librechat:librechat:auth.
  • deprovisioning What happens to a removed user's data and shared assets? [partial]: The docs provide user deletion scripts, but content ownership transfer and revocation behavior were not fixture-tested. Sources: librechat:librechat:auth.
  • seat_assignment Can admins assign and reclaim seats? [partial]: Operators manage accounts/roles under an MIT licence; there is no per-seat licence entitlement in the scoped source. Sources: librechat:librechat:auth, librechat:librechat:license.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:access, librechat:librechat:entra, librechat:librechat:auth, librechat:librechat:license.

meinGPT

Agent cross-checked Support: partial

Governance includes SCIM; user provisioning and login-time group sync have separate effects.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform plus Governance provisioning add-on; add_ons=Governance; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • group_sync: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync.
  • deprovisioning: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested.
  • scim Is SCIM provisioning supported? [supported]: Entra SCIM v1 creates/updates/deactivates users, requires a verified domain and workspace enablement, and replaces manual invitations. Sources: meingpt:meingpt:scim, meingpt:meingpt:prices.
  • group_sync Are identity-provider groups synced? [partial]: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync. Sources: meingpt:meingpt:scim, meingpt:meingpt:sso.
  • jit_provisioning Are users created at first login? [supported]: Custom OIDC can join a verified-domain workspace on first authenticated login; plain Microsoft sign-in alone does not grant workspace membership. Sources: meingpt:meingpt:sso, meingpt:meingpt:scim.
  • deprovisioning What happens to a removed user's data and shared assets? [partial]: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested. Sources: meingpt:meingpt:scim.
  • seat_assignment Can admins assign and reclaim seats? [supported]: New SCIM users start as unlicensed viewers unless automatic seat assignment is on; admins can assign seats. Sources: meingpt:meingpt:scim.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:scim, meingpt:meingpt:prices, meingpt:meingpt:sso.

ADM-03 Roles, groups and feature permissions

Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group.

LibreChat

Agent cross-checked Support: partial

Role permissions, resource ACLs and system grants support granular governance; the separate management UI remains preview.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server, Separately deployed LibreChat Admin Panel preview; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Separate Admin Panel preview for GUI management; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • Separate admin management UI is preview; the core authorization model is documented as available.
  • No two-group disabled-feature fixture was run.
  • admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: ADMIN/USER and custom roles exist; capability grants can delegate selected administrative functions without full admin. Sources: librechat:librechat:access.
  • groups Can permissions be set per group? [supported]: Local and Entra groups can receive ACLs, system grants and configuration overrides. Sources: librechat:librechat:access, librechat:librechat:admin.
  • feature_toggles Which features can be switched on or off per group? [supported]: Permissions include Agents, MCP, prompts, memory, search, file search/citations and code execution. Sources: librechat:librechat:access.
  • multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Tenant-scoped API queries and group/configuration boundaries are documented. A commercial multi-entity contract and tested tenant isolation were not established. Sources: librechat:librechat:insights, librechat:librechat:access.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:access, librechat:librechat:admin, librechat:librechat:insights.

meinGPT

Agent cross-checked Support: partial

Role and group controls include request-enabled app permissions and model restrictions.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • multi_entity: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established.
  • admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: Admin, Member and Viewer; unlimited workspace admins and separate team administrators are documented. Workspace admins consume a seat and bypass restrictions. Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions.
  • groups Can permissions be set per group? [supported]: Teams control shared resources and models; admins see all team-shared assets. Sources: meingpt:meingpt:roles, meingpt:meingpt:config.
  • feature_toggles Which features can be switched on or off per group? [supported]: Request-enabled controls restrict image, meeting notes/bot, translation, web, Voice Agent, Buddy and automation use by teams or persons. Sources: meingpt:meingpt:permissions.
  • multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established. Sources: meingpt:meingpt:sso.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions, meingpt:meingpt:config, meingpt:meingpt:sso.

ADM-04 Usage and adoption analytics

Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring.

LibreChat

Agent cross-checked Support: partial

Optional Insights reports identifiable activity; token transactions and optional tracing are separate sources of usage detail.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • breakdowns: Insights supports Agent filtering and user activity; recorded token/context cost details are per model/endpoint. Complete group/feature/assistant exports were not established.
  • export: Can usage data be exported? A documented complete admin analytics export and group/cost-centre dataset were not verified.
  • privacy_modes: Insights is off unless enabled and is capability-gated; it can display names, emails and first-message content. Pseudonymized reporting was not established.
  • adoption_dashboard Is there an adoption dashboard? [supported]: Opt-in Insights reports conversations, unique users, messages, tokens, top users and recent conversations. Sources: librechat:librechat:insights.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [partial]: Insights supports Agent filtering and user activity; recorded token/context cost details are per model/endpoint. Complete group/feature/assistant exports were not established. Sources: librechat:librechat:insights, librechat:librechat:tokens.
  • export Can usage data be exported? [unknown]: export: Can usage data be exported? A documented complete admin analytics export and group/cost-centre dataset were not verified.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [partial]: Insights is off unless enabled and is capability-gated; it can display names, emails and first-message content. Pseudonymized reporting was not established. Sources: librechat:librechat:insights.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:insights, librechat:librechat:tokens.

meinGPT

Agent cross-checked Support: partial

Adoption metrics and cost CSVs have team and anonymization options.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • breakdowns: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated.
  • adoption_dashboard Is there an adoption dashboard? [supported]: Cockpit lists prompts, active users, daily prompts/workflow runs and popular workflows. Sources: meingpt:meingpt:analytics.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [partial]: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated. Sources: meingpt:meingpt:analytics.
  • export Can usage data be exported? [supported]: User/team cost statistics export to CSV. Sources: meingpt:meingpt:analytics.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [supported]: Metric anonymization replaces names with IDs; top-user metrics depend on that setting. Sources: meingpt:meingpt:analytics.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:analytics.

ADM-05 Spend controls and cost allocation

Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts.

LibreChat

Agent cross-checked Support: partial

Optional token-credit balances block admission when insufficient; credit estimates differ from actual cloud invoices.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • cost_visibility: Token transactions and configured token prices support per-user/model estimates. Insights explicitly reports activity rather than monetary billing.
  • budgets: Optional per-user start balances and automatic refills are documented. Group/cost-centre pooled budgets were not established.
  • chargeback: Can costs be exported per cost centre? Cost-centre chargeback exports and reconciliation to actual vendor invoices were not established.
  • cost_visibility Can admins see cost or consumption per user and group? [partial]: Token transactions and configured token prices support per-user/model estimates. Insights explicitly reports activity rather than monetary billing. Sources: librechat:librechat:tokens, librechat:librechat:insights.
  • budgets Can budgets be set per user or group? [partial]: Optional per-user start balances and automatic refills are documented. Group/cost-centre pooled budgets were not established. Sources: librechat:librechat:balance.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [supported]: Pinned balance middleware reserves estimated token cost and throws an error if credits cannot be reserved; no low-budget trial was run. Sources: librechat:librechat:balance-pin.
  • chargeback Can costs be exported per cost centre? [unknown]: chargeback: Can costs be exported per cost centre? Cost-centre chargeback exports and reconciliation to actual vendor invoices were not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:tokens, librechat:librechat:insights, librechat:librechat:balance, librechat:librechat:balance-pin.

meinGPT

Agent cross-checked Support: partial

Personal category budgets and pooled credit provide controls with documented exceptions.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • budget_enforcement: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories.
  • chargeback: CSV cost exports exist by user/team; formal cost-centre coding is not established.
  • cost_visibility Can admins see cost or consumption per user and group? [supported]: Usage-based plans show EUR costs per user/model and team, separately for platform and API. Sources: meingpt:meingpt:analytics.
  • budgets Can budgets be set per user or group? [supported]: Six personal usage levels configure monthly budgets across five categories and are assigned singly or in bulk. Sources: meingpt:meingpt:limits.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [partial]: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api.
  • chargeback Can costs be exported per cost centre? [partial]: CSV cost exports exist by user/team; formal cost-centre coding is not established. Sources: meingpt:meingpt:analytics.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:analytics, meingpt:meingpt:limits, meingpt:meingpt:api.

ADM-06 Audit logs and compliance export

Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model.

LibreChat

Agent cross-checked Support: partial

Operational logs and persisted chats are available; a complete audit retention/integrity or eDiscovery system was not verified.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • admin_events: Backend logs capture errors/debug activity and can include operational/security actions. A complete immutable admin-event schema was not established.
  • content_logging: Chats are persisted in MongoDB subject to retention settings; external tracing is optional. This is not a verified compliance archive.
  • siem_export: Operators can feed log files to external systems such as ELK. A native managed SIEM stream and integrity guarantee were not verified.
  • ediscovery: Are eDiscovery and legal hold supported? No eDiscovery/legal hold, tamper-evident archive or complete prompt/file/connector event coverage was verified.
  • log_retention: The logging guide describes 14-day rotation. Rotation is not evidence of an enforced legal retention or deletion guarantee across external sinks.
  • admin_events Are admin and security events logged? [partial]: Backend logs capture errors/debug activity and can include operational/security actions. A complete immutable admin-event schema was not established. Sources: librechat:librechat:logging.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [partial]: Chats are persisted in MongoDB subject to retention settings; external tracing is optional. This is not a verified compliance archive. Sources: librechat:librechat:retention, librechat:librechat:compose-pin.
  • siem_export Can logs stream to a SIEM or be exported? [partial]: Operators can feed log files to external systems such as ELK. A native managed SIEM stream and integrity guarantee were not verified. Sources: librechat:librechat:logging.
  • ediscovery Are eDiscovery and legal hold supported? [unknown]: ediscovery: Are eDiscovery and legal hold supported? No eDiscovery/legal hold, tamper-evident archive or complete prompt/file/connector event coverage was verified.
  • log_retention How long are logs kept? [partial]: The logging guide describes 14-day rotation. Rotation is not evidence of an enforced legal retention or deletion guarantee across external sinks. Sources: librechat:librechat:logging.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:logging, librechat:librechat:retention, librechat:librechat:compose-pin.

meinGPT

Agent cross-checked Support: partial

Administrative change exports and a separate Outpost search log have distinct retention.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • admin_events: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found.
  • content_logging: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear.
  • siem_export: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established.
  • Unverified ediscovery: No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established.
  • admin_events Are admin and security events logged? [partial]: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found. Sources: meingpt:meingpt:audit, meingpt:meingpt:scim.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [partial]: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear. Sources: meingpt:meingpt:audit.
  • siem_export Can logs stream to a SIEM or be exported? [partial]: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established. Sources: meingpt:meingpt:audit-export.
  • ediscovery Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Unknown. No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established.
  • log_retention How long are logs kept? [supported]: Administrative settings changes are retained indefinitely; Governance Outpost query records are retained 90 days from enablement. Sources: meingpt:meingpt:audit.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:audit, meingpt:meingpt:scim, meingpt:meingpt:audit-export.

ADM-07 Data loss prevention and personal data

Judgment rule: Record detection and handling of personal and confidential data before it reaches a model: redaction, masking, blocking, warning. Record integration with Purview, Netskope or similar, and whether filtering runs locally or at a third party. Send a fixture prompt with a Swiss AHV number and IBAN and record the outcome.

LibreChat

Agent cross-checked Support: partial

Optional server-side content filters support configured pattern detection, blocking and auditing, plus narrowly scoped Agent text redaction. External DLP integration and fixture accuracy remain unknown.

Availability: source-only · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Development source a378657583567310c841d652b0f6b00c83e2bd6b; current Latest (dev) documentation; limited redaction announced in config v1.3.18 on 2026-10-22; plan=Customer-operated LibreChat; optional base-YAML content policies, disabled unless configured; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • Development-source finding; no running instance or AHV/IBAN fixture.
  • Filtering is opt-in and limited to configured sources/fields. Default patterns cover credential shapes, not every PII class.
  • Redaction applies only to eligible fresh Agent text; encrypted originals remain stored.
  • A dedicated external DLP integration remains unverified.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: librechat:librechat:r4-content-filter, librechat:librechat:r4-pii-runtime, librechat:librechat:r4-patterns, librechat:librechat:r4-private-submission, librechat:librechat:r4-filter-middleware, librechat:librechat:r4-config-1318.

meinGPT

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

ADM-08 AI policy and guardrails

Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow.

LibreChat

Agent cross-checked Support: partial

Operators can configure prompts and usage terms; abuse moderation is distinct from semantic content-policy enforcement.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • org_instructions: Enforced model-spec presets and Agent instructions can guide behavior; model-followed instructions are not guaranteed policy enforcement.
  • content_filters: Automated moderation scores rate/authentication/message abuse and can ban users. Semantic topic or PII policy coverage was not established.
  • violation_reporting: Abuse scoring is documented, but a complete organization content-policy violation dashboard and reporting fixture were not established.
  • org_instructions Can admins set organisation-wide instructions? [partial]: Enforced model-spec presets and Agent instructions can guide behavior; model-followed instructions are not guaranteed policy enforcement. Sources: librechat:librechat:modelspec, librechat:librechat:agents.
  • usage_notice Can users be required to accept a usage policy? [supported]: Interface configuration includes custom terms of service and acceptance settings. Sources: librechat:librechat:interface.
  • content_filters Are content filters configurable? [partial]: Automated moderation scores rate/authentication/message abuse and can ban users. Semantic topic or PII policy coverage was not established. Sources: librechat:librechat:mod.
  • violation_reporting Are policy hits visible to admins? [partial]: Abuse scoring is documented, but a complete organization content-policy violation dashboard and reporting fixture were not established. Sources: librechat:librechat:mod.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:modelspec, librechat:librechat:agents, librechat:librechat:interface, librechat:librechat:mod.

meinGPT

Agent cross-checked Support: partial

Workspace instructions and Governance acknowledgements are documented; policy enforcement breadth is limited.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • org_instructions: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer.
  • content_filters: Provider content filtering can stop output; configurable organization-wide topic filters were not established.
  • Unverified violation_reporting: Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run.
  • org_instructions Can admins set organisation-wide instructions? [partial]: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer. Sources: meingpt:meingpt:config.
  • usage_notice Can users be required to accept a usage policy? [supported]: Governance includes multilingual acceptable-use policies for acknowledgement and mandatory courses that block other pages until complete. Sources: meingpt:meingpt:prices, meingpt:meingpt:audit.
  • content_filters Are content filters configurable? [partial]: Provider content filtering can stop output; configurable organization-wide topic filters were not established. Sources: meingpt:meingpt:api.
  • violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:config, meingpt:meingpt:prices, meingpt:meingpt:audit, meingpt:meingpt:api.

Data protection and sovereignty

DATA-01 Hosting location and data residency

Judgment rule: Record country or region separately for chat storage, files and indexes, model inference, backups, logs and telemetry, and support access. Name the cloud provider. Record whether residency is default, a paid option or plan-dependent. "EU data boundary" programmes are recorded with their documented exceptions.

LibreChat

Agent cross-checked Support: partial

Customer operators choose storage and service locations; external model, OCR, search and code services need separate residency decisions.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • backups_logs_region: Logs and mounted data reside in the configured deployment; backup, telemetry and optional tracing geographies depend on operator choices and were not audited.
  • support_access_region: From where can vendor staff access data? No vendor or integrator support-access country restriction was reviewed for this customer-operated deployment.
  • swiss_hosting: A customer may run the software on Swiss infrastructure; no bundled Swiss managed inference/support commitment was established.
  • storage_region Where are chats, files and indexes stored? [supported]: The reference self-hosted stack keeps application data in configured MongoDB/files and retrieval data in PGVector. Its country is chosen by the deployer. Sources: librechat:librechat:compose-pin, librechat:librechat:remote.
  • inference_region Where do model calls run, per provider? [supported]: Customer-selected cloud endpoints/regions or local endpoints determine inference; hosting LibreChat in Switzerland does not place every external model there. Sources: librechat:librechat:custom, librechat:librechat:bedrock, librechat:librechat:vertex.
  • backups_logs_region Where are backups, logs and telemetry? [partial]: Logs and mounted data reside in the configured deployment; backup, telemetry and optional tracing geographies depend on operator choices and were not audited. Sources: librechat:librechat:logging, librechat:librechat:compose-pin.
  • support_access_region From where can vendor staff access data? [unknown]: support_access_region: From where can vendor staff access data? No vendor or integrator support-access country restriction was reviewed for this customer-operated deployment.
  • swiss_hosting Is Swiss hosting available? [partial]: A customer may run the software on Swiss infrastructure; no bundled Swiss managed inference/support commitment was established. Sources: librechat:librechat:remote, librechat:librechat:license.
  • residency_plan Which plan or option provides residency? [supported]: Customer-controlled placement is a self-hosted deployment property, not a separately priced residency licence. Sources: librechat:librechat:remote, librechat:librechat:license.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:compose-pin, librechat:librechat:remote, librechat:librechat:custom, librechat:librechat:bedrock, librechat:librechat:vertex, librechat:librechat:logging, librechat:librechat:license.

meinGPT

Agent cross-checked Support: partial

Germany platform storage and model-specific EU/global routes must be scoped separately.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • inference_region: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions.
  • backups_logs_region: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified.
  • residency_plan: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers.
  • Unverified support_access_region, swiss_hosting: No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found.
  • storage_region Where are chats, files and indexes stored? [supported]: Hetzner Germany hosts chats, accounts, documents and cloud indexes; register identifies Nürnberg/Falkenstein. Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors.
  • inference_region Where do model calls run, per provider? [partial]: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa.
  • backups_logs_region Where are backups, logs and telemetry? [partial]: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:dpa.
  • support_access_region From where can vendor staff access data? [unknown]: From where can vendor staff access data? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found.
  • swiss_hosting Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found.
  • residency_plan Which plan or option provides residency? [partial]: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa, meingpt:meingpt:dpa-page.

DATA-02 Deployment options

Judgment rule: Record multi-tenant SaaS, dedicated single-tenant instance, deployment in the customer's cloud account, on-premise and air-gapped as separate options with plan and availability. Record which features are missing in each mode, who operates it, and the documented seat or contract threshold for each mode, which can differ from the enterprise plan threshold (e.g. dedicated SaaS from 2,000 seats, own cloud from 5,000). A local-network connector or gateway that reaches on-prem data from a vendor-hosted platform is KNOW-03, not on-premise deployment.

LibreChat

Agent cross-checked Support: partial

The project documents local and customer-cloud installs. A free public demo is separate from a production managed service.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server, LibreChat public evaluation demo; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • multi_tenant_saas: The project operates a free public evaluation Demo, not a reviewed production business SaaS offer. Its terms permit data cleanups and disclaim persistence.
  • dedicated_instance: Is a dedicated single-tenant instance offered, from what size? A vendor-operated dedicated production service and its contractual size floor were not established.
  • air_gapped: Local chat/embedding routes exist, but a complete disconnected installation and its full dependency behavior were not verified.
  • mode_feature_gaps: External APIs, OCR/search services and separate code runtimes need their own availability/networking; there is no verified SaaS/on-prem feature-parity matrix.
  • multi_tenant_saas Is a shared SaaS offered? [partial]: The project operates a free public evaluation Demo, not a reviewed production business SaaS offer. Its terms permit data cleanups and disclaim persistence. Sources: librechat:librechat:demo, librechat:librechat:firstchat.
  • dedicated_instance Is a dedicated single-tenant instance offered, from what size? [unknown]: dedicated_instance: Is a dedicated single-tenant instance offered, from what size? A vendor-operated dedicated production service and its contractual size floor were not established.
  • customer_cloud Can it run in the customer's own cloud account, from what size? [supported]: Remote hosting documentation describes customer-selected servers/cloud hosting without a software seat minimum. Sources: librechat:librechat:remote, librechat:librechat:license.
  • on_premise Can the whole platform run on customer infrastructure, from what size? [supported]: Docker/npm installation can run the application and dependencies on customer infrastructure. Sources: librechat:librechat:local, librechat:librechat:compose-pin.
  • air_gapped Can it run without internet access? [partial]: Local chat/embedding routes exist, but a complete disconnected installation and its full dependency behavior were not verified. Sources: librechat:librechat:custom, librechat:librechat:ragcfg.
  • mode_feature_gaps Which features are missing outside SaaS? [partial]: External APIs, OCR/search services and separate code runtimes need their own availability/networking; there is no verified SaaS/on-prem feature-parity matrix. Sources: librechat:librechat:ocr, librechat:librechat:web, librechat:librechat:code.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:demo, librechat:librechat:firstchat, librechat:librechat:remote, librechat:librechat:license, librechat:librechat:local, librechat:librechat:compose-pin, librechat:librechat:custom, librechat:librechat:ragcfg, librechat:librechat:ocr, librechat:librechat:web, librechat:librechat:code.

meinGPT

Agent cross-checked Support: partial

SaaS is offered; terms permit individually agreed on-premise use, while Outpost is a connector.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace, meinGPT Outpost local connector; version=Public documentation checked 2026-10-21; plan=Public SaaS; on-premise only if specifically contracted; add_ons=none stated; deployment_mode=not specified; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • on_premise: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public.
  • mode_feature_gaps: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list.
  • Unverified dedicated_instance, customer_cloud, air_gapped: Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
  • multi_tenant_saas Is a shared SaaS offered? [supported]: The public web workspace and shared organization API limits establish the managed SaaS offer. Sources: meingpt:meingpt:terms, meingpt:meingpt:api.
  • dedicated_instance Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
  • customer_cloud Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
  • on_premise Can the whole platform run on customer infrastructure, from what size? [partial]: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public. Sources: meingpt:meingpt:terms.
  • air_gapped Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
  • mode_feature_gaps Which features are missing outside SaaS? [partial]: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list. Sources: meingpt:meingpt:sandbox.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:api, meingpt:meingpt:sandbox.

DATA-03 Training use and provider retention

Judgment rule: Record whether customer content trains vendor or provider models, by plan and default; zero-data-retention arrangements with model providers; abuse-monitoring retention and human review; and the model provider's terms that apply. A "no training" claim on a marketing page is `vendor-claimed` until the contract or DPA says so.

LibreChat

Agent cross-checked Support: partial

The customer configures model contracts and data paths; a universal no-training or provider-retention promise was not established.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • vendor_training: The self-hosted application stores data in the customer’s configured stack; this architecture is not a contractual promise covering every optional external service.
  • provider_training: Do model providers train on it under this product's contracts? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers.
  • provider_retention: How long do model providers keep prompts, including for abuse monitoring? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers.
  • zero_retention: Is zero data retention available, and on which plan? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers.
  • human_review: Can provider staff review content? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers.
  • vendor_training Does the vendor train on customer content? [partial]: The self-hosted application stores data in the customer’s configured stack; this architecture is not a contractual promise covering every optional external service. Sources: librechat:librechat:compose-pin, librechat:librechat:firstchat.
  • provider_training Do model providers train on it under this product's contracts? [unknown]: provider_training: Do model providers train on it under this product's contracts? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [unknown]: provider_retention: How long do model providers keep prompts, including for abuse monitoring? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers.
  • zero_retention Is zero data retention available, and on which plan? [unknown]: zero_retention: Is zero data retention available, and on which plan? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers.
  • human_review Can provider staff review content? [unknown]: human_review: Can provider staff review content? No specific customer provider agreement, abuse retention/human-review period or zero-retention entitlement was reviewed. Website and Demo privacy policies do not govern arbitrary self-hosted providers.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:compose-pin, librechat:librechat:firstchat.

meinGPT

Agent cross-checked Support: partial

DPA 2.0.1 prohibits training and marks conditional AI services for no permanent provider content copy.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • provider_retention: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified.
  • zero_retention: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version.
  • Unverified human_review: Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide.
  • vendor_training Does the vendor train on customer content? [supported]: Section 5(5) restricts processing to service delivery and excludes other purposes. Sources: meingpt:meingpt:dpa.
  • provider_training Do model providers train on it under this product's contracts? [supported]: Section 5(5) states no subprocessor uses customer data to train its own AI model. Sources: meingpt:meingpt:dpa.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [partial]: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified. Sources: meingpt:meingpt:dpa.
  • zero_retention Is zero data retention available, and on which plan? [partial]: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version. Sources: meingpt:meingpt:dpa.
  • human_review Can provider staff review content? [unknown]: Can provider staff review content? Unknown. Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa.

DATA-04 Retention and deletion

Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation.

LibreChat

Agent cross-checked Support: partial

Normal chats have no default expiry; temporary chats default to 30 days and admins can configure broader expiry modes.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • user_deletion: Users can delete conversations/data and retention sweeps remove files. Copies, backups and external provider deletion were not end-to-end verified.
  • contract_end_deletion: What is deleted at contract end, and when? No commercial contract-end purge/confirmation deadline was reviewed; the Demo’s retention terms are a separate offer.
  • default_retention What is retained and for how long by default? [supported]: The default temporary retention is 720 hours; normal chats persist unless configured under all/ephemeral modes. Memories do not expire with chats. Sources: librechat:librechat:retention.
  • admin_retention Can admins set retention periods? [supported]: Admins set all or ephemeral retention, regular/temporary deadlines and Agent file retention. New settings apply on later saves rather than rewriting every existing record immediately. Sources: librechat:librechat:retention.
  • user_deletion Can users delete their chats and files permanently? [partial]: Users can delete conversations/data and retention sweeps remove files. Copies, backups and external provider deletion were not end-to-end verified. Sources: librechat:librechat:retention, librechat:librechat:settings.
  • contract_end_deletion What is deleted at contract end, and when? [unknown]: contract_end_deletion: What is deleted at contract end, and when? No commercial contract-end purge/confirmation deadline was reviewed; the Demo’s retention terms are a separate offer.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:retention, librechat:librechat:settings.

meinGPT

Agent cross-checked Support: partial

Ordinary chat removal archives; admin retention and contractual deletion use different mechanisms.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • user_deletion: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls.
  • default_retention What is retained and for how long by default? [supported]: Chat/file data stays until instructed deletion; UI Chat löschen archives. Text translations remain until user deletion; document translations persist until account/workspace deletion. Sources: meingpt:meingpt:flow, meingpt:meingpt:translation.
  • admin_retention Can admins set retention periods? [supported]: Release 2.67.0 adds disabled-by-default deletion periods for chats, meetings and automation runs, with a 24-hour wait before a new/shorter period applies. Sources: meingpt:meingpt:changes.
  • user_deletion Can users delete their chats and files permanently? [partial]: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls. Sources: meingpt:meingpt:flow, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt:translation.
  • contract_end_deletion What is deleted at contract end, and when? [supported]: DPA section 12 requires return or requested deletion, including backups, within 30 days after termination or an agreed export window; statutory retention exceptions apply and proof is available on request. Sources: meingpt:meingpt:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:flow, meingpt:meingpt:translation, meingpt:meingpt:changes, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt:dpa.

DATA-05 Sub-processors and foreign-law exposure

Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment.

LibreChat

Agent cross-checked Support: partial

ClickHouse’s acquisition is sourced; the self-hosted deployment still selects its own external processors and contracts.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • subprocessor_list: Is a dated sub-processor list published? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.
  • subprocessor_countries: Which countries do sub-processors operate in? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.
  • change_notification: Are customers notified of sub-processor changes? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.
  • parent_jurisdiction: ClickHouse, Inc. announced the LibreChat acquisition on 2025-11-04 from San Francisco and brought founder/team into ClickHouse. A self-hosted customer contracting entity/governing jurisdiction was not established from that announcement.
  • transfer_mechanism: Which transfer mechanism applies to non-EU/CH processing? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.
  • government_access_policy: Is there a published government-access or transparency policy? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.
  • subprocessor_list Is a dated sub-processor list published? [unknown]: subprocessor_list: Is a dated sub-processor list published? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.
  • subprocessor_countries Which countries do sub-processors operate in? [unknown]: subprocessor_countries: Which countries do sub-processors operate in? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.
  • change_notification Are customers notified of sub-processor changes? [unknown]: change_notification: Are customers notified of sub-processor changes? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: ClickHouse, Inc. announced the LibreChat acquisition on 2025-11-04 from San Francisco and brought founder/team into ClickHouse. A self-hosted customer contracting entity/governing jurisdiction was not established from that announcement. Sources: librechat:librechat:owner.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [unknown]: transfer_mechanism: Which transfer mechanism applies to non-EU/CH processing? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.
  • government_access_policy Is there a published government-access or transparency policy? [unknown]: government_access_policy: Is there a published government-access or transparency policy? No project-wide dated sub-processor/country list, change-notification schedule, transfer instrument or government-access policy was established for arbitrary customer-operated deployments. Website/Demo policies are separate scopes.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:owner.

meinGPT

Agent cross-checked Support: partial

DPA and processing register name providers, conditional use and advance change notices.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • parent_jurisdiction: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified.
  • subprocessor_list Is a dated sub-processor list published? [supported]: DPA Annex 4 is dated 24 September 2026; live function/region register is also public. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors.
  • subprocessor_countries Which countries do sub-processors operate in? [supported]: Contract entities include Germany, Netherlands, Slovenia, Luxembourg, France, Ireland and Finland. Processing register names Germany platform, France backups, Finland, Ireland, Sweden/France and Frankfurt inference routes; EU symbol is processing, not ownership. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors.
  • change_notification Are customers notified of sub-processor changes? [supported]: Section 9 requires notice before additions/replacements and gives two weeks to object on important data-protection grounds, with specified termination rights. Sources: meingpt:meingpt:dpa.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified. Sources: meingpt:meingpt:terms, meingpt:meingpt:subprocessors.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA section 4(3) uses GDPR Article 45 adequacy or Article 46 safeguards for disclosed/instructed transfers; it does not promise a blanket absence of third-country processing. Sources: meingpt:meingpt:dpa.
  • government_access_policy Is there a published government-access or transparency policy? [supported]: Section 7 requires notification where lawful, review/challenge of disproportionate requests, minimization and no compliance with unrecognized third-country requests. Sources: meingpt:meingpt:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors, meingpt:meingpt:terms.

DATA-06 Contracts and regulatory coverage

Judgment rule: Record DPA availability and form (click-through, negotiable), reference to Swiss revDSG and GDPR, governing law and court, EU AI Act documentation (provider or deployer role, transparency materials), and sector-specific materials (FINMA outsourcing, banking secrecy, public sector). No compliance verdict.

LibreChat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

meinGPT

Agent cross-checked Support: partial

A public GDPR DPA and German-law terms are available; sector coverage needs qualification.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • dpa: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised.
  • revdsg_gdpr: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found.
  • ai_act_materials: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established.
  • sector_materials: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found.
  • dpa Is a DPA available, and is it negotiable? [partial]: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found. Sources: meingpt:meingpt:dpa.
  • governing_law Which law and court govern the contract? [supported]: DPA section 13 uses German law; terms choose the competent court at the vendor seat. Sources: meingpt:meingpt:dpa, meingpt:meingpt:terms.
  • ai_act_materials Is EU AI Act documentation provided? [partial]: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established. Sources: meingpt:meingpt:prices.
  • sector_materials Are FINMA or other sector materials provided? [partial]: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found. Sources: meingpt:meingpt:prices.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa, meingpt:meingpt:terms, meingpt:meingpt:prices.

DATA-07 Certifications and attestations

Judgment rule: Record each certificate or report separately: ISO 27001, 27017, 27018, 27701, 42001; SOC 2 Type I/II with period; BSI C5; TISAX; national schemes. Record issuer, scope (which product and entity), validity and access route. A cloud provider's certificate does not certify the product.

LibreChat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

meinGPT

Agent cross-checked Support: partial

ISO and penetration-test documents are advertised behind email access; certificates were not independently verified.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • iso_27001: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim.
  • c5: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service.
  • pentest: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved.
  • Unverified soc2, other_certifications: SOC 2 and other product attestations were not established. No email-gated report was requested.
  • iso_27001 ISO 27001 with scope and validity? [partial]: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim. Sources: meingpt:meingpt:dpa, meingpt:meingpt:trust.
  • soc2 SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested.
  • c5 BSI C5 attestation? [partial]: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service. Sources: meingpt:meingpt:subprocessors.
  • other_certifications Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested.
  • report_access How can customers obtain reports? [supported]: The trust centre asks for email-based access for ISO and SySS 2025 penetration-test documents. Sources: meingpt:meingpt:trust.
  • pentest Are independent penetration test summaries available? [partial]: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved. Sources: meingpt:meingpt:trust.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa, meingpt:meingpt:trust, meingpt:meingpt:subprocessors.

DATA-08 Encryption and key control

Judgment rule: Record encryption at rest and in transit, customer-managed keys (BYOK/HYOK), key location, and private networking (private link, IP allow-lists, VPN).

LibreChat

Agent cross-checked Support: partial

Network and storage security depend on the customer’s deployment; application authentication does not certify encryption of all stored content.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • encryption_at_rest: Is data encrypted at rest? No default at-rest encryption guarantee covering MongoDB/files/PGVector or audited multi-tenant managed-service isolation was established from the installation guides.
  • customer_managed_keys: Operators own infrastructure and application secrets; a documented product HYOK/customer-managed content-encryption service was not verified.
  • tenant_isolation: How are customers separated in shared SaaS? No default at-rest encryption guarantee covering MongoDB/files/PGVector or audited multi-tenant managed-service isolation was established from the installation guides.
  • encryption_at_rest Is data encrypted at rest? [unknown]: encryption_at_rest: Is data encrypted at rest? No default at-rest encryption guarantee covering MongoDB/files/PGVector or audited multi-tenant managed-service isolation was established from the installation guides.
  • customer_managed_keys Can the customer manage or hold the keys? [partial]: Operators own infrastructure and application secrets; a documented product HYOK/customer-managed content-encryption service was not verified. Sources: librechat:librechat:auth, librechat:librechat:compose-pin.
  • private_networking Is private connectivity or IP restriction available? [supported]: Operators deploy the stack on their own network and configure reverse proxies/HTTPS for remote access. Sources: librechat:librechat:remote, librechat:librechat:local.
  • tenant_isolation How are customers separated in shared SaaS? [unknown]: tenant_isolation: How are customers separated in shared SaaS? No default at-rest encryption guarantee covering MongoDB/files/PGVector or audited multi-tenant managed-service isolation was established from the installation guides.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:auth, librechat:librechat:compose-pin, librechat:librechat:remote, librechat:librechat:local.

meinGPT

Agent cross-checked Support: partial

Encryption and logical tenancy are documented; key and private-networking details remain incomplete.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business/Enterprise hosted workspace; CMK entitlement excluded from verified findings; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • CMK is an access/entitlement gap, not an absent capability.
  • encryption_at_rest Is data encrypted at rest? [supported]: Security guide states AES-256 at rest and TLS 1.3; DPA Annex 3 includes encryption at rest/transit. Sources: meingpt:meingpt:security, meingpt:meingpt:dpa.
  • customer_managed_keys Can the customer manage or hold the keys? [unknown]: Unknown for Business or Enterprise. The security FAQ says Customer Managed Keys are on request but does not identify an eligible tier, price, key custody or location. No plan-scoped CMK commitment was verified.
  • private_networking Is private connectivity or IP restriction available? [unknown]: Is private connectivity or IP restriction available? Unknown. A private-link/IP allowlist/VPN product entitlement was not established; Outpost outbound TLS is a source connector rather than a private SaaS endpoint.
  • tenant_isolation How are customers separated in shared SaaS? [partial]: DPA Annex 3 specifies logical tenant separation and network segmentation; no independent isolation test was run. Sources: meingpt:meingpt:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:security, meingpt:meingpt:dpa.

DATA-09 Professional secrecy

Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment.

LibreChat

Agent cross-checked Support: partial

Customer-operated message storage and configurable local/external inference establish part of the content-access boundary. A LibreChat-scoped staff/sub-processor secrecy undertaking or professional-secrecy offering remains unverified.

Availability: unknown · Delivery: unknown
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; message schema and reference Compose pinned to v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional commercial secrecy terms unverified. Public Demo and website policies checked only to distinguish their scope; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected application, storage and model-service locations; no DE/CH professional-secrecy contract variant verified; os=not specified.

Limitations

  • The secrecy undertaking, sub-processor coverage, offering and professional-secrecy-specific documentation remain unknown.
  • content_access: Operator permissions, vendor/support grants, optional service access and provider staff access were not tested or contractually verified.
  • Technical data controls, a DPA, privacy wording and no-training statements do not establish the requested contractual undertaking. No legal compliance assessment is made.
  • secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No LibreChat-scoped § 203 StGB / Art. 321 StGB undertaking binding vendor staff was obtained from the reviewed project documentation and public legal pages. The website privacy policy expressly excludes the self-hosted application; ClickHouse ownership does not establish a product-specific agreement. Sources: librechat:librechat:siteprivacy, librechat:librechat:owner.
  • subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: No self-hosted LibreChat professional-secrecy annex or documented extension to sub-processors was obtained. The separate Demo policy describes processor instruction/security obligations, which do not establish the undertaking requested here or coverage of a customer deployment. Sources: librechat:librechat:secrecy-demo-policy.
  • secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: No dedicated professional-secrecy edition, paid add-on, eligible plan or price was established in the public project/legal materials and targeted searches. The public Demo is evaluation-only and excludes confidential or regulated data; it is a separate surface. Sources: librechat:librechat:demo.
  • content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The pinned reference deployment mounts customer-controlled MongoDB, uploads and logs; the message schema declares ordinary text/content fields. This places host/database operators inside the application trust boundary (an architectural inference, not a permissions audit). The first-chat and endpoint guides route prompts to a selected local or external model with customer credentials. Vendor/support access, optional service operators and provider human access remain deployment- and contract-specific and unverified. Sources: librechat:librechat:compose-pin, librechat:librechat:secrecy-message-pin, librechat:librechat:firstchat, librechat:librechat:custom.
  • secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public installation, endpoint and privacy documents describe technical data paths and distinguish website, Demo and self-hosted software. No LibreChat-specific DE/CH secrecy contract template, covered-party annex or professional-body guidance was located in the reviewed sources. Sources: librechat:librechat:firstchat, librechat:librechat:siteprivacy.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:siteprivacy, librechat:librechat:owner, librechat:librechat:secrecy-demo-policy, librechat:librechat:demo, librechat:librechat:compose-pin, librechat:librechat:secrecy-message-pin, librechat:librechat:firstchat, librechat:librechat:custom.

meinGPT

Agent cross-checked Support: partial

The base AGB contains conditional professional-secrecy duties. Eligibility and executed terms of the separately marketed Governance addendum remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked2026-10-21; plan=Business/Enterprise customer contracts incorporating AGB section12(4); only the base-terms obligation is assessed; add_ons=Separate Governance addendum excluded from verified entitlement; contract required; deployment_mode=multi-tenant-saas; region=Germany/EU platform; model route and deployment exceptions apply; os=not specified.

Limitations

  • The base-terms duties and a separately executed Governance addendum are separate legal documents. No claim that one depends on purchase of the other is made.
  • secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [partial]: For contracts incorporating the published AGB, section12(4) applies when processed data fall under professional secrecy, including §203. It imposes indefinite confidentiality, access only as necessary to perform services and acknowledgement of criminal duties. The clause states no Governance prerequisite. It does not establish a separately executed addendum or Swiss Art321 coverage. Sources: meingpt:meingpt:secrecy-contract-rev2.
  • subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [partial]: Section12(4) requires staff/subcontractors who can access covered data to be bound in at least text form. Subcontracting and services outside the EU require text consent, deemed granted for known providers at contract start. Provider-specific executed undertakings were not retrieved. Sources: meingpt:meingpt:secrecy-contract-rev2.
  • secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: Unknown whether the separate Governance §203 addendum is available with self-service Business or only a contracted platform offer. The calculator lists it under Governance at EUR1.35/user/month annually, but this is not proof of eligibility or a fee for the base AGB duties. Sources: meingpt:meingpt:prices-rev2.
  • content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The base AGB restrict knowledge of covered data to what is necessary for the contracted service. The clause does not promise that staff or model providers can never see plaintext. Agreement-specific access restrictions beyond section12(4) were not verified. Sources: meingpt:meingpt:secrecy-contract-rev2.
  • secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [partial]: The public AGB section12(4) is the verified contract text. A separately executed/template Governance addendum and provider-by-provider undertakings were not obtained. Sources: meingpt:meingpt:secrecy-contract-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:secrecy-contract-rev2, meingpt:meingpt:prices-rev2.

Commercials and vendor

VEN-01 Pricing model and list prices

Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment.

LibreChat

Agent cross-checked Support: partial

MIT software has no licence subscription; hosting, inference and optional runtime services are separately procured.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • add_ons: Optional external code/OCR/search/image services need separately configured endpoints and credentials. Their rates depend on the operator’s contracts.
  • overage: Provider APIs charge their account holder; internal credit balances are governance configuration rather than a single LibreChat usage tariff.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:firstchat, librechat:librechat:code, librechat:librechat:ocr, librechat:librechat:web, librechat:librechat:images, librechat:librechat:balance, librechat:librechat:tokens.

meinGPT

Agent cross-checked Support: partial

Self-service Business costs EUR29/user/month excluding VAT and includes standard-model use. Enterprise and platform-module pricing are outside this scoped offer.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business, monthly billing only; contracted Enterprise/platform calculator excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • The progressive platform calculator is not used as a Business tariff. Its contract eligibility remains outside this finding.
  • pricing_unit What is the pricing unit? [supported]: Business is sold per user per month through self-service Stripe checkout. Premium/reasoning models, API use and meeting-bot recordings are separately metered. Sources: meingpt:meingpt:billing-rev2.
  • list_prices What are list prices per plan, with date and currency? [supported]: Self-service Business is EUR29/user/month, excluding VAT, on monthly billing. No annual discount or progressive marginal tiers are applied to this offer. Sources: meingpt:meingpt:billing-rev2.
  • included_usage What usage is included? [partial]: Standard-model use in Business is unlimited according to the billing guide. Premium/reasoning models, API and meeting bots remain additional; the exact standard-model catalog and any applicable workload restrictions are not fixed by this page. Sources: meingpt:meingpt:billing-rev2.
  • add_ons Which features cost extra? [unknown]: Unknown for self-service Business. The separate platform calculator has Governance/Outpost modules, but their Business eligibility and package prices were not established.
  • overage What do usage beyond limits and premium models cost? [partial]: Business standard models do not consume additional billed usage under the billing guide. Premium/reasoning, API and meeting-bot use draw on workspace credit; meeting bots cost EUR0.80/audio hour. Other route-specific charges depend on the selected service. Sources: meingpt:meingpt:billing-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:billing-rev2.

VEN-02 Scenario cost

Judgment rule: Price three workloads for 12 months: 200, 1,000 and 5,000 users with a disclosed light/regular/power usage mix, in CHF and EUR excluding VAT. Include licences, platform fees, add-ons, model usage and, for self-hosted options, a stated operating assumption. Separate fixed, variable, included and unknown costs. No invented discounts.

LibreChat

Agent cross-checked Support: partial

ALM-14 shared cost assumptions v1.4, 2026-10-21: zero standard licence plus a disclosed Swiss infrastructure/operations and direct-BYO-model budget. Annual CHF/EUR figures are floors plus named unknown costs.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=Analyst-selected direct OpenAI API proxy, not a bundled model, Assumed operations staffing; optional commercial services excluded; deployment_mode=customer-cloud; region=Azure Switzerland North for the reference application infrastructure; standard OpenAI API inference has no Swiss/EU residency assumption; os=not specified.

Limitations

  • ALM-14 shared cost assumptions v1.4, 2026-10-21 are analyst inputs, not vendor sizing or an uptime promise.
  • The budget is a floor because named infrastructure and service costs are unpriced.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:cost-fx, librechat:librechat:cost-model, librechat:librechat:cost-effort.

meinGPT

Agent cross-checked Support: partial

Business-only seat floors are EUR69600 / EUR348000 / EUR1740000 for200/1000/5000 users over12months, each plus unknown workload and contract components.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business at EUR29/user/month, paid monthly for12months; Business standard-chat floor only; add_ons=No paid add-ons included; required extras unknown; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • ALM-14 shared cost assumptions v1.4, 2026-10-21:12months, list prices, excluding VAT;60% light100,30% regular400,10% power1500 messages/user/month;3000 input and600 output tokens/message. Weighted330messages,0.99M input/0.198M output per user/month. Token mix is used only on separately billed routes; this Business standard-chat floor has included usage.
  • ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Vendor currency EUR is primary. Contract-specific extras remain unknown.
  • cost_200 Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 200 users over12months: from EUR69600.00 / CHF64289.52 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.
  • cost_1000 Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 1000 users over12months: from EUR348000.00 / CHF321447.60 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.
  • cost_5000 Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 5000 users over12months: from EUR1740000.00 / CHF1607238.00 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.
  • variable_share Which part depends on usage? [partial]: Business standard-model chat is included. A model-preserving workload outside that standard catalog, premium/reasoning models, API and meeting-bot charges cannot be quantified without the actual route and contract; the variable remainder stays unknown. No provider proxy or progressive-platform tariff is substituted. Sources: meingpt:meingpt:billing-rev2.
  • unknown_parts Which costs could not be priced? [partial]: Business eligibility for200/1000/5000 users, standard-model mapping, premium/tool use, required Governance/Outpost, rollout and Enterprise services remain unknown. No progressive-platform amount is mixed into the Business floor. Sources: meingpt:meingpt:billing-rev2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.

VEN-03 Evaluation access

Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval.

LibreChat

Agent cross-checked Support: supported

Customers can self-install without licence payment; the public demo is an evaluation-only alternative.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server, LibreChat public evaluation demo; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

  • free_tier Is there a free tier for business use? [supported]: MIT self-installation permits organizational use without a software licence fee. Sources: librechat:librechat:license.
  • self_serve_trial Is a self-serve business trial available? [supported]: Self-installation has no trial clock or software card requirement; the free hosted Demo can be tried separately under its terms. Sources: librechat:librechat:local, librechat:librechat:demo.
  • trial_scope Do trials include SSO, connectors and admin features? [supported]: Self-installed instances can configure SSO, Agents, file retrieval and administration with their own service accounts. It is not evidence that every experimental add-on is enabled by default. Sources: librechat:librechat:auth, librechat:librechat:agents, librechat:librechat:rag.
  • sales_gate Does meaningful evaluation require sales contact? [supported]: The documented Docker install does not require sales approval; optional third-party services have separate account requirements. Sources: librechat:librechat:local, librechat:librechat:firstchat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:local, librechat:librechat:demo, librechat:librechat:auth, librechat:librechat:agents, librechat:librechat:rag, librechat:librechat:firstchat.

meinGPT

Agent cross-checked Support: partial

A self-serve 10-day trial exists, while several enterprise features still need enablement.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • free_tier: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace.
  • trial_scope: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed.
  • sales_gate: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made.
  • free_tier Is there a free tier for business use? [partial]: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace. Sources: meingpt:meingpt:billing.
  • self_serve_trial Is a self-serve business trial available? [supported]: 10 days, EUR 5 after phone verification, no payment details or automatic paid conversion, up to ten emailed invitees. Sources: meingpt:meingpt:billing.
  • trial_scope Do trials include SSO, connectors and admin features? [partial]: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed. Sources: meingpt:meingpt:billing.
  • sales_gate Does meaningful evaluation require sales contact? [partial]: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made. Sources: meingpt:meingpt:billing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:billing.

VEN-04 Contract terms and pricing transparency

Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint.

LibreChat

Agent cross-checked Support: partial

The MIT licence has no seat or contract-term subscription; optional service contracts are outside that licence.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • cancellation: An operator can stop running the application; this does not cancel its separately purchased cloud/model services or establish deletion of all copies.
  • local_invoicing: Can it be invoiced in CHF or EUR from a European entity? CHF/EUR commercial invoicing from a European entity was not established for optional project services.
  • transparency_class: Source licensing is transparent; a complete all-in hosted/support/inference tariff is not included in this self-hosted offer.
  • minimum_commitment What seat or spend minimum applies? [supported]: The MIT permission grant has no user-count or spending minimum for software use. Sources: librechat:librechat:license.
  • contract_length What contract lengths are offered? [supported]: There is no monthly/annual licence subscription in the MIT permission grant. External hosting/API contracts are separate. Sources: librechat:librechat:license.
  • cancellation How can the contract be cancelled or reduced? [partial]: An operator can stop running the application; this does not cancel its separately purchased cloud/model services or establish deletion of all copies. Sources: librechat:librechat:license, librechat:librechat:local.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [unknown]: local_invoicing: Can it be invoiced in CHF or EUR from a European entity? CHF/EUR commercial invoicing from a European entity was not established for optional project services.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [partial]: Source licensing is transparent; a complete all-in hosted/support/inference tariff is not included in this self-hosted offer. Sources: librechat:librechat:license, librechat:librechat:firstchat.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:local, librechat:librechat:firstchat.

meinGPT

Agent cross-checked Support: partial

Public price fields and German contract defaults exist; customer-specific terms and CHF invoicing remain open.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • minimum_commitment: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated.
  • local_invoicing: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed.
  • transparency_class: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs.
  • minimum_commitment What seat or spend minimum applies? [partial]: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated. Sources: meingpt:meingpt:prices.
  • contract_length What contract lengths are offered? [supported]: Public calculator has annual/monthly options; terms default to one year absent another agreement. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms.
  • cancellation How can the contract be cancelled or reduced? [supported]: Absent other terms, three months before term-end, text/email or admin cancellation; downgrades/user reductions effective following month, no current-month refund. Price changes require the stated notice/consent procedure. Sources: meingpt:meingpt:terms.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [partial]: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed. Sources: meingpt:meingpt:terms.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs. Sources: meingpt:meingpt:prices, meingpt:meingpt:billing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms, meingpt:meingpt:billing.

VEN-05 Source licence

Judgment rule: Record licence per component (client, server, connectors, hosted extensions) and revision. Distinguish OSI open source, source-available with restrictions (branding clauses, user caps), and closed. Repository visibility is not a licence classification. Licences change between releases: record the current terms, and never carry a fork's historical licence over to the upstream product or the reverse.

LibreChat

Agent cross-checked Support: partial

The pinned main repository is MIT licensed; no user-count or product-branding clause appears in that licence.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • enterprise_features_closed: The project documents a separate preview admin panel and optional code services. A closed enterprise-edition boundary for the main repository was not established.
  • licence_type Which licence applies to each component? [supported]: The main client/server repository at v0.8.8 is MIT. Separate Code Interpreter, admin-panel, connector or hosted-service components need their own licence review. Sources: librechat:librechat:license.
  • branding_restrictions Do licence terms restrict branding or user counts? [supported]: The MIT grant permits use/modification/distribution subject to retaining its copyright and permission notice; it includes no 50-user cap or mandatory UI branding clause. Sources: librechat:librechat:license.
  • enterprise_features_closed Are enterprise features in a separate closed edition? [partial]: The project documents a separate preview admin panel and optional code services. A closed enterprise-edition boundary for the main repository was not established. Sources: librechat:librechat:admin, librechat:librechat:code, librechat:librechat:license.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:admin, librechat:librechat:code.

meinGPT

Agent cross-checked Support: partial

The public AGB establish a commercial subscription/rental use licence with contract-limited rights. Public component source licences and a distinct enterprise source-edition mapping remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • Contractual service-use rights do not establish the licence of every server/client/connector dependency.
  • No public implementation repository or enterprise source-edition map was identified.
  • licence_type Which licence applies to each component? [partial]: SelectCode AGB describe the software as a subscription/rental and grant a non-exclusive use right limited to the contract term. Public display, adaptation, translation and decompilation of the software are restricted subject to statutory rights. This establishes the commercial service-use licence; a client/server/connector source-licence inventory and current implementation revision remain unpublished. Sources: meingpt:meingpt:terms-20261026.
  • branding_restrictions Do licence terms restrict branding or user counts? [partial]: AGB require purchased licences for majority-owned affiliates and give no independent right to sublicense or transfer usage rights. They restrict adapting the software. A numerical user cap or a component-specific branding licence is not established by these clauses. Sources: meingpt:meingpt:terms-20261026.
  • enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. The public commercial terms describe rented software, but no public client/server/connector source licence or current repository revision was located. Repository visibility was not treated as a licence. Rechecked 2026-10-26 in Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. Official links and targeted first-party searches yielded no further plan-scoped specification for the remaining atom.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: meingpt:meingpt:terms-20261026.

VEN-06 Data export and exit

Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable.

LibreChat

Agent cross-checked Support: partial

Users can export conversations in machine-readable formats; organization-wide Agent/knowledge exit completeness remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • chat_export: Pinned client code exports a user-selected conversation, including optional branches/options. A documented admin bulk export of every user’s chats was not established.
  • assistant_export: Beta management APIs expose Agent/Skill objects, but a reusable complete assistant/prompt export fixture was not verified.
  • knowledge_export: Can knowledge bases and their sources be exported? No admin exit fixture, knowledge-source/index portability test or commercial post-termination retrieval window was verified; infrastructure backups are operator-owned.
  • post_termination_window: How long can data be retrieved after termination? No admin exit fixture, knowledge-source/index portability test or commercial post-termination retrieval window was verified; infrastructure backups are operator-owned.
  • chat_export Can admins export all chats? [partial]: Pinned client code exports a user-selected conversation, including optional branches/options. A documented admin bulk export of every user’s chats was not established. Sources: librechat:librechat:export-pin.
  • assistant_export Can assistants and prompts be exported in a reusable format? [partial]: Beta management APIs expose Agent/Skill objects, but a reusable complete assistant/prompt export fixture was not verified. Sources: librechat:librechat:api.
  • knowledge_export Can knowledge bases and their sources be exported? [unknown]: knowledge_export: Can knowledge bases and their sources be exported? No admin exit fixture, knowledge-source/index portability test or commercial post-termination retrieval window was verified; infrastructure backups are operator-owned.
  • export_format Are formats documented and machine-readable? [supported]: Conversation export code supports JSON, CSV, Markdown and text. This establishes format availability, not complete organization-data portability. Sources: librechat:librechat:export-pin.
  • post_termination_window How long can data be retrieved after termination? [unknown]: post_termination_window: How long can data be retrieved after termination? No admin exit fixture, knowledge-source/index portability test or commercial post-termination retrieval window was verified; infrastructure backups are operator-owned.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:export-pin, librechat:librechat:api.

meinGPT

Agent cross-checked Support: partial

Individual downloads exist but a bulk chat export is explicitly unavailable.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • chat_export: Security FAQ explicitly says there is currently no function to export all chats at once.
  • export_format: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export.
  • post_termination_window: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it.
  • Unverified assistant_export, knowledge_export: No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run.
  • chat_export Can admins export all chats? [unsupported]: Security FAQ explicitly says there is currently no function to export all chats at once. Sources: meingpt:meingpt:security.
  • assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run.
  • knowledge_export Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run.
  • export_format Are formats documented and machine-readable? [partial]: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export. Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export.
  • post_termination_window How long can data be retrieved after termination? [partial]: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it. Sources: meingpt:meingpt:terms, meingpt:meingpt:dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export, meingpt:meingpt:terms, meingpt:meingpt:dpa.

VEN-07 Support and service levels

Judgment rule: Record support channels, languages (German, French, Italian), hours and time zone, local or regional presence, documented response times, uptime SLA and credits, public status page and incident history. Popularity is not a reliability score.

LibreChat

Agent cross-checked Support: partial

Public project/community channels are available; a binding business support SLA was not established.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • support_channels: Public GitHub issue reporting and community channels are documented; a supported enterprise channel/response-time matrix was not established for MIT self-hosting.
  • support_languages: Is support available in German, French or Italian? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass.
  • regional_presence: Is there a DACH or Swiss entity, team or partner? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass.
  • uptime_sla: Is there an uptime SLA with credits? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass.
  • status_page: Is there a public status page with history? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass.
  • support_channels Which support channels are available on each plan? [partial]: Public GitHub issue reporting and community channels are documented; a supported enterprise channel/response-time matrix was not established for MIT self-hosting. Sources: librechat:librechat:logging, librechat:librechat:firstchat.
  • support_languages Is support available in German, French or Italian? [unknown]: support_languages: Is support available in German, French or Italian? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [unknown]: regional_presence: Is there a DACH or Swiss entity, team or partner? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass.
  • uptime_sla Is there an uptime SLA with credits? [unknown]: uptime_sla: Is there an uptime SLA with credits? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass.
  • status_page Is there a public status page with history? [unknown]: status_page: Is there a public status page with history? No DE/FR/IT support coverage, CH/DACH legal/partner presence, priced uptime credits or product-service incident-history contract was verified in the public docs, site and release pass.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:logging, librechat:librechat:firstchat.

meinGPT

Agent cross-checked Support: partial

German vendor support and a public incident history are documented; an uptime credit schedule was not found.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • support_channels: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated.
  • Unverified support_languages, uptime_sla: Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage.
  • support_channels Which support channels are available on each plan? [partial]: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated. Sources: meingpt:meingpt:terms.
  • support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [supported]: SelectCode GmbH contracts from Unterhaching, Germany. Sources: meingpt:meingpt:terms.
  • uptime_sla Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage.
  • status_page Is there a public status page with history? [supported]: Public status.meingpt.com lists the platform and historical incidents; uptime is not an SLA. Sources: meingpt:meingpt:status.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:status.

VEN-08 Onboarding, training and adoption

Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings.

LibreChat

Agent cross-checked Support: partial

Self-hosting and Agent use have public setup guides; vendor-led training/adoption packages were not verified.

Availability: generally-available · Delivery: native
Scope: surfaces=Customer-operated web application and server; version=Public documentation retrieved 2026-10-21; inspected source v0.8.8 / e8f3be08623663d4ad7f7241e693c94469b63bb0; plan=MIT customer-operated LibreChat; optional separately deployed services identified per answer; add_ons=none stated; deployment_mode=on-premise; region=Customer-selected infrastructure; model, OCR, search, observability and support services separately scoped; os=not specified.

Limitations

  • onboarding_service: Is guided onboarding included? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site.
  • user_training: Is end-user training offered, in which languages? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site.
  • use_case_library: The Agent and setup guides include examples and tutorials; a role-based enterprise training/use-case program was not established.
  • adoption_programme: Is there a champion or adoption programme? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site.
  • service_cost: Which services cost extra? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site.
  • onboarding_service Is guided onboarding included? [unknown]: onboarding_service: Is guided onboarding included? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site.
  • user_training Is end-user training offered, in which languages? [unknown]: user_training: Is end-user training offered, in which languages? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site.
  • use_case_library Are role-based use cases and templates provided? [partial]: The Agent and setup guides include examples and tutorials; a role-based enterprise training/use-case program was not established. Sources: librechat:librechat:agents, librechat:librechat:firstchat.
  • adoption_programme Is there a champion or adoption programme? [unknown]: adoption_programme: Is there a champion or adoption programme? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site.
  • service_cost Which services cost extra? [unknown]: service_cost: Which services cost extra? No included guided rollout, local-language end-user training, champion programme, change-management service or professional-service price list was established from the official documentation and site.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:firstchat.

meinGPT

Agent cross-checked Support: partial

Learning paths and business examples are built in; personal rollout services are quote-based.

Availability: generally-available · Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations

  • onboarding_service: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised.
  • user_training: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated.
  • adoption_programme: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found.
  • onboarding_service Is guided onboarding included? [partial]: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised. Sources: meingpt:meingpt:prices.
  • user_training Is end-user training offered, in which languages? [partial]: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated. Sources: meingpt:meingpt:academy, meingpt:meingpt:audit.
  • use_case_library Are role-based use cases and templates provided? [supported]: Role/department personalization and business-use-case material are documented. Sources: meingpt:meingpt:academy.
  • adoption_programme Is there a champion or adoption programme? [partial]: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found. Sources: meingpt:meingpt:billing.
  • service_cost Which services cost extra? [supported]: Personal guidance is quote-only; terms bill services by time/person-days or individually agreed fixed price. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:prices, meingpt:meingpt:academy, meingpt:meingpt:audit, meingpt:meingpt:billing, meingpt:meingpt:terms.

Sources

  1. Custom endpoints librechat:librechat:custom

    Operators configure compatible endpoints and customer-held keys, including local and hosted services.

    Endpoint setup; API key; base URL; model list · documented · Source date not stated · Retrieved 2026-10-21

  2. Azure OpenAI configuration librechat:librechat:azure

    Azure OpenAI uses customer deployment groups, instance names and credentials.

    Deployment groups; API credentials · documented · Source date not stated · Retrieved 2026-10-21

  3. AWS Bedrock object structure librechat:librechat:bedrock

    Bedrock routes use customer AWS configuration and region selection.

    Region; credentials; model selection · documented · Source date not stated · Retrieved 2026-10-21

  4. Anthropic Vertex AI configuration librechat:librechat:vertex

    Claude can run through customer Google Vertex AI credentials and regions.

    Project and region configuration · documented · Source date not stated · Retrieved 2026-10-21

  5. Model specifications librechat:librechat:modelspec

    Administrators can enforce configured model presets and defaults; available endpoints still depend on customer credentials.

    enforce; preset; modelSelect; addedEndpoints · documented · Source date not stated · Retrieved 2026-10-21

  6. Agents librechat:librechat:agents

    Agents combine instructions, models, files, tools, skills and sharing permissions, with visible execution and configurable approval.

    Builder; Capabilities; Version history; Sharing; Activity; tool approval · documented · Source date not stated · Retrieved 2026-10-21

  7. OCR for documents librechat:librechat:ocr

    OCR can augment text extraction, or files can be sent to compatible provider APIs; format and model limitations remain.

    File Context; Upload as Text; Optional OCR; Limitations · documented · Source date not stated · Retrieved 2026-10-21

  8. LibreChat v0.8.8 release librechat:librechat:releases

    The stable release documents agent controls, current model updates and explicitly experimental schedules/workspaces and beta Agents API.

    Highlights, 2026-10-01 · documented · Source date 2026-10-01 · Retrieved 2026-10-21

  9. Alle Modelle | MeinGPT Docs meingpt:meingpt:rates

    Public EUR token and service rates include GPT-5 mini at EUR 0.30 input and EUR 2.40 output per million tokens.

    Text-generation, translation, images and other-functions tables · documented · Source date not stated · Retrieved 2026-10-21

  10. Modelle | MeinGPT Docs meingpt:meingpt:models-rev2

    Current documentation lists selectable non-Meta model families, per-chat selection and context-length routing; the lifecycle table contains no current selectable Meta model.

    Model picker, model tables and own-LLM-key FAQ · documented · Source date not stated · Retrieved 2026-10-21

  11. Modell-Lifecycle | MeinGPT Docs meingpt:meingpt:lifecycle-rev2

    Active models, future retirement dates and automatic replacement rules are published.

    Phases, notice period and current-model table · documented · Source date not stated · Retrieved 2026-10-21

  12. Modell-Lifecycle | MeinGPT Docs meingpt:meingpt:lifecycle

    Active models, future retirement dates and automatic replacement rules are published.

    Phases, notice period and current-model table · documented · Source date not stated · Retrieved 2026-10-21

  13. Was wir zuletzt released haben | MeinGPT | KI-Use-Case-Plattform für den Mittelstand meingpt:meingpt:changes

    Release 2.67.0 on 18 October adds Gemini 4 Argon, retires named models and adds configurable deletion periods.

    v2.67.0, model retirement and deletion periods · documented · Source date 2026-10-18 · Retrieved 2026-10-21

  14. Your first chat librechat:librechat:firstchat

    LibreChat ships without a model key; the public demo is for evaluation rather than private or durable data.

    Software you host yourself; endpoint credentials; public demo · documented · Source date not stated · Retrieved 2026-10-21

  15. Code Interpreter API librechat:librechat:code

    A separate code execution service supports multiple languages and downloadable generated files; stateful/attached modes are experimental.

    Setup; self-hosted service; workspace permissions; generated files · documented · Source date not stated · Retrieved 2026-10-21

  16. LibreChat v0.8.8 MIT licence librechat:librechat:license

    The pinned repository is MIT licensed with copyright/permission notice preservation and an as-is disclaimer.

    LICENSE, permission grant and notice requirement · documented · Source date not stated · Retrieved 2026-10-21

  17. Modelle | MeinGPT Docs meingpt:meingpt:models

    Users choose models per chat; automatic selection is based on context length; customer LLM keys and endpoints cannot be added.

    Model picker, model tables and own-LLM-key FAQ · documented · Source date not stated · Retrieved 2026-10-21

  18. Übersetzer | MeinGPT Docs meingpt:meingpt:translation

    Default text translation uses Google Cloud Translate and document translation uses DeepL through EU endpoints; glossaries and layout preservation are documented.

    Engine/hosting, formats and glossary management · documented · Source date not stated · Retrieved 2026-10-21

  19. RAG API configuration librechat:librechat:ragcfg

    OpenAI, Hugging Face and Ollama embedding configurations are documented; image choice affects local embedding support.

    Embedding providers; lite image; full image · documented · Source date not stated · Retrieved 2026-10-21

  20. Subdienstleister & Verarbeitungsregionen | MeinGPT meingpt:meingpt:subprocessors

    The register separates Germany platform storage, France backups and provider-specific EU inference regions.

    Register by function and processing region · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  21. Granular access control librechat:librechat:access

    Roles, groups and resource ACLs govern features and sharing, with Entra groups synchronized at sign-in.

    Feature permissions; Resource ACLs; System grants; Groups · documented · Source date not stated · Retrieved 2026-10-21

  22. LibreChat Admin Panel librechat:librechat:admin

    A separate browser management panel is available for testing and uses the underlying LibreChat admin APIs.

    Status Preview; separate service; admin APIs · documented · Source date not stated · Retrieved 2026-10-21

  23. Balance configuration librechat:librechat:balance

    Optional token-credit balances initialize and refill user credits; tracking is disabled by default.

    enabled; startBalance; refill configuration · documented · Source date not stated · Retrieved 2026-10-21

  24. Automated moderation librechat:librechat:mod

    Moderation scores abusive login/registration/message activity and may ban users; it is not a documented content DLP classifier.

    Violation scoring and limits · documented · Source date not stated · Retrieved 2026-10-21

  25. LibreChat balance admission implementation librechat:librechat:balance-pin

    The pinned middleware reserves user credits and throws a TOKEN_BALANCE error when the reservation cannot be admitted.

    packages/api/src/middleware/checkBalance.ts, checkBalance · source-inspected · Source date not stated · Retrieved 2026-10-21
    Commit e8f3be08623663d4ad7f7241e693c94469b63bb0, path packages/api/src/middleware/checkBalance.ts

  26. Workspace-Konfiguration | MeinGPT Docs meingpt:meingpt:config

    Admins can restrict models by teams or people and supply workspace-wide instructions; denied API models return an error.

    Model access, default settings and additional chat context · documented · Source date not stated · Retrieved 2026-10-21

  27. Nutzungslimits | MeinGPT Docs meingpt:meingpt:limits

    Personal category budgets block new use at zero; running meeting bots can overrun limits and scheduled runs are outside personal categories.

    Usage levels, meeting limits and user consumption table · documented · Source date not stated · Retrieved 2026-10-21

  28. Einführung | MeinGPT Docs meingpt:meingpt:api

    Chat, embeddings, assistants, workflows and transcription APIs use bearer keys and published token rate limits; translation is UI-only.

    API overview, rate limits and errors · documented · Source date not stated · Retrieved 2026-10-21

  29. RAG API librechat:librechat:rag

    A separate RAG API indexes uploaded content in PostgreSQL/PGVector for retrieval.

    Architecture; document indexing; embeddings; semantic search · documented · Source date not stated · Retrieved 2026-10-21

  30. Upload files as text librechat:librechat:text

    Text upload injects extracted file content rather than relying only on vector retrieval.

    Full text extraction and context · documented · Source date not stated · Retrieved 2026-10-21

  31. File configuration librechat:librechat:filecfg

    File limits and formats are configurable by endpoint and file processing route.

    File limits; MIME patterns; provider routes · documented · Source date not stated · Retrieved 2026-10-21

  32. LibreChat spreadsheet text parser librechat:librechat:r4-spreadsheet-parser

    The built-in parser accepts XLSX/XLS/ODS and serializes each sheet as its name followed by CSV values. It does not establish preserved workbook layout, recalculated formulas or fixture accuracy.

    getParserForMimeType; excelSheetToText, lines 109-129 · source-inspected · Source date 2026-10-24 · Retrieved 2026-10-26
    Commit a378657583567310c841d652b0f6b00c83e2bd6b, path packages/api/src/files/documents/crud.ts

  33. LibreChat current Upload as Text guide librechat:librechat:r4-text-current

    The development guide lists XLSX/XLS/ODS parsing up to 15 MB and token-bounded text injection, not a formatted spreadsheet editor.

    Built-in parser; supported documents; truncation · documented · Source date not stated · Retrieved 2026-10-26

  34. Datenquellen & RAG | MeinGPT Docs meingpt:meingpt:pools

    Cloud pools index six source types in Germany, refresh every 15 minutes and share a 300 GB raw-data budget.

    Cloud-source table, connector comparison and normal-chat search · documented · Source date not stated · Retrieved 2026-10-21

  35. Eingabefeld | MeinGPT Docs meingpt:meingpt:chat

    Chat has stop, model choice, file upload, dictation and sharing links, with 50 files and 50 MB per non-image file.

    Input controls, file limits, dictation and sharing · documented · Source date not stated · Retrieved 2026-10-21

  36. Datenfluss bei MeinGPT Chats | MeinGPT Docs meingpt:meingpt:flow

    Chat deletion archives content; prompts have provider-dependent processing, and platform data stays until instructed deletion.

    Processing steps, providers and deletion rights · documented · Source date not stated · Retrieved 2026-10-21

  37. Code-Sandbox | MeinGPT Docs meingpt:meingpt:sandbox

    Python/JavaScript analysis and Office generation run in an isolated Unikraft Cloud VM in Frankfurt, including for on-premise customers.

    Execution flow, hosting, lifetime and limitations · documented · Source date not stated · Retrieved 2026-10-21

  38. Projects librechat:librechat:projects

    Projects persist files and instructions across a user’s chats but cannot be shared or transferred.

    Availability; personal scope; files and instructions · documented · Source date not stated · Retrieved 2026-10-21

  39. Assistenten | MeinGPT Docs meingpt:meingpt:assistants

    Assistants combine model, instructions, files, pools, connectors, tools and memory.

    Creation guide and editor sections · documented · Source date not stated · Retrieved 2026-10-21

  40. Projekte | MeinGPT Docs meingpt:meingpt:projects

    Projects share instructions and workflows while each member keeps a private chat history.

    Collaboration, roles and deletion · documented · Source date not stated · Retrieved 2026-10-21

  41. SharePoint and OneDrive integration librechat:librechat:sharepoint

    The Microsoft file picker uses Entra token reuse and delegated on-behalf-of downloads to attach files.

    Prerequisites; delegated permissions; admin consent · documented · Source date not stated · Retrieved 2026-10-21

  42. MCP librechat:librechat:mcp

    MCP servers can be configured through YAML or the permission-gated UI, including per-user OAuth.

    YAML/UI setup; authentication; ownership and selection · documented · Source date not stated · Retrieved 2026-10-21

  43. MCP server configuration librechat:librechat:mcpcfg

    Configuration includes stdio, SSE and Streamable HTTP transports and server-specific credentials.

    Transport examples; headers; OAuth · documented · Source date not stated · Retrieved 2026-10-21

  44. Microsoft 365 | MeinGPT Docs meingpt:meingpt:m365

    Separate Outlook, Teams, SharePoint and OneDrive connectors run under user OAuth; Outlook can write, the other three read.

    Overview, setup, tenant consent and permission model · documented · Source date not stated · Retrieved 2026-10-21

  45. Sucheinstellungen am Datenpool | MeinGPT Docs meingpt:meingpt:pool-controls

    Source-permission import is off by default and request-enabled for SharePoint and Drive only; answers always show sources.

    Settings table and source-permission section · documented · Source date not stated · Retrieved 2026-10-21

  46. LibreChat Docker service configuration librechat:librechat:compose-pin

    The pinned example runs a MongoDB primary store and a separate PGVector/RAG service with customer-mounted data.

    docker-compose.yml, api/mongodb/vectordb/rag_api services · source-inspected · Source date not stated · Retrieved 2026-10-21
    Commit e8f3be08623663d4ad7f7241e693c94469b63bb0, path docker-compose.yml

  47. User memory librechat:librechat:memory

    Configured user memory stores cross-chat key/value context with user editing controls; it does not index all past chats.

    Key/value store; controls; disabled by default · documented · Source date not stated · Retrieved 2026-10-21

  48. Memory | MeinGPT Docs meingpt:meingpt:memory

    Memory persists per user across enabled assistants; users can inspect/delete it and admins can disable the tool.

    How memory works, management and admin controls · documented · Source date not stated · Retrieved 2026-10-21

  49. Präferenzen | MeinGPT Docs meingpt:meingpt:preferences

    Users can set persistent system instructions and a platform-language preference.

    Chat settings and appearance · documented · Source date not stated · Retrieved 2026-10-21

  50. Rollen & Zugriffsmodell | MeinGPT Docs meingpt:meingpt:roles

    Admin, Member and Viewer roles differ in settings access and seat use; admins see all team-shared assets.

    Role table, admin exception and support visibility · documented · Source date not stated · Retrieved 2026-10-21

  51. Berechtigungen | MeinGPT Docs meingpt:meingpt:permissions

    Support-enabled permissions control creation, sharing and app use per person or team.

    Availability, permissions table and app restrictions · documented · Source date not stated · Retrieved 2026-10-21

  52. Prompt-Bibliothek | MeinGPT Docs meingpt:meingpt:prompts

    Saved prompt folders have private, workspace or department visibility.

    Core functions, visibility and sharing · documented · Source date not stated · Retrieved 2026-10-21

  53. Image generation and editing librechat:librechat:images

    Agents can use configured image tools for generation/editing; provider credentials and model parameters are separate.

    OpenAI Image Tools; provider setup; admin configuration · documented · Source date not stated · Retrieved 2026-10-21

  54. Web search librechat:librechat:web

    Search can use Serper, SearXNG, Tavily or Keenable, with independently configured scraping and optional reranking.

    Provider, scraper and reranker configuration · documented · Source date not stated · Retrieved 2026-10-21

  55. Websuche | MeinGPT Docs meingpt:meingpt:web

    Linkup powers chat search and a multi-step Deep Research app with cited sources.

    Three routes, query creation, Linkup and research app · documented · Source date not stated · Retrieved 2026-10-21

  56. Scheduled Chats librechat:librechat:schedule

    Opt-in experimental schedules execute saved Agents with cron/time zones and recheck access and balance before running.

    Experimental and disabled by default; runtime and permissions · documented · Source date not stated · Retrieved 2026-10-21

  57. Agents API beta librechat:librechat:api

    The beta API exposes chat/Responses inference, Agent/Skill management and authenticated event delivery.

    Inference; management; Agent Events; authentication · documented · Source date not stated · Retrieved 2026-10-21

  58. Workflows erstellen und ausführen | MeinGPT Docs meingpt:meingpt:workflows

    Project workflows support multiple models, variables, documents and downloadable Office, PDF or JSON output.

    Workflow editor and output format · documented · Source date not stated · Retrieved 2026-10-21

  59. Geplante Aufgaben | MeinGPT Docs meingpt:meingpt:scheduled

    Scheduled tasks are support-enabled beta with schedule, webhook and email triggers under the creator account.

    Beta availability, triggers and execution account · documented · Source date not stated · Retrieved 2026-10-21

  60. Tool-Zugriffsrichtlinien | MeinGPT Docs meingpt:meingpt:tools

    Tool methods are intersected across admin and assistant policies; there is no interactive per-action permission dialog.

    Security warning and four enforcement layers · documented · Source date not stated · Retrieved 2026-10-21

  61. Compliance Controls | MeinGPT Docs meingpt:meingpt:audit

    Administrative settings logs exclude chat contents and are retained indefinitely; Governance Outpost search records are retained 90 days.

    Core controls and Outpost search log · documented · Source date not stated · Retrieved 2026-10-21

  62. Outlook Add-in | MeinGPT Docs meingpt:meingpt:outlook

    The Outlook add-in requires Enterprise API enablement and a personal API key and works in the received-mail reading view.

    Prerequisites, supported clients and central deployment · documented · Source date not stated · Retrieved 2026-10-21

  63. Temporary chat and data retention librechat:librechat:retention

    Operators configure expiry for chats/messages/files/shared links; normal chats do not expire by default and memories are excluded.

    Default 30-day temporary retention; all/ephemeral; deadlines; memories · documented · Source date not stated · Retrieved 2026-10-21

  64. Admin Insights librechat:librechat:insights

    Insights reports persisted MongoDB activity and identifiable recent conversations; it is not monetary billing analytics.

    Opt-in; capabilities; metrics; tenant scope · documented · Source date not stated · Retrieved 2026-10-21

  65. Docker installation librechat:librechat:local

    Docker self-installation runs LibreChat with its configured service dependencies.

    Installation; configuration; updating · documented · Source date not stated · Retrieved 2026-10-21

  66. Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand meingpt:meingpt:terms

    German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination.

    Sections 1a, 2, 3, 5 and final provisions · documented · Source date not stated · Retrieved 2026-10-21

  67. Bilder Generieren | MeinGPT Docs meingpt:meingpt:images

    The image app supports FLUX, GPT Image and Gemini image models with reference images and downloadable files.

    Model list, references and output management · documented · Source date not stated · Retrieved 2026-10-21

  68. Bildmodelle verwalten | MeinGPT Docs meingpt:meingpt:image-admin

    Admins enable image models and set a default; the table distinguishes manufacturer, host and EU/global processing.

    Image-model controls and complete table · documented · Source date not stated · Retrieved 2026-10-21

  69. Speech configuration librechat:librechat:speech

    Administrators configure audio provider engines and models separately from text generation.

    Speech-to-text and text-to-speech engines · documented · Source date not stated · Retrieved 2026-10-21

  70. LibreChat conversation-mode speech settings librechat:librechat:speech-conversation-r2

    Conversation mode chains transcription, auto-send and TTS playback for hands-free turns after microphone activation; engines and audio routing are separately configured.

    Speech Tab: conversationMode, autoTranscribeAudio, autoSendText, automaticPlayback; engine and allowedAddresses settings · documented · Source date not stated · Retrieved 2026-10-21

  71. Meetings | MeinGPT Docs meingpt:meingpt:meeting

    Recordings and transcripts become searchable meeting notes; Hetzner, Gladia and Vertex EU form the processing path.

    Formats/limits, data flow and prices · documented · Source date not stated · Retrieved 2026-10-21

  72. Artifacts librechat:librechat:artifacts

    Artifacts render generated React, HTML and Mermaid content in the chat interface.

    React, HTML and Mermaid previews · documented · Source date not stated · Retrieved 2026-10-21

  73. Shareable links librechat:librechat:share

    Shared links publish a transcript branch and optional file snapshots independently of the owner’s live file ACL.

    Authentication defaults; file snapshots; continuation · documented · Source date not stated · Retrieved 2026-10-21

  74. LibreChat locale registration librechat:librechat:i18n-pin

    The pinned client registers English, German, French and Italian translations among its supported locales.

    client/src/locales/i18n.ts, language resources · source-inspected · Source date not stated · Retrieved 2026-10-21
    Commit e8f3be08623663d4ad7f7241e693c94469b63bb0, path client/src/locales/i18n.ts

  75. Authentication system librechat:librechat:auth

    Local/LDAP accounts can be required to use TOTP; federated MFA belongs to the identity provider and account creation/deletion scripts are documented.

    Required two-factor authentication; Registration; User scripts · documented · Source date not stated · Retrieved 2026-10-21

  76. OAuth2 and OIDC librechat:librechat:openid

    LibreChat documents OAuth2/OIDC providers including Microsoft Entra, Google, Keycloak and Auth0.

    Supported providers; setup · documented · Source date not stated · Retrieved 2026-10-21

  77. SAML authentication librechat:librechat:saml

    SAML is a documented authentication option for the self-hosted application.

    Overview and requirements · documented · Source date not stated · Retrieved 2026-10-21

  78. Azure Entra authentication librechat:librechat:entra

    Entra OIDC supports group-based admission and Graph integration using configured scopes and token reuse.

    Group claims; token reuse; Microsoft Graph integration · documented · Source date not stated · Retrieved 2026-10-21

  79. prices meingpt:meingpt:prices

    The public calculator uses marginal seat tiers plus model consumption and optional Governance and Outpost fees.

    Annual price tiers, included functions, add-ons and model-cost sections · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  80. Access & Login Security | MeinGPT Docs meingpt:meingpt:sso

    OIDC, Google and Microsoft login, verified domains and additive Entra group synchronization are documented; SAML is explicitly excluded.

    Own identity provider, authentication methods and Entra synchronization · documented · Source date not stated · Retrieved 2026-10-21

  81. Entra ID SCIM-Provisionierung | MeinGPT Docs meingpt:meingpt:scim

    SCIM v1 provisions users only; deactivated accounts retain data and release their seat.

    SCIM versus SSO, prerequisites, effects and seat assignment · documented · Source date not stated · Retrieved 2026-10-21

  82. Token usage librechat:librechat:tokens

    Usage and estimated costs use recorded tokens and configured provider rates; transactions are distinct from balance enforcement.

    Context cost; transactions; per-endpoint token rates · documented · Source date not stated · Retrieved 2026-10-21

  83. KI-Cockpit | MeinGPT Docs meingpt:meingpt:analytics

    Adoption and cost reports include user, model, API/platform and team breakdowns with CSV and ID-based anonymization.

    Typical metrics, user/team costs and knowledge search · documented · Source date not stated · Retrieved 2026-10-21

  84. Logging librechat:librechat:logging

    Backend operational logs are written to customer files and can feed external tools; the guide describes 14-day rotation rather than a compliance archive.

    Error/debug logs; rotation; external tools · documented · Source date not stated · Retrieved 2026-10-21

  85. Änderungsprotokoll exportieren | MeinGPT Docs meingpt:meingpt:audit-export

    Admins export filtered administrative changes as CSV or JSON, capped at 10000 entries, 20 MiB and two minutes.

    Export procedure, fields and limits · documented · Source date not stated · Retrieved 2026-10-21

  86. LibreChat development content-filter configuration librechat:librechat:r4-content-filter

    Opt-in base-YAML policies inspect selected message/file content; block and audit differ from limited Agent text redaction. This is development documentation, not a hosted DLP assurance.

    Source-Aware Filters; Pattern Configuration; Redaction; File Fields · documented · Source date not stated · Retrieved 2026-10-26

  87. LibreChat content-inspection runtime librechat:librechat:r4-pii-runtime

    Source-aware configured inspection executes in the LibreChat API. Missing policy disables that scope; configured actions and fields bound inspection.

    createConfiguredContentInspector; source rule configuration · source-inspected · Source date 2026-10-24 · Retrieved 2026-10-26
    Commit a378657583567310c841d652b0f6b00c83e2bd6b, path packages/api/src/protection/runtime.ts

  88. LibreChat pattern detector librechat:librechat:r4-patterns

    Default starter patterns detect credential-shaped tokens/headers. Operator custom patterns use bounded regular expressions; a generic comprehensive PII classifier is not established.

    STARTER_PATTERNS; configured RE2JS rules · source-inspected · Source date 2026-10-24 · Retrieved 2026-10-26
    Commit a378657583567310c841d652b0f6b00c83e2bd6b, path packages/api/src/protection/detectors/pattern.ts

  89. LibreChat private text submission librechat:librechat:r4-private-submission

    The private text ingress permits configured redaction only on eligible fresh interactive Agent text. Original content is encrypted; edit/resume/file paths do not gain blanket redaction.

    createPrivateTextIngress; fresh Agent text and clientRequestId checks · source-inspected · Source date 2026-10-24 · Retrieved 2026-10-26
    Commit a378657583567310c841d652b0f6b00c83e2bd6b, path packages/api/src/protection/private/submission.ts

  90. LibreChat API content-filter middleware librechat:librechat:r4-filter-middleware

    The server middleware applies configured inspection and rejects blocked/uninspectable requests with HTTP 400. No deployment or detection fixture was run.

    createMessageFilterPii; contentFilterBlockResponse; uninspectable response · source-inspected · Source date 2026-10-24 · Retrieved 2026-10-26
    Commit a378657583567310c841d652b0f6b00c83e2bd6b, path packages/api/src/middleware/messageFilterPii.ts

  91. LibreChat config v1.3.18 changelog librechat:librechat:r4-config-1318

    Dated development config changes add limited Agent text redaction and ephemeral retention mode. These are not a promise of universal redaction or a vendor zero-retention contract.

    October 22, 2026; opt-in PII redaction; retention mode · documented · Source date 2026-10-22 · Retrieved 2026-10-26

  92. Interface configuration librechat:librechat:interface

    Administrators configure UI feature permissions and usage terms in the self-hosted deployment.

    Feature permissions; custom welcome and terms · documented · Source date not stated · Retrieved 2026-10-21

  93. Remote hosting librechat:librechat:remote

    The application can be deployed on customer-selected remote servers with operator-managed security.

    Hosting options; security considerations · documented · Source date not stated · Retrieved 2026-10-21

  94. Auftragsverarbeitungsvertrag | MeinGPT | KI-Use-Case-Plattform für den Mittelstand meingpt:meingpt:dpa-page

    DPA 2.0.1 dated 24 September 2026 needs signature or recorded electronic acceptance; existing customers retain their agreed version.

    Version and effectiveness · documented · Source date 2026-09-24 · Retrieved 2026-10-21

  95. MeinGPT DPA 2.0.1 meingpt:meingpt:dpa

    The signed-form DPA prohibits training, lists conditional subprocessors, defines authority-request handling and requires return or deletion within 30 days.

    Version 2.0.1; sections 4, 5(5), 7, 9, 12, 13 and Annexes 3/4, pages 3-12 · documented · Source date 2026-09-24 · Retrieved 2026-10-21

  96. LibreChat Demo terms librechat:librechat:demo

    The free hosted Demo is offered as-is with possible data cleanups and no durable business-service guarantee.

    Evaluation scope; retention; disclaimer · documented · Source date 2026-03-12 · Retrieved 2026-10-21

  97. Personal settings librechat:librechat:settings

    Users configure interface language, audio and personal data controls.

    Language; speech; data controls · documented · Source date not stated · Retrieved 2026-10-21

  98. Sind meine Daten sicher? | MeinGPT Docs meingpt:meingpt:security

    Security documentation states TLS 1.3, AES-256, customer-managed keys on request, and no bulk chat/file export.

    Technical security, deletion and data portability · documented · Source date not stated · Retrieved 2026-10-21

  99. ClickHouse acquisition of LibreChat librechat:librechat:owner

    ClickHouse announced the acquisition of LibreChat and that Danny Avila and the team joined ClickHouse.

    Announcement, November 4, 2025 · documented · Source date 2025-11-04 · Retrieved 2026-10-21

  100. Sicherheitsnachweise & Trust Center | MeinGPT meingpt:meingpt:trust

    ISO 27001 and a 2025 SySS penetration-test certificate are listed behind email-gated access.

    Certificates, assessments and document access · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  101. LibreChat website privacy policy librechat:librechat:siteprivacy

    Website, demo and self-hosted software are distinct privacy scopes; website terms do not establish a customer deployment DPA.

    Scope and exclusions · documented · Source date not stated · Retrieved 2026-10-21

  102. LibreChat v0.8.8 message storage schema librechat:librechat:secrecy-message-pin

    The pinned Mongoose schema declares message text as a String and content as mixed fields; this source does not establish operator exclusion from live content.

    packages/data-schemas/src/schema/message.ts, text at lines 55-58 and content at lines 139-143 · source-inspected · Source date not stated · Retrieved 2026-10-21
    Commit e8f3be08623663d4ad7f7241e693c94469b63bb0, path packages/data-schemas/src/schema/message.ts

  103. LibreChat Demo privacy policy librechat:librechat:secrecy-demo-policy

    The Demo policy describes model-provider transmission and contractual processor instruction/security duties for the Demo; it does not cover a customer self-hosted deployment.

    Scope; section 4 Third-Party AI Model Providers; section 6 Data Sharing and Sub-Processors · documented · Source date 2026-03-12 · Retrieved 2026-10-21

  104. Preise für Plattform, Add-ons und KI-Nutzung | MeinGPT meingpt:meingpt:prices-rev2

    The contracted platform is offered with optional Governance and Outpost modules; local files are Early Access and local MCP/PostgreSQL Private Beta. The price calculator requires a binding individual offer.

    Feature table: Outpost release states; Governance separate agreement; calculator explicitly nonbinding · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  105. meinGPT terms: professional secrecy meingpt:meingpt:secrecy-contract-rev2

    Section12(4) itself imposes indefinite professional secrecy and text-form staff/subcontractor obligations when covered data are processed; it does not state a Governance prerequisite. A separate addendum is outside the verified base-terms finding.

    Section12(4), conditional duties for professional-secret data; no Governance prerequisite stated · documented · Source date not stated · Retrieved 2026-10-21

  106. Abrechnung verwalten | MeinGPT Docs meingpt:meingpt:billing-rev2

    Self-service Business is EUR29 per user/month excluding VAT, billed monthly, with unlimited standard-model use; premium/reasoning, API and meeting-bot use are separately metered.

    Workspace types; Business upgrade card; standard-model inclusion · documented · Source date not stated · Retrieved 2026-10-21

  107. Azure Retail Prices, Switzerland North Linux VMs librechat:librechat:cost-vm

    EUR hourly PAYG rates retrieved 2026-10-21 are 0.2226, 0.4453 and 0.8905 for D4s, D8s and D16s v5 respectively.

    Consumption; Virtual Machines Dsv5 Series; Standard_D4s_v5/D8s_v5/D16s_v5 · documented · Source date not stated · Retrieved 2026-10-21

  108. Azure Retail Prices, PostgreSQL Flexible Server librechat:librechat:cost-pg

    EUR hourly PAYG GP compute is 0.2288, 0.4576 and 0.9152 for 2/4/8 vCore; storage is EUR 0.1325 per GB-month.

    General Purpose Ddsv5 Series Compute, 2/4/8 vCore; Flex Server Storage · documented · Source date not stated · Retrieved 2026-10-21

  109. ECB euro reference rate history librechat:librechat:cost-fx

    The 2026-10-20 reference rates are EUR 1 = USD 1.1215 and CHF 0.9237.

    Cube time=2026-10-20; USD and CHF · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  110. OpenAI API pricing librechat:librechat:cost-model

    Standard gpt-6-luna API price is USD 0.10 per million input tokens and USD 0.50 per million output tokens; caching, batch and regional premiums are separate.

    Standard, short-context gpt-6-luna row · documented · Source date not stated · Retrieved 2026-10-21

  111. GPT-6 Luna model documentation librechat:librechat:cost-effort

    The model accepts reasoning effort none, the lowest documented effort, and lists the same standard text-token rates.

    Reasoning effort and text-token pricing · documented · Source date not stated · Retrieved 2026-10-21

  112. ECB historical euro reference rates, 20 October 2026 meingpt:meingpt:ecb-fx

    ECB2026-10-20 reference rates:EUR1=USD1.1215=CHF0.9237, implying USD1=EUR0.89166206.

    Cube time=2026-10-20, USD and CHF currency entries · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  113. Abrechnung verwalten | MeinGPT Docs meingpt:meingpt:billing

    A separate Business offer includes standard models; the trial lasts 10 days with EUR 5 credit and no payment details.

    Workspace types, trial differences and Business upgrade · documented · Source date not stated · Retrieved 2026-10-21

  114. Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand meingpt:meingpt:terms-20261026

    German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination.

    Sections 1a, 2, 3, 5 and final provisions · documented · Source date not stated · Retrieved 2026-10-26

  115. LibreChat conversation export implementation librechat:librechat:export-pin

    The pinned user conversation exporter supports JSON, CSV, Markdown and text, plus screenshot export.

    client/src/hooks/Conversations/useExportConversation.ts, export dispatch · source-inspected · Source date not stated · Retrieved 2026-10-21
    Commit e8f3be08623663d4ad7f7241e693c94469b63bb0, path client/src/hooks/Conversations/useExportConversation.ts

  116. status meingpt:meingpt:status

    A public service-status page exposes incident history.

    Platform component and incidents · documented · Source date not stated · Retrieved 2026-10-21

  117. Lernen & Entdecken | MeinGPT Docs meingpt:meingpt:academy

    The learning area includes guided learning paths and business use cases.

    Learning area content and personalization · documented · Source date not stated · Retrieved 2026-10-21