--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/librechat-vs-swisscom-assistant/" data_url: "https://onaihq.com/compare/agents/librechat-vs-swisscom-assistant/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # LibreChat vs Swisscom Swiss AI Assistant > 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 26 criteria with sourced findings for both products, including 26 that a second agent cross-checked for both. 48 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. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - LibreChat source checks: 2026-10-21 to 2026-10-26. - Swisscom Swiss AI Assistant source checks: 2026-10-21. - Canonical HTML: https://onaihq.com/compare/agents/librechat-vs-swisscom-assistant/ - Machine-readable JSON: https://onaihq.com/compare/agents/librechat-vs-swisscom-assistant/data.json - Methodology: https://onaihq.com/compare/agents/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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial The current offer lists a selectable catalogue of four open-model families. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Automatic routing, per-chat selection persistence and a per-model image/audio/file matrix were not documented or tested. - providers — Which model providers are available? [supported]: Named origins are OpenAI, Qwen, Mistral and Gemma. These are hosted open-model choices, not evidence of external provider API contracts. Sources: swisscom-assistant:swisscom-assistant:offer. - current_models — Which current models are selectable on this plan? [supported]: FAQ names GPT OSS 120B, Qwen3.5 397B A17B, Mistral Small 4 119B and Gemma 4 31B as current choices. Sources: swisscom-assistant:swisscom-assistant:offer. - user_choice — Can users pick the model per chat? [partial]: FAQ says the model can be chosen for the use case; per-chat switching behaviour was not observed. Sources: swisscom-assistant:swisscom-assistant:offer. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? Unknown. Automatic routing, per-chat selection persistence and a per-model image/audio/file matrix were not documented or tested. - multimodal_input — Which models accept images, audio or files? [partial]: FAQ calls Qwen3.5 multimodal; factsheet includes image analysis and audio transcription across editions. Exact per-model input routing is not documented. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:releases, librechat:librechat:modelspec, librechat:librechat:custom #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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. - own_api_keys — Can the customer use its own provider API keys? [supported]: Provider keys can be operator-supplied or user_provided, with user key controls in Settings. Sources: librechat:librechat:firstchat, librechat:librechat:custom. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [supported]: Customer Azure OpenAI deployments, AWS Bedrock region/credentials and Anthropic Vertex project/region routes are documented separately. Sources: librechat:librechat:azure, librechat:librechat:bedrock, librechat:librechat:vertex. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Operators can configure a custom compatible API URL and model list. Sources: librechat:librechat:custom. - byo_pricing — Does BYO change the licence price? [supported]: MIT repository use has no per-seat licence fee; customers separately procure provider service usage. Sources: librechat:librechat:license, librechat:librechat:firstchat. - byo_restrictions — Which features stop working with BYO? [partial]: File modalities, tools and other capabilities depend on provider/model support and optional services. A universal BYO feature-parity guarantee was not established. Sources: librechat:librechat:ocr, librechat:librechat:code. Checked 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Swisscom operates open models in Switzerland. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Customer-hosted chat/embeddings, supported serving runtimes and non-vendor-model feature parity are not documented for Swiss AI Assistant. - self_hosted_chat — Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? Unknown. Customer-hosted chat/embeddings, supported serving runtimes and non-vendor-model feature parity are not documented for Swiss AI Assistant. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. Customer-hosted chat/embeddings, supported serving runtimes and non-vendor-model feature parity are not documented for Swiss AI Assistant. - feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. Customer-hosted chat/embeddings, supported serving runtimes and non-vendor-model feature parity are not documented for Swiss AI Assistant. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [supported]: The current model FAQ and launch announcement describe open models on Swisscom Swiss AI Platform with processing in its Swiss data centres. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:announcement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:announcement ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Standard packages publish organisation-level monthly token allowances. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Group allow-lists, content/model binding, admin defaults, per-user rate limits and behaviour after exhaustion or premium-model accounting are not specified. - model_allowlist_by_group — Can admins limit models per group? [unknown]: Can admins limit models per group? Unknown. Group allow-lists, content/model binding, admin defaults, per-user rate limits and behaviour after exhaustion or premium-model accounting are not specified. - 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. Group allow-lists, content/model binding, admin defaults, per-user rate limits and behaviour after exhaustion or premium-model accounting are not specified. - default_model — Can admins set the default model? [unknown]: Can admins set the default model? Unknown. Group allow-lists, content/model binding, admin defaults, per-user rate limits and behaviour after exhaustion or premium-model accounting are not specified. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Essential 20m, Professional 75m and Premium 200m tokens/month per company. These are pooled company allowances, not documented per-user caps. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. - limit_behaviour — What happens when a limit is reached? [unknown]: What happens when a limit is reached? Unknown. Group allow-lists, content/model binding, admin defaults, per-user rate limits and behaviour after exhaustion or premium-model accounting are not specified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet ## 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 Verification status: Agent cross-checked (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 2026-10-26; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial The factsheet lists document, image and audio analysis. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Storage quotas are per company, not per-file or per-chat limits. OCR, spreadsheet formula/table fidelity and whole-document versus chunked processing were not established; no upload fixture was run. - formats — Which formats are accepted? [partial]: Lists PDF, Word, Excel, CSV, JSON, TXT and audio files, plus image analysis. Exact extensions and codec limits are not enumerated. Sources: swisscom-assistant:swisscom-assistant:factsheet. - limits — What size and count limits apply per file and chat? [unknown]: What size and count limits apply per file and chat? Unknown. Storage quotas are per company, not per-file or per-chat limits. OCR, spreadsheet formula/table fidelity and whole-document versus chunked processing were not established; no upload fixture was run. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. Storage quotas are per company, not per-file or per-chat limits. OCR, spreadsheet formula/table fidelity and whole-document versus chunked processing were not established; no upload fixture was run. - spreadsheets — Are Excel tables read with structure intact? [unknown]: Are Excel tables read with structure intact? Unknown. Storage quotas are per company, not per-file or per-chat limits. OCR, spreadsheet formula/table fidelity and whole-document versus chunked processing were not established; no upload fixture was run. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [unknown]: Is the whole file used or only retrieved parts, and does the user see which? Unknown. Storage quotas are per company, not per-file or per-chat limits. OCR, spreadsheet formula/table fidelity and whole-document versus chunked processing were not established; no upload fixture was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid editions provide persistent document-backed personal assistants that can be shared. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Per-collection limits, shared-collection ownership and sharing-target controls need documentation or an authenticated tenant. - persistent_collections — Can users keep document collections across chats? [supported]: Users upload documents to assistants and retain chat histories; assistant storage persists across use. Sources: swisscom-assistant:swisscom-assistant:offer. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [partial]: Assistant sharing is included in paid editions; exact individual/group/organisation targeting is not specified. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. - size_limits — What are the collection limits? [partial]: Essential up to 3 assistants/user and 5 GB/customer; Professional 5 and 40 GB; Premium 7 and 150 GB. Per-collection file/count caps are not published. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. - assistant_binding — Can collections be bound to an assistant? [supported]: Employees build assistants with specific uploaded documents as their information sources. Sources: swisscom-assistant:swisscom-assistant:offer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:sharepoint, librechat:librechat:mcpcfg, librechat:librechat:mcp #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:access, librechat:librechat:sharepoint, librechat:librechat:agents #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:rag, librechat:librechat:ocr, librechat:librechat:compose-pin #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:rag, librechat:librechat:access #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial The basic-feature list advertises source references; citation accuracy was not tested. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - No shared DE/FR/EN corpus was loaded. Citation correctness, cross-language recall, refusal for unanswered questions and question-set accuracy remain untested. The guide recommends refusal instructions without proving enforced behaviour. - citations — Are answers linked to specific sources? [partial]: Transparent source references are listed as a basic feature; passage granularity was not established. Sources: swisscom-assistant:swisscom-assistant:offer. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared DE/FR/EN corpus was loaded. Citation correctness, cross-language recall, refusal for unanswered questions and question-set accuracy remain untested. The guide recommends refusal instructions without proving enforced behaviour. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No shared DE/FR/EN corpus was loaded. Citation correctness, cross-language recall, refusal for unanswered questions and question-set accuracy remain untested. The guide recommends refusal instructions without proving enforced behaviour. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared DE/FR/EN corpus was loaded. Citation correctness, cross-language recall, refusal for unanswered questions and question-set accuracy remain untested. The guide recommends refusal instructions without proving enforced behaviour. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared DE/FR/EN corpus was loaded. Citation correctness, cross-language recall, refusal for unanswered questions and question-set accuracy remain untested. The guide recommends refusal instructions without proving enforced behaviour. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:access #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Users create named assistants from documents and system instructions, with starter prompts and sharing. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Creator restrictions, directory/catalogue, assistant versioning, tool assignment and precise sharing scope were not documented or tested. - create_assistants — Can users create assistants with instructions, knowledge and tools? [partial]: The guide describes a named assistant, description, system prompt and uploaded documents. External tool assignment is not specified. Sources: swisscom-assistant:swisscom-assistant:guide. - creator_permissions — Can admins limit who creates them? [unknown]: Can admins limit who creates them? Unknown. Creator restrictions, directory/catalogue, assistant versioning, tool assignment and precise sharing scope were not documented or tested. - sharing_scope — Can assistants be shared with users, groups or everyone? [partial]: Users can share assistants with colleagues; exact user/group/company scope is not specified. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:guide. - catalogue — Is there an internal assistant directory? [unknown]: Is there an internal assistant directory? Unknown. Creator restrictions, directory/catalogue, assistant versioning, tool assignment and precise sharing scope were not documented or tested. - prompt_library — Are shared prompt templates available? [partial]: Assistant conversation starters can store example prompts. An organisation-managed shared prompt library is unverified. Sources: swisscom-assistant:swisscom-assistant:guide. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:guide, swisscom-assistant:swisscom-assistant:offer ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Standard editions include Web Fetch, with published request allowances. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Custom API actions, MCP client support, local/remote server controls, tool OAuth/shared-account identity and action approvals are not documented. - builtin_tools — Which tools are built in? [supported]: Processing web content via Web Fetch is included: 500 requests/month Essential, 2,000 Professional and 5,000 Premium; Custom is tailored. Sources: swisscom-assistant:swisscom-assistant:factsheet. - custom_actions — Can admins add API actions? [unknown]: Can admins add API actions? Unknown. Custom API actions, MCP client support, local/remote server controls, tool OAuth/shared-account identity and action approvals are not documented. - mcp_client — Can it use remote MCP servers, and with what admin control? [unknown]: Can it use remote MCP servers, and with what admin control? Unknown. Custom API actions, MCP client support, local/remote server controls, tool OAuth/shared-account identity and action approvals are not documented. - tool_auth — Do tools act as the user or as a shared account? [unknown]: Do tools act as the user or as a shared account? Unknown. Custom API actions, MCP client support, local/remote server controls, tool OAuth/shared-account identity and action approvals are not documented. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [unknown]: Can admins approve or block tools, and can users confirm actions before they run? Unknown. Custom API actions, MCP client support, local/remote server controls, tool OAuth/shared-account identity and action approvals are not documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:web, librechat:librechat:agents, librechat:librechat:access #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web search is a paid Custom option; standard Web Fetch is a different feature. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Search provider/region, admin organisation/group control, multi-step report research and search citation behaviour are not specified. Trial terms identify an unnamed EU Web Fetch provider, not a search engine. - web_search — Is web search available? [supported]: Factsheet explicitly marks Web Search unavailable in Essential/Professional/Premium and available for an additional charge in Custom. Sources: swisscom-assistant:swisscom-assistant:factsheet. - admin_toggle — Can admins disable it per organisation or group? [unknown]: Can admins disable it per organisation or group? Unknown. Search provider/region, admin organisation/group control, multi-step report research and search citation behaviour are not specified. Trial terms identify an unnamed EU Web Fetch provider, not a search engine. - search_provider — Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? Unknown. Search provider/region, admin organisation/group control, multi-step report research and search citation behaviour are not specified. Trial terms identify an unnamed EU Web Fetch provider, not a search engine. - deep_research — Is multi-step research with a report available? [unknown]: Is multi-step research with a report available? Unknown. Search provider/region, admin organisation/group control, multi-step report research and search citation behaviour are not specified. Trial terms identify an unnamed EU Web Fetch provider, not a search engine. - web_citations — Are web sources cited? [unknown]: Are web sources cited? Unknown. Search provider/region, admin organisation/group control, multi-step report research and search citation behaviour are not specified. Trial terms identify an unnamed EU Web Fetch provider, not a search engine. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:schedule, librechat:librechat:api #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workflow automation is listed as a paid Custom option. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Builder audience, schedules, external triggers and where workflows execute are not documented. The separate GenAI Studio platform is not assumed to be bundled. - workflow_builder — Is there a workflow or chain builder? [partial]: Factsheet marks workflow automation unavailable on standard editions and chargeable in Custom. A customer-configurable builder is not described. Sources: swisscom-assistant:swisscom-assistant:factsheet. - scheduled_tasks — Can prompts or assistants run on a schedule? [unknown]: Can prompts or assistants run on a schedule? Unknown. Builder audience, schedules, external triggers and where workflows execute are not documented. The separate GenAI Studio platform is not assumed to be bundled. - event_triggers — Can external events start a workflow? [unknown]: Can external events start a workflow? Unknown. Builder audience, schedules, external triggers and where workflows execute are not documented. The separate GenAI Studio platform is not assumed to be bundled. - builder_audience — Is building aimed at business users, IT or developers? [unknown]: Is building aimed at business users, IT or developers? Unknown. Builder audience, schedules, external triggers and where workflows execute are not documented. The separate GenAI Studio platform is not assumed to be bundled. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:code, librechat:librechat:releases #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial AI agents are listed as a paid Custom option. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Visible plans/tool calls, confirmation of side effects, stop controls and actual task execution were not established. - agent_mode — Is there an agent mode for multi-step tasks? [partial]: Factsheet marks AI agents unavailable on standard editions and chargeable in Custom; task/tool scope is not specified. Sources: swisscom-assistant:swisscom-assistant:factsheet. - visible_steps — Are steps and tool calls shown? [unknown]: Are steps and tool calls shown? Unknown. Visible plans/tool calls, confirmation of side effects, stop controls and actual task execution were not established. - side_effect_confirmation — Must the user confirm actions with side effects? [unknown]: Must the user confirm actions with side effects? Unknown. Visible plans/tool calls, confirmation of side effects, stop controls and actual task execution were not established. - stop_control — Can the user stop a running task? [unknown]: Can the user stop a running task? Unknown. Visible plans/tool calls, confirmation of side effects, stop controls and actual task execution were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:api, librechat:librechat:access #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial A browser-accessed company chatbot with Swisscom Login is offered. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Native Windows/macOS or iOS/Android apps, extension/sidebar, MDM configuration and mobile feature parity are not documented for this business Assistant. The separate consumer myAI product is excluded. - web — Is a full web client available? [supported]: The offer links activation through My Swisscom Business and describes an online company chatbot; browser access is shown by the published workspace material. Sources: swisscom-assistant:swisscom-assistant:offer. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. Native Windows/macOS or iOS/Android apps, extension/sidebar, MDM configuration and mobile feature parity are not documented for this business Assistant. The separate consumer myAI product is excluded. - mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. Native Windows/macOS or iOS/Android apps, extension/sidebar, MDM configuration and mobile feature parity are not documented for this business Assistant. The separate consumer myAI product is excluded. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. Native Windows/macOS or iOS/Android apps, extension/sidebar, MDM configuration and mobile feature parity are not documented for this business Assistant. The separate consumer myAI product is excluded. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. Native Windows/macOS or iOS/Android apps, extension/sidebar, MDM configuration and mobile feature parity are not documented for this business Assistant. The separate consumer myAI product is excluded. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. Native Windows/macOS or iOS/Android apps, extension/sidebar, MDM configuration and mobile feature parity are not documented for this business Assistant. The separate consumer myAI product is excluded. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer ### 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 Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Basic text translation and rewriting are advertised; de-CH/formality can be requested in assistant instructions. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Whole-document formatting, glossaries, enforced de-CH controls and translation quality on the shared contract fixture were not established. - document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Unknown. Whole-document formatting, glossaries, enforced de-CH controls and translation quality on the shared contract fixture were not established. - translation_engine — Which engine translates? [partial]: Product describes AI text translation and rewriting using its LLM chatbot; no separate translation service is named. Sources: swisscom-assistant:swisscom-assistant:offer. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? Unknown. Whole-document formatting, glossaries, enforced de-CH controls and translation quality on the shared contract fixture were not established. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Guide shows assistant instructions for Swiss spelling, ss instead of ß and informal/formal address. This is prompt guidance, not an enforced locale control. Sources: swisscom-assistant:swisscom-assistant:guide. - writing_tools — Are dedicated rewrite and proofreading tools available? [supported]: Translate, rewrite, summarise and create text are advertised across the basic service. Sources: swisscom-assistant:swisscom-assistant:offer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:guide ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:images, librechat:librechat:access #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:speech, librechat:librechat:speech-conversation-r2 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial The factsheet includes voice input and audio transcription in all paid editions. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Read-aloud, live two-way voice, speech languages including Swiss German and meeting-specific limits were not documented or tested. - dictation — Can users dictate prompts? [supported]: Voice input is included across Essential, Professional, Premium and Custom. Sources: swisscom-assistant:swisscom-assistant:factsheet. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. Read-aloud, live two-way voice, speech languages including Swiss German and meeting-specific limits were not documented or tested. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Read-aloud, live two-way voice, speech languages including Swiss German and meeting-specific limits were not documented or tested. - meeting_summaries — Are meetings transcribed and summarised? [partial]: Audio files and transcription are listed; product use cases mention meeting summaries. A live meeting bot, recording method and summary workflow are not specified. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Read-aloud, live two-way voice, speech languages including Swiss German and meeting-specific limits were not documented or tested. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:factsheet, swisscom-assistant:swisscom-assistant:offer ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:code, librechat:librechat:artifacts #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:share, librechat:librechat:projects #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:i18n-pin #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Swisscom Login is required; enterprise SSO is a paid Custom option. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - MFA enforcement, conditional access, domain capture, SSO protocols and Custom identity-provider configuration are not documented. - sso_protocols — Which SSO protocols and identity providers work? [partial]: Basic access requires a valid Swisscom Login. Custom SSO is listed but SAML/OIDC/IdP support is not specified. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet, swisscom-assistant:swisscom-assistant:trial-terms. - sso_plan — Which plan includes SSO? [supported]: Factsheet explicitly marks SSO unavailable on standard paid editions and chargeable in Custom. Sources: swisscom-assistant:swisscom-assistant:factsheet. - mfa — Can MFA be enforced? [unknown]: Can MFA be enforced? Unknown. MFA enforcement, conditional access, domain capture, SSO protocols and Custom identity-provider configuration are not documented. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. MFA enforcement, conditional access, domain capture, SSO protocols and Custom identity-provider configuration are not documented. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. MFA enforcement, conditional access, domain capture, SSO protocols and Custom identity-provider configuration are not documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet, swisscom-assistant:swisscom-assistant:trial-terms ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:access, librechat:librechat:admin, librechat:librechat:insights #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:insights, librechat:librechat:tokens #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:logging, librechat:librechat:retention, librechat:librechat:compose-pin #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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. - pii_detection — Is personal data detected in prompts and files? [partial]: Configured source-aware policies can inspect selected prompt fields and file names/extracted text/transcripts. Built-in starter rules match credentials; admins must supply additional personal-data patterns. Opaque files may be allowed by default or explicitly blocked. AHV/IBAN and confidential-file detection accuracy were not tested. 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. - pii_action — Is it redacted, masked, blocked or only warned? [partial]: Configured matches can block or audit. Redaction transforms only fresh, text-only interactive Agent submissions carrying clientRequestId and a valid CREDS_KEY; edits, resumes, files, quotes and other endpoints retain blocking checks. Original text is encrypted and unindexed, rather than discarded. No running deployment was tested. 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. - custom_patterns — Can admins add custom patterns or terms? [supported]: Operators can add labelled custom RE2JS regular expressions in base librechat.yaml, with optional categories. Database/role/group/user overrides cannot modify the policy; all replicas must load matching configuration. Invalid rules are rejected on configuration load. Sources: librechat:librechat:r4-content-filter, librechat:librechat:r4-patterns, librechat:librechat:r4-filter-middleware. - dlp_integration — Does it integrate with an existing DLP product? [unknown]: No first-party Purview/Netskope or other external DLP connector was established from the content-filter guide, current public repository tree and targeted official-site search. Configurable local patterns are not evidence of an external enterprise DLP integration. - filter_location — Where does filtering run? [supported]: Inspected content-filter middleware and rule evaluation run in the customer-operated LibreChat API backend. Optional extraction/OCR and inference providers remain separate data flows; no named deployment region or traffic path was tested. Sources: librechat:librechat:r4-pii-runtime, librechat:librechat:r4-filter-middleware. Checked 2026-10-26; 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 #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Custom guardrails are marketed; trial users accept vendor usage terms at login. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Organisation system instructions, configurable filter policies, violation reports and a customer-specific acknowledgement flow are not documented. Assistant prompts are a separate capability. - org_instructions — Can admins set organisation-wide instructions? [unknown]: Can admins set organisation-wide instructions? Unknown. Organisation system instructions, configurable filter policies, violation reports and a customer-specific acknowledgement flow are not documented. Assistant prompts are a separate capability. - usage_notice — Can users be required to accept a usage policy? [partial]: Free Trial B.3 states user usage terms are displayed at login and accepted by use. A customer-authored policy/explicit acknowledgement control is not specified. Sources: swisscom-assistant:swisscom-assistant:trial-terms. - content_filters — Are content filters configurable? [unknown]: Are content filters configurable? Unknown. Organisation system instructions, configurable filter policies, violation reports and a customer-specific acknowledgement flow are not documented. Assistant prompts are a separate capability. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Organisation system instructions, configurable filter policies, violation reports and a customer-specific acknowledgement flow are not documented. Assistant prompts are a separate capability. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:trial-terms ## 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Swisscom describes Swiss storage and inference; trial Web Fetch may send URLs to an EU third party. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Backups, logs/telemetry breakdown, index placement, full staff-access geography and paid/Custom Web Fetch exception terms are not established. Blanket Swiss-only wording needs the trial Web Fetch qualification. - storage_region — Where are chats, files and indexes stored? [partial]: Trial terms C.8 locate Swiss AI Platform and related login/chat/usage databases at Swisscom data centres in Switzerland. Paid offer also claims all customer data stored in Switzerland; file/index topology is unspecified. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:trial-terms. - inference_region — Where do model calls run, per provider? [supported]: Swiss AI Platform processing is exclusively in Swisscom Swiss data centres under trial C.8; current paid offer claims Swiss storage and processing. These are hosted open models, not calls to their originating providers. Sources: swisscom-assistant:swisscom-assistant:trial-terms, swisscom-assistant:swisscom-assistant:offer. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? Unknown. Backups, logs/telemetry breakdown, index placement, full staff-access geography and paid/Custom Web Fetch exception terms are not established. Blanket Swiss-only wording needs the trial Web Fetch qualification. - support_access_region — From where can vendor staff access data? [partial]: Factsheet advertises support directly from Switzerland. This does not establish every staff access location or privileged-support boundary. Sources: swisscom-assistant:swisscom-assistant:factsheet. - swiss_hosting — Is Swiss hosting available? [supported]: Swisscom Cloud in Switzerland is the stated hosting for this Assistant. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. - residency_plan — Which plan or option provides residency? [partial]: Swiss hosting is advertised for all editions. Free Trial C.8 explicitly permits Web Fetch to transmit referenced URLs to an unnamed external EU provider. Custom search data flows were not documented. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:trial-terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:trial-terms, swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:compose-pin, librechat:librechat:firstchat #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Trial terms prohibit training on submitted data; the paid offer repeats the no-training claim. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Provider retention/abuse monitoring, zero retention and staff content-review conditions are not specified. Locally hosted model weights do not establish a zero-retention contract. - vendor_training — Does the vendor train on customer content? [supported]: Trial C.9 limits submitted data to its requested purpose and forbids training/developing the LLM. Paid offer makes the same claim but no paid DPA was retrieved. Sources: swisscom-assistant:swisscom-assistant:trial-terms, swisscom-assistant:swisscom-assistant:offer. - provider_training — Do model providers train on it under this product's contracts? [partial]: Trial C.8 uses publicly available unchanged open models on Swisscom infrastructure. Data training by external model providers is not described; paid page says no company-data model training. Sources: swisscom-assistant:swisscom-assistant:trial-terms, swisscom-assistant:swisscom-assistant:offer. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [unknown]: How long do model providers keep prompts, including for abuse monitoring? Unknown. Provider retention/abuse monitoring, zero retention and staff content-review conditions are not specified. Locally hosted model weights do not establish a zero-retention contract. - zero_retention — Is zero data retention available, and on which plan? [unknown]: Is zero data retention available, and on which plan? Unknown. Provider retention/abuse monitoring, zero retention and staff content-review conditions are not specified. Locally hosted model weights do not establish a zero-retention contract. - human_review — Can provider staff review content? [unknown]: Can provider staff review content? Unknown. Provider retention/abuse monitoring, zero retention and staff content-review conditions are not specified. Locally hosted model weights do not establish a zero-retention contract. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:trial-terms, swisscom-assistant:swisscom-assistant:offer ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:retention, librechat:librechat:settings #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unconverted trial data is deleted three months after trial end. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Admin retention configuration, permanent user deletion, paid contract-end timing and backup deletion/confirmation remain undocumented. Trial expiry is not paid-contract termination. - default_retention — What is retained and for how long by default? [partial]: Trial C.9 retains assistants/chat histories for potential paid conversion and deletes all trial data if no purchase occurs within three months after trial end. Paid default chat/file/index/log retention is not specified. Sources: swisscom-assistant:swisscom-assistant:trial-terms, swisscom-assistant:swisscom-assistant:offer. - admin_retention — Can admins set retention periods? [unknown]: Can admins set retention periods? Unknown. Admin retention configuration, permanent user deletion, paid contract-end timing and backup deletion/confirmation remain undocumented. Trial expiry is not paid-contract termination. - user_deletion — Can users delete their chats and files permanently? [unknown]: Can users delete their chats and files permanently? Unknown. Admin retention configuration, permanent user deletion, paid contract-end timing and backup deletion/confirmation remain undocumented. Trial expiry is not paid-contract termination. - contract_end_deletion — What is deleted at contract end, and when? [unknown]: What is deleted at contract end, and when? Unknown. Admin retention configuration, permanent user deletion, paid contract-end timing and backup deletion/confirmation remain undocumented. Trial expiry is not paid-contract termination. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:trial-terms, swisscom-assistant:swisscom-assistant:offer ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:owner #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Trial contract identifies a Swiss provider and an unnamed EU Web Fetch processor. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - No Assistant-specific dated subprocessor list, change-notification rule, transfer mechanism or detailed government-access policy was retrieved. Marketing CLOUD Act protection is a vendor claim, not a legal conclusion. - subprocessor_list — Is a dated sub-processor list published? [unknown]: Is a dated sub-processor list published? Unknown. No Assistant-specific dated subprocessor list, change-notification rule, transfer mechanism or detailed government-access policy was retrieved. Marketing CLOUD Act protection is a vendor claim, not a legal conclusion. - subprocessor_countries — Which countries do sub-processors operate in? [partial]: Trial C.8 permits an external EU third party for URL retrieval; its identity is not listed. Swiss AI Platform itself runs in Switzerland. Sources: swisscom-assistant:swisscom-assistant:trial-terms. - change_notification — Are customers notified of sub-processor changes? [unknown]: Are customers notified of sub-processor changes? Unknown. No Assistant-specific dated subprocessor list, change-notification rule, transfer mechanism or detailed government-access policy was retrieved. Marketing CLOUD Act protection is a vendor claim, not a legal conclusion. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: Trial names Swisscom (Switzerland) Ltd as provider. The parent incorporation/ownership was not independently re-retrieved in this pass. Sources: swisscom-assistant:swisscom-assistant:trial-terms. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [unknown]: Which transfer mechanism applies to non-EU/CH processing? Unknown. No Assistant-specific dated subprocessor list, change-notification rule, transfer mechanism or detailed government-access policy was retrieved. Marketing CLOUD Act protection is a vendor claim, not a legal conclusion. - government_access_policy — Is there a published government-access or transparency policy? [unknown]: Is there a published government-access or transparency policy? Unknown. No Assistant-specific dated subprocessor list, change-notification rule, transfer mechanism or detailed government-access policy was retrieved. Marketing CLOUD Act protection is a vendor claim, not a legal conclusion. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:trial-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 Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## 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 Verification status: Agent cross-checked (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. - pricing_unit — What is the pricing unit? [supported]: The pinned MIT permission grant has no per-user fee; self-hosting and model accounts are customer responsibilities. Sources: librechat:librechat:license, librechat:librechat:firstchat. - list_prices — What are list prices per plan, with date and currency? [supported]: The repository’s MIT licence permits use without a software fee as retrieved 2026-10-21; there is no bundled inference subscription in this scope. Sources: librechat:librechat:license, librechat:librechat:firstchat. - included_usage — What usage is included? [supported]: LibreChat ships with no model API key and no included provider token balance. Sources: librechat:librechat:firstchat. - add_ons — Which features cost extra? [partial]: Optional external code/OCR/search/image services need separately configured endpoints and credentials. Their rates depend on the operator’s contracts. Sources: librechat:librechat:code, librechat:librechat:ocr, librechat:librechat:web, librechat:librechat:images. - overage — What do usage beyond limits and premium models cost? [partial]: Provider APIs charge their account holder; internal credit balances are governance configuration rather than a single LibreChat usage tariff. Sources: librechat:librechat:balance, librechat:librechat:tokens, librechat:librechat:firstchat. Checked 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Swisscom publishes monthly organisation packages in CHF excluding VAT. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Overage prices, model-specific token accounting and extra Custom feature rates are not published in accessible sources. - pricing_unit — What is the pricing unit? [supported]: Flat monthly price per company package with user, storage and token caps; Custom is quoted. Sources: swisscom-assistant:swisscom-assistant:offer. - list_prices — What are list prices per plan, with date and currency? [supported]: As retrieved 2026-10-21: Essential CHF 149/month up to 10 users; Professional CHF 399 up to 40; Premium CHF 799 up to 100, all excluding VAT. Custom has no public numerical price. Sources: swisscom-assistant:swisscom-assistant:offer. - included_usage — What usage is included? [supported]: Essential 5 GB/20m tokens; Professional 40 GB/75m; Premium 150 GB/200m monthly company tokens. Web Fetch requests/month 500/2,000/5,000 respectively. Assistant caps 3/5/7 per user. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. - add_ons — Which features cost extra? [partial]: Custom Web Search, SSO, agents and workflows cost extra per matrix; rates are not public. Sources: swisscom-assistant:swisscom-assistant:factsheet. - overage — What do usage beyond limits and premium models cost? [unknown]: What do usage beyond limits and premium models cost? Unknown. Overage prices, model-specific token accounting and extra Custom feature rates are not published in accessible sources. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 200 users, 12 months excluding VAT: from CHF 34778.28 / EUR 37651.06 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 4749.26, operations CHF 30000.00, and BYO model usage USD 475.20. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: librechat:librechat:license, librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:cost-fx, librechat:librechat:cost-model, librechat:librechat:cost-effort. - cost_1000 — Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 1,000 users, 12 months excluding VAT: from CHF 88600.40 / EUR 95919.02 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 12605.23, operations CHF 75000.00, and BYO model usage USD 2376.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: librechat:librechat:license, librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:cost-fx, librechat:librechat:cost-model, librechat:librechat:cost-effort. - cost_5000 — Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. 5,000 users, 12 months excluding VAT: from CHF 189541.24 / EUR 205197.83 plus unpriced items. Includes zero standard-software licence, reference infrastructure EUR 32214.49, operations CHF 150000.00, and BYO model usage USD 11880.00. This is an assumption-based budget floor, not a vendor quote or validated capacity plan. Sources: librechat:librechat:license, librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:cost-fx, librechat:librechat:cost-model, librechat:librechat:cost-effort. - variable_share — Which part depends on usage? [partial]: Shared mix is 60% light at 100, 30% regular at 400 and 10% power at 1,500 messages/user/month, or 330 weighted messages. Each message is 3,000 input and 600 output tokens. Direct BYO proxy is gpt-6-luna, reasoning effort none, Standard short-context uncached rates USD 0.10/0.50 per million input/output tokens. It costs USD 2.376/user/year before optional tools, embedding, caching or regional processing. This proxy is an analyst assumption, not the product default. Sources: librechat:librechat:cost-model, librechat:librechat:cost-effort. - unknown_parts — Which costs could not be priced? [partial]: Unpriced additions are file/object storage beyond the assumed 500 GB PostgreSQL storage, VM OS/data disks, backup excess, egress/load balancers, Redis or additional database services, high availability, embeddings, OCR, search, audio/images, integration work and optional commercial services. MongoDB remains the primary store, so its infrastructure, file storage and other required dependencies are additional unpriced items; PostgreSQL is only the shared RAG/reference compute assumption. The shared VM/PG sizes have not been load-tested and do not replace each product’s documented runtime dependencies. Sources: librechat:librechat:cost-vm, librechat:librechat:cost-pg, librechat:librechat:license. Checked 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21. The 200, 1,000 and 5,000-seat scenarios require a Custom quote and cannot be priced from packages capped at 100 users. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - variable_share — Which part depends on usage? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - unknown_parts — Which costs could not be priced? [supported]: Custom base price, token pool/overage, connectors, agents, SSO and service costs are unpriced. Multiple standard packages are not assumed to form one enterprise contract. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet, swisscom-assistant:swisscom-assistant: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 Verification status: Agent cross-checked (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 2026-10-21; 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 #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial A one-month business trial is self-activated by eligible My Swisscom Business administrators. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - No permanent business free tier, card requirement or complete SSO/connector/admin trial scope was established. No existing eligible business account was available, so fixtures were not run. - free_tier — Is there a free tier for business use? [unknown]: Is there a free tier for business use? Unknown. No permanent business free tier, card requirement or complete SSO/connector/admin trial scope was established. No existing eligible business account was available, so fixtures were not run. - self_serve_trial — Is a self-serve business trial available? [partial]: Offer provides one month free, up to 2 assistants/user and 10m tokens/company. Activation requires My Swisscom Business administrator rights and Swisscom Login. New noncustomers are directed to contact Swisscom. Sources: swisscom-assistant:swisscom-assistant:offer. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Published trial includes assistant creation and company token allowance; SSO/connectors/admin entitlement and seat count are not specified. Sources: swisscom-assistant:swisscom-assistant:offer. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Existing eligible company administrators can activate online; people without a Swisscom customer account are directed to contact Swisscom. Custom evaluation requires scope clarification. Sources: swisscom-assistant:swisscom-assistant:offer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:local, librechat:librechat:firstchat #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial There is no minimum contract duration; cancellation is 30 days to calendar-month end. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Annual-billing options, price-change policy, EUR invoices and complete Custom commitments are not documented in accessible sources. - minimum_commitment — What seat or spend minimum applies? [supported]: Offer explicitly says no minimum contract duration; organisation package caps apply, with Custom terms separately quoted. Sources: swisscom-assistant:swisscom-assistant:offer. - contract_length — What contract lengths are offered? [partial]: Monthly subscription/package prices; no minimum duration. Annual prepayment options are not specified. Sources: swisscom-assistant:swisscom-assistant:offer. - cancellation — How can the contract be cancelled or reduced? [supported]: Cancel online with 30 days notice to month-end. Upgrades bill pro rata from upgrade day; downgrades only on the first day of a following month. Sources: swisscom-assistant:swisscom-assistant:offer. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: CHF excluding VAT prices are published by Swisscom. EUR invoicing and a paid contracting-entity invoice specimen are not established. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:trial-terms. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified. Standard monthly prices and capacities are public; Custom, overage and add-on rates require a quote. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:trial-terms, swisscom-assistant:swisscom-assistant:factsheet ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:license, librechat:librechat:admin, librechat:librechat:code #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Free Trial terms grant a restricted service-use licence and reserve intellectual property. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Paid server/client/connector component licences and any distinct closed enterprise source edition are not published in retrieved documents. - licence_type — Which licence applies to each component? [partial]: Trial B.1/B.6 gives non-exclusive non-transferable internal-business use and prohibits copying, modifying or distributing the chatbot. This is distinct from the open licences of underlying model weights. Sources: swisscom-assistant:swisscom-assistant:trial-terms. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Custom branding with name/logo/colours is included in paid basic features; trial bars copying or modifying the chatbot. Full paid component licence and seat restrictions remain unavailable. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:trial-terms. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. Paid server/client/connector component licences and any distinct closed enterprise source edition are not published in retrieved documents. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:trial-terms, swisscom-assistant:swisscom-assistant:offer ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:export-pin, librechat:librechat:api #### Swisscom Swiss AI Assistant Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:logging, librechat:librechat:firstchat #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Personal Swisscom support is included; trial terms disclaim availability guarantees. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Guaranteed support languages/hours, response times, paid SLA credits and an Assistant-specific public status/incident history were not located. - support_channels — Which support channels are available on each plan? [partial]: Personalised support is a basic feature across editions; page supplies an enquiry form. Contractual response-time channels are not specified. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Guaranteed support languages/hours, response times, paid SLA credits and an Assistant-specific public status/incident history were not located. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: Factsheet identifies Swisscom (Switzerland) Ltd Enterprise Customers in Berne and support directly from Switzerland. Sources: swisscom-assistant:swisscom-assistant:factsheet. - uptime_sla — Is there an uptime SLA with credits? [partial]: Free Trial B.4 explicitly provides no availability/accessibility guarantee. Paid uptime SLA and credits were not retrieved. Sources: swisscom-assistant:swisscom-assistant:trial-terms. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? Unknown. Guaranteed support languages/hours, response times, paid SLA credits and an Assistant-specific public status/incident history were not located. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:factsheet, swisscom-assistant:swisscom-assistant:trial-terms ### 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 Verification status: Agent cross-checked (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 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: librechat:librechat:agents, librechat:librechat:firstchat #### Swisscom Swiss AI Assistant Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public videos and a setup guide support self-service assistant creation. Availability: generally-available Delivery: native Scope: surfaces=Swiss AI Assistant browser workspace; version=not specified; plan=Essential, Professional and Premium standard editions; separately quoted Custom; one-month Free Trial where stated; add_ons=none stated; deployment_mode=not specified; region=Switzerland Swisscom Cloud; Free Trial Web Fetch can send URLs to an external EU provider; os=not specified. Limitations: - Guided onboarding entitlement, champion/adoption programmes and paid consulting/training costs are not specified. Personal support does not establish a full adoption programme. - onboarding_service — Is guided onboarding included? [unknown]: Is guided onboarding included? Unknown. Guided onboarding entitlement, champion/adoption programmes and paid consulting/training costs are not specified. Personal support does not establish a full adoption programme. - user_training — Is end-user training offered, in which languages? [partial]: Offer links FAQ videos for starting a trial, building an assistant and custom prompts; the guide provides a German walkthrough. Formal training languages and inclusion are not specified. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:guide. - use_case_library — Are role-based use cases and templates provided? [supported]: Published HR, support, manuals, correspondence and sales examples plus example instructions provide use-case material. Sources: swisscom-assistant:swisscom-assistant:guide. - adoption_programme — Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Unknown. Guided onboarding entitlement, champion/adoption programmes and paid consulting/training costs are not specified. Personal support does not establish a full adoption programme. - service_cost — Which services cost extra? [unknown]: Which services cost extra? Unknown. Guided onboarding entitlement, champion/adoption programmes and paid consulting/training costs are not specified. Personal support does not establish a full adoption programme. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swisscom-assistant:swisscom-assistant:offer, swisscom-assistant:swisscom-assistant:guide ## Sources ### librechat:librechat:custom Custom endpoints. Operators configure compatible endpoints and customer-held keys, including local and hosted services. - URL: https://www.librechat.ai/docs/quick_start/custom_endpoints - Locator: Endpoint setup; API key; base URL; model list - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:azure Azure OpenAI configuration. Azure OpenAI uses customer deployment groups, instance names and credentials. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/ai_endpoints/azure - Locator: Deployment groups; API credentials - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:bedrock AWS Bedrock object structure. Bedrock routes use customer AWS configuration and region selection. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/aws_bedrock - Locator: Region; credentials; model selection - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:vertex Anthropic Vertex AI configuration. Claude can run through customer Google Vertex AI credentials and regions. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/anthropic_vertex - Locator: Project and region configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:modelspec Model specifications. Administrators can enforce configured model presets and defaults; available endpoints still depend on customer credentials. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/model_specs - Locator: enforce; preset; modelSelect; addedEndpoints - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:agents Agents. Agents combine instructions, models, files, tools, skills and sharing permissions, with visible execution and configurable approval. - URL: https://www.librechat.ai/docs/features/agents - Locator: Builder; Capabilities; Version history; Sharing; Activity; tool approval - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:ocr OCR for documents. OCR can augment text extraction, or files can be sent to compatible provider APIs; format and model limitations remain. - URL: https://www.librechat.ai/docs/features/ocr - Locator: File Context; Upload as Text; Optional OCR; Limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:releases LibreChat v0.8.8 release. The stable release documents agent controls, current model updates and explicitly experimental schedules/workspaces and beta Agents API. - URL: https://github.com/LibreChat-AI/LibreChat/releases/tag/v0.8.8 - Locator: Highlights, 2026-10-01 - Evidence kind: documented - Source date: 2026-10-01 - Retrieved: 2026-10-21 ### swisscom-assistant:swisscom-assistant:offer Swiss AI Assistant offer and FAQ. Lists Swiss hosting, current selectable models, flat-rate packages, Swisscom Login, trial retention and commercial conditions. - URL: https://www.swisscom.ch/en/business/sme/it-cloud/new-way-of-working/swiss-ai-assistant.html - Locator: Basic features; edition cards; Custom; FAQ; Additional offer terms - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### swisscom-assistant:swisscom-assistant:factsheet Swiss AI Assistant factsheet. Lists document/audio/image features and marks web search, SSO, agents and workflow automation unavailable on standard editions and chargeable in Custom. - URL: https://documents.swisscom.com/product/filestore/lib/1f276f70-63fc-4e15-8cc1-086ae198fdea/factsheet_swiss_a_assistant-en.pdf?idxme=pex-search - Locator: Page 2 hosted service; page 3 feature matrix and legend - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:firstchat Your first chat. LibreChat ships without a model key; the public demo is for evaluation rather than private or durable data. - URL: https://www.librechat.ai/docs/quick_start/first_chat - Locator: Software you host yourself; endpoint credentials; public demo - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:code Code Interpreter API. A separate code execution service supports multiple languages and downloadable generated files; stateful/attached modes are experimental. - URL: https://www.librechat.ai/docs/features/code_interpreter - Locator: Setup; self-hosted service; workspace permissions; generated files - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:license LibreChat v0.8.8 MIT licence. The pinned repository is MIT licensed with copyright/permission notice preservation and an as-is disclaimer. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/LICENSE - Locator: LICENSE, permission grant and notice requirement - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:ragcfg RAG API configuration. OpenAI, Hugging Face and Ollama embedding configurations are documented; image choice affects local embedding support. - URL: https://www.librechat.ai/docs/configuration/rag_api - Locator: Embedding providers; lite image; full image - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swisscom-assistant:swisscom-assistant:announcement Swiss AI Assistant knowledge-management announcement. Describes Swiss-operated unchanged open models, future Apertus availability and the distinct Swiss AI Platform portfolio. - URL: https://www.swisscom.ch/en/about/news/2026/02/18-swiss-ai-assistant.html - Locator: AI with clear data sovereignty; AI introduction; AI strategy - Evidence kind: vendor-claimed - Source date: 2026-02-18 - Retrieved: 2026-10-21 ### librechat:librechat:access Granular access control. Roles, groups and resource ACLs govern features and sharing, with Entra groups synchronized at sign-in. - URL: https://www.librechat.ai/docs/features/access_control - Locator: Feature permissions; Resource ACLs; System grants; Groups - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:admin LibreChat Admin Panel. A separate browser management panel is available for testing and uses the underlying LibreChat admin APIs. - URL: https://www.librechat.ai/docs/features/admin_panel - Locator: Status Preview; separate service; admin APIs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:balance Balance configuration. Optional token-credit balances initialize and refill user credits; tracking is disabled by default. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/balance - Locator: enabled; startBalance; refill configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:mod Automated moderation. Moderation scores abusive login/registration/message activity and may ban users; it is not a documented content DLP classifier. - URL: https://www.librechat.ai/docs/features/mod_system - Locator: Violation scoring and limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:balance-pin LibreChat balance admission implementation. The pinned middleware reserves user credits and throws a TOKEN_BALANCE error when the reservation cannot be admitted. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/packages/api/src/middleware/checkBalance.ts - Locator: packages/api/src/middleware/checkBalance.ts, checkBalance - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: packages/api/src/middleware/checkBalance.ts ### librechat:librechat:rag RAG API. A separate RAG API indexes uploaded content in PostgreSQL/PGVector for retrieval. - URL: https://www.librechat.ai/docs/features/rag_api - Locator: Architecture; document indexing; embeddings; semantic search - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:text Upload files as text. Text upload injects extracted file content rather than relying only on vector retrieval. - URL: https://www.librechat.ai/docs/features/upload_as_text - Locator: Full text extraction and context - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:filecfg File configuration. File limits and formats are configurable by endpoint and file processing route. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/file_config - Locator: File limits; MIME patterns; provider routes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:r4-spreadsheet-parser LibreChat spreadsheet text 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. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/files/documents/crud.ts - Locator: getParserForMimeType; excelSheetToText, lines 109-129 - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/files/documents/crud.ts ### librechat:librechat:r4-text-current LibreChat current Upload as Text guide. The development guide lists XLSX/XLS/ODS parsing up to 15 MB and token-bounded text injection, not a formatted spreadsheet editor. - URL: https://www.librechat.ai/docs/features/upload_as_text - Locator: Built-in parser; supported documents; truncation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### librechat:librechat:projects Projects. Projects persist files and instructions across a user’s chats but cannot be shared or transferred. - URL: https://www.librechat.ai/docs/features/projects - Locator: Availability; personal scope; files and instructions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:sharepoint SharePoint and OneDrive integration. The Microsoft file picker uses Entra token reuse and delegated on-behalf-of downloads to attach files. - URL: https://www.librechat.ai/docs/configuration/sharepoint - Locator: Prerequisites; delegated permissions; admin consent - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:mcp MCP. MCP servers can be configured through YAML or the permission-gated UI, including per-user OAuth. - URL: https://www.librechat.ai/docs/features/mcp - Locator: YAML/UI setup; authentication; ownership and selection - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:mcpcfg MCP server configuration. Configuration includes stdio, SSE and Streamable HTTP transports and server-specific credentials. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/mcp_servers - Locator: Transport examples; headers; OAuth - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:compose-pin LibreChat Docker service configuration. The pinned example runs a MongoDB primary store and a separate PGVector/RAG service with customer-mounted data. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/docker-compose.yml - Locator: docker-compose.yml, api/mongodb/vectordb/rag_api services - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: docker-compose.yml ### librechat:librechat:memory User memory. Configured user memory stores cross-chat key/value context with user editing controls; it does not index all past chats. - URL: https://www.librechat.ai/docs/features/memory - Locator: Key/value store; controls; disabled by default - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swisscom-assistant:swisscom-assistant:guide How SMEs use AI assistants. Gives a Swiss AI Assistant setup example with document upload, assistant system instructions, conversation starters and colleague sharing. - URL: https://www.swisscom.ch/de/b2bmag/new-way-of-working/ki-assistent-kmu-nutzen/ - Locator: Anleitung: einen KI-Assistenten erstellen, steps 1-6 - Evidence kind: documented - Source date: 2026-09-16 - Retrieved: 2026-10-21 ### librechat:librechat:images Image generation and editing. Agents can use configured image tools for generation/editing; provider credentials and model parameters are separate. - URL: https://www.librechat.ai/docs/features/image_gen - Locator: OpenAI Image Tools; provider setup; admin configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:web Web search. Search can use Serper, SearXNG, Tavily or Keenable, with independently configured scraping and optional reranking. - URL: https://www.librechat.ai/docs/features/web_search - Locator: Provider, scraper and reranker configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:schedule Scheduled Chats. Opt-in experimental schedules execute saved Agents with cron/time zones and recheck access and balance before running. - URL: https://www.librechat.ai/docs/features/scheduled_chats - Locator: Experimental and disabled by default; runtime and permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:api Agents API beta. The beta API exposes chat/Responses inference, Agent/Skill management and authenticated event delivery. - URL: https://www.librechat.ai/docs/features/agents_api - Locator: Inference; management; Agent Events; authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:retention Temporary chat and data retention. Operators configure expiry for chats/messages/files/shared links; normal chats do not expire by default and memories are excluded. - URL: https://www.librechat.ai/docs/features/temporary_chat - Locator: Default 30-day temporary retention; all/ephemeral; deadlines; memories - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:insights Admin Insights. Insights reports persisted MongoDB activity and identifiable recent conversations; it is not monetary billing analytics. - URL: https://www.librechat.ai/docs/features/insights - Locator: Opt-in; capabilities; metrics; tenant scope - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:local Docker installation. Docker self-installation runs LibreChat with its configured service dependencies. - URL: https://www.librechat.ai/docs/local/docker - Locator: Installation; configuration; updating - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:speech Speech configuration. Administrators configure audio provider engines and models separately from text generation. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/speech - Locator: Speech-to-text and text-to-speech engines - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:speech-conversation-r2 LibreChat conversation-mode speech settings. Conversation mode chains transcription, auto-send and TTS playback for hands-free turns after microphone activation; engines and audio routing are separately configured. - URL: https://www.librechat.ai/docs/configuration/stt_tts - Locator: Speech Tab: conversationMode, autoTranscribeAudio, autoSendText, automaticPlayback; engine and allowedAddresses settings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:artifacts Artifacts. Artifacts render generated React, HTML and Mermaid content in the chat interface. - URL: https://www.librechat.ai/docs/features/artifacts - Locator: React, HTML and Mermaid previews - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:share Shareable links. Shared links publish a transcript branch and optional file snapshots independently of the owner’s live file ACL. - URL: https://www.librechat.ai/docs/features/shareable_links - Locator: Authentication defaults; file snapshots; continuation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:i18n-pin LibreChat locale registration. The pinned client registers English, German, French and Italian translations among its supported locales. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/client/src/locales/i18n.ts - Locator: client/src/locales/i18n.ts, language resources - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: client/src/locales/i18n.ts ### librechat:librechat:auth Authentication system. Local/LDAP accounts can be required to use TOTP; federated MFA belongs to the identity provider and account creation/deletion scripts are documented. - URL: https://www.librechat.ai/docs/configuration/authentication - Locator: Required two-factor authentication; Registration; User scripts - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:openid OAuth2 and OIDC. LibreChat documents OAuth2/OIDC providers including Microsoft Entra, Google, Keycloak and Auth0. - URL: https://www.librechat.ai/docs/configuration/authentication/OAuth2-OIDC - Locator: Supported providers; setup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:saml SAML authentication. SAML is a documented authentication option for the self-hosted application. - URL: https://www.librechat.ai/docs/configuration/authentication/SAML - Locator: Overview and requirements - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:entra Azure Entra authentication. Entra OIDC supports group-based admission and Graph integration using configured scopes and token reuse. - URL: https://www.librechat.ai/docs/configuration/authentication/OAuth2-OIDC/azure - Locator: Group claims; token reuse; Microsoft Graph integration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swisscom-assistant:swisscom-assistant:trial-terms Data protection and terms of use, Swiss AI Assistant Free Trial. Specifies Swiss platform processing, EU Web Fetch URL exception, no training, trial rights and deletion three months after an unconverted trial. - URL: https://documents.swisscom.com/product/filestore/lib/a195711f-5f91-4746-96c1-8394cb28f0fd/leg1955-en.pdf - Locator: Page 1 sections B.1-B.7 and C.8-C.9; version Jun2026 - Evidence kind: documented - Source date: 2026-06-01 - Retrieved: 2026-10-21 ### librechat:librechat:tokens Token usage. Usage and estimated costs use recorded tokens and configured provider rates; transactions are distinct from balance enforcement. - URL: https://www.librechat.ai/docs/configuration/token_usage - Locator: Context cost; transactions; per-endpoint token rates - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:logging 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. - URL: https://www.librechat.ai/docs/configuration/logging - Locator: Error/debug logs; rotation; external tools - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:r4-content-filter LibreChat development content-filter configuration. 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. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/message_filter - Locator: Source-Aware Filters; Pattern Configuration; Redaction; File Fields - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### librechat:librechat:r4-pii-runtime LibreChat content-inspection runtime. Source-aware configured inspection executes in the LibreChat API. Missing policy disables that scope; configured actions and fields bound inspection. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/protection/runtime.ts - Locator: createConfiguredContentInspector; source rule configuration - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/protection/runtime.ts ### librechat:librechat:r4-patterns LibreChat pattern detector. Default starter patterns detect credential-shaped tokens/headers. Operator custom patterns use bounded regular expressions; a generic comprehensive PII classifier is not established. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/protection/detectors/pattern.ts - Locator: STARTER_PATTERNS; configured RE2JS rules - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/protection/detectors/pattern.ts ### librechat:librechat:r4-private-submission LibreChat private text 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. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/protection/private/submission.ts - Locator: createPrivateTextIngress; fresh Agent text and clientRequestId checks - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/protection/private/submission.ts ### librechat:librechat:r4-filter-middleware LibreChat API content-filter middleware. The server middleware applies configured inspection and rejects blocked/uninspectable requests with HTTP 400. No deployment or detection fixture was run. - URL: https://github.com/LibreChat-AI/LibreChat/blob/a378657583567310c841d652b0f6b00c83e2bd6b/packages/api/src/middleware/messageFilterPii.ts - Locator: createMessageFilterPii; contentFilterBlockResponse; uninspectable response - Evidence kind: source-inspected - Source date: 2026-10-24 - Retrieved: 2026-10-26 - Commit: a378657583567310c841d652b0f6b00c83e2bd6b - Path: packages/api/src/middleware/messageFilterPii.ts ### librechat:librechat:r4-config-1318 LibreChat config v1.3.18 changelog. 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. - URL: https://www.librechat.ai/changelog/config_v1.3.18 - Locator: October 22, 2026; opt-in PII redaction; retention mode - Evidence kind: documented - Source date: 2026-10-22 - Retrieved: 2026-10-26 ### librechat:librechat:interface Interface configuration. Administrators configure UI feature permissions and usage terms in the self-hosted deployment. - URL: https://www.librechat.ai/docs/configuration/librechat_yaml/object_structure/interface - Locator: Feature permissions; custom welcome and terms - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:remote Remote hosting. The application can be deployed on customer-selected remote servers with operator-managed security. - URL: https://www.librechat.ai/docs/remote - Locator: Hosting options; security considerations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:demo LibreChat Demo terms. The free hosted Demo is offered as-is with possible data cleanups and no durable business-service guarantee. - URL: https://www.librechat.ai/demo/terms - Locator: Evaluation scope; retention; disclaimer - Evidence kind: documented - Source date: 2026-03-12 - Retrieved: 2026-10-21 ### librechat:librechat:settings Personal settings. Users configure interface language, audio and personal data controls. - URL: https://www.librechat.ai/docs/features/settings - Locator: Language; speech; data controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:owner ClickHouse acquisition of LibreChat. ClickHouse announced the acquisition of LibreChat and that Danny Avila and the team joined ClickHouse. - URL: https://clickhouse.com/blog/clickhouse-acquires-librechat - Locator: Announcement, November 4, 2025 - Evidence kind: documented - Source date: 2025-11-04 - Retrieved: 2026-10-21 ### librechat:librechat:siteprivacy LibreChat website privacy policy. Website, demo and self-hosted software are distinct privacy scopes; website terms do not establish a customer deployment DPA. - URL: https://www.librechat.ai/privacy - Locator: Scope and exclusions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:secrecy-message-pin LibreChat v0.8.8 message storage schema. 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. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/packages/data-schemas/src/schema/message.ts - Locator: packages/data-schemas/src/schema/message.ts, text at lines 55-58 and content at lines 139-143 - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: packages/data-schemas/src/schema/message.ts ### librechat:librechat:secrecy-demo-policy LibreChat Demo privacy 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. - URL: https://www.librechat.ai/demo/privacy - Locator: Scope; section 4 Third-Party AI Model Providers; section 6 Data Sharing and Sub-Processors - Evidence kind: documented - Source date: 2026-03-12 - Retrieved: 2026-10-21 ### librechat:librechat:cost-vm Azure Retail Prices, Switzerland North Linux VMs. EUR hourly PAYG rates retrieved 2026-10-21 are 0.2226, 0.4453 and 0.8905 for D4s, D8s and D16s v5 respectively. - URL: https://prices.azure.com/api/retail/prices?currencyCode=EUR&%24filter=armRegionName+eq+%27switzerlandnorth%27+and+serviceName+eq+%27Virtual+Machines%27+and+%28armSkuName+eq+%27Standard_D4s_v5%27+or+armSkuName+eq+%27Standard_D8s_v5%27+or+armSkuName+eq+%27Standard_D16s_v5%27%29+and+priceType+eq+%27Consumption%27 - Locator: Consumption; Virtual Machines Dsv5 Series; Standard_D4s_v5/D8s_v5/D16s_v5 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:cost-pg Azure Retail Prices, PostgreSQL Flexible Server. 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. - URL: https://prices.azure.com/api/retail/prices?currencyCode=EUR&%24filter=armRegionName+eq+%27switzerlandnorth%27+and+serviceName+eq+%27Azure+Database+for+PostgreSQL%27+and+priceType+eq+%27Consumption%27 - Locator: General Purpose Ddsv5 Series Compute, 2/4/8 vCore; Flex Server Storage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:cost-fx ECB euro reference rate history. The 2026-10-20 reference rates are EUR 1 = USD 1.1215 and CHF 0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20; USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### librechat:librechat:cost-model OpenAI API pricing. 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. - URL: https://developers.openai.com/api/docs/pricing - Locator: Standard, short-context gpt-6-luna row - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### librechat:librechat:cost-effort GPT-6 Luna model documentation. The model accepts reasoning effort none, the lowest documented effort, and lists the same standard text-token rates. - URL: https://developers.openai.com/api/docs/models/gpt-6-luna - Locator: Reasoning effort and text-token pricing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swisscom-assistant:swisscom-assistant:ecb-fx ECB euro foreign exchange reference rates, 20 October 2026. ECB records EUR 1 = USD 1.1215 and CHF 0.9237 on 20 October 2026; derived USD to EUR is 1/1.1215 and CHF to EUR is 1/0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time="2026-10-20": USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### librechat:librechat:export-pin LibreChat conversation export implementation. The pinned user conversation exporter supports JSON, CSV, Markdown and text, plus screenshot export. - URL: https://raw.githubusercontent.com/LibreChat-AI/LibreChat/e8f3be08623663d4ad7f7241e693c94469b63bb0/client/src/hooks/Conversations/useExportConversation.ts - Locator: client/src/hooks/Conversations/useExportConversation.ts, export dispatch - Evidence kind: source-inspected - Source date: Not stated - Retrieved: 2026-10-21 - Commit: e8f3be08623663d4ad7f7241e693c94469b63bb0 - Path: client/src/hooks/Conversations/useExportConversation.ts