--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/librechat-vs-swissgpt/" data_url: "https://onaihq.com/compare/agents/librechat-vs-swissgpt/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 AlpineAI / SwissGPT > 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. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. 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. - AlpineAI / SwissGPT source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/librechat-vs-swissgpt/ - Machine-readable JSON: https://onaihq.com/compare/agents/librechat-vs-swissgpt/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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial AlpineAI names Mistral Large 3 as its primary model and says it operates all models itself in Switzerland. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - The FAQ does not enumerate all models, expose a per-chat picker, explain routing visibility or map multimodal inputs to models. - providers — Which model providers are available? [partial]: Mistral is the named current provider. Other providers are not enumerated. Sources: swissgpt:swissgpt:product. - current_models — Which current models are selectable on this plan? [partial]: Mistral Large 3 is named as the primary model; this does not establish a user-selectable catalogue. Sources: swissgpt:swissgpt:product. - user_choice — Can users pick the model per chat? [unknown]: Can users pick the model per chat? Unknown. The FAQ does not enumerate all models, expose a per-chat picker, explain routing visibility or map multimodal inputs to models. - 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. The FAQ does not enumerate all models, expose a per-chat picker, explain routing visibility or map multimodal inputs to models. - multimodal_input — Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. The FAQ does not enumerate all models, expose a per-chat picker, explain routing visibility or map multimodal inputs to models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial AlpineAI says it hosts open models on its own Swiss hardware. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Customer-hosted chat and embedding routes, supported runtimes and their feature parity are not documented in the reviewed current offer. - self_hosted_chat — Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? Unknown. Customer-hosted chat and embedding routes, supported runtimes and their feature parity are not documented in the reviewed current offer. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. Customer-hosted chat and embedding routes, supported runtimes and their feature parity are not documented in the reviewed current offer. - feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. Customer-hosted chat and embedding routes, supported runtimes and their feature parity are not documented in the reviewed current offer. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [supported]: The vendor identifies Mistral Large 3 as its current primary open model, operated on AlpineAI-owned hardware in Switzerland without foreign model APIs. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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 #### AlpineAI / SwissGPT 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. ## 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Document upload is advertised for assistants and chat. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. - formats — Which formats are accepted? [partial]: PDF, Word, text and Excel are named across the product and sector pages. This is not an exhaustive format matrix. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:university. - limits — What size and count limits apply per file and chat? [unknown]: What size and count limits apply per file and chat? Unknown. The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. - spreadsheets — Are Excel tables read with structure intact? [unknown]: Are Excel tables read with structure intact? Unknown. The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. - 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. The published 50-document/100 MB assistant limit does not define per-file and per-chat limits. OCR, embedded images, formula/table fidelity and full-file versus chunked processing need technical documentation or the shared upload fixture. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:university ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Standard and Premium include document-backed assistants with published collection limits. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - User/group/organisation sharing and Enterprise collection limits are not specified. The wording does not clearly distinguish per-file from aggregate 100 MB. - persistent_collections — Can users keep document collections across chats? [supported]: Assistants retain their own reference-document workspace for later questions. Sources: swissgpt:swissgpt:product. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [unknown]: Can collections be shared with users, groups or the whole organisation? Unknown. User/group/organisation sharing and Enterprise collection limits are not specified. The wording does not clearly distinguish per-file from aggregate 100 MB. - size_limits — What are the collection limits? [partial]: Standard has 2 assistants and Premium 5; each is listed as 50 documents / max. 100 MB. Enterprise limits are not published. Sources: swissgpt:swissgpt:university. - assistant_binding — Can collections be bound to an assistant? [supported]: Users place documents in an assistant workspace and questions use those sources. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:university ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise sector pages name production REST integrations with eGeKo and five healthcare systems. A public standard connector matrix for M365, Google, Atlassian and on-premise sources remains unverified. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - The production integration names are vendor claims on the sector pages, not a tested connector inventory. - Individual integrations require the Enterprise package from 10 licences; no API account, customer deployment or fixture was accessed. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [unknown]: Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? Unknown. The current FAQ does not identify shipped SharePoint, OneDrive, Outlook-search, Teams, Google, Atlassian or on-prem-source connectors, their consent scopes or maintainers. The Outlook add-in is recorded under WORK-02. Rechecked 2026-10-26 in AlpineAI product, public-administration and healthcare feature/licence FAQs and Security page. No extra technical/admin documentation was identified in official links or targeted first-party searches; no account fixture was run. - google_workspace — Which Google sources are connected? [unknown]: Which Google sources are connected? Unknown. The current FAQ does not identify shipped SharePoint, OneDrive, Outlook-search, Teams, Google, Atlassian or on-prem-source connectors, their consent scopes or maintainers. The Outlook add-in is recorded under WORK-02. Rechecked 2026-10-26 in AlpineAI product, public-administration and healthcare feature/licence FAQs and Security page. No extra technical/admin documentation was identified in official links or targeted first-party searches; no account fixture was run. - atlassian — Confluence and Jira? [unknown]: Confluence and Jira? Unknown. The current FAQ does not identify shipped SharePoint, OneDrive, Outlook-search, Teams, Google, Atlassian or on-prem-source connectors, their consent scopes or maintainers. The Outlook add-in is recorded under WORK-02. Rechecked 2026-10-26 in AlpineAI product, public-administration and healthcare feature/licence FAQs and Security page. No extra technical/admin documentation was identified in official links or targeted first-party searches; no account fixture was run. - other_systems — Which other business systems? [partial]: The public-administration FAQ names eGeKo as an integration in production. The healthcare FAQ names Axenita, Aeskulap, Ines, Logival and Mediway as production integrations through the AlpineAI REST API. Individual integrations are part of Enterprise from 10 licences and planned with the customer IT team. Public consent scopes, per-system configuration and a self-service connector matrix are not supplied. Sources: swissgpt:swissgpt:public-pricing-20261026, swissgpt:swissgpt:health-pricing-20261026. - on_prem_sources — Can on-prem file shares or databases be connected? [unknown]: Can on-prem file shares or databases be connected? Unknown. The current FAQ does not identify shipped SharePoint, OneDrive, Outlook-search, Teams, Google, Atlassian or on-prem-source connectors, their consent scopes or maintainers. The Outlook add-in is recorded under WORK-02. Rechecked 2026-10-26 in AlpineAI product, public-administration and healthcare feature/licence FAQs and Security page. No extra technical/admin documentation was identified in official links or targeted first-party searches; no account fixture was run. - connector_provider — Who builds and maintains each connector? [partial]: AlpineAI plans custom Enterprise integrations with the institution IT team. The university FAQ mentions expanding prebuilt connectors without naming them. Sources: swissgpt:swissgpt:university. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:public-pricing-20261026, swissgpt:swissgpt:health-pricing-20261026, swissgpt:swissgpt:product-20261026, swissgpt:swissgpt:security-20261026 ### 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The vendor describes source citations in Listener transcript search; retrieval accuracy was not tested. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - No shared corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. - citations — Are answers linked to specific sources? [partial]: The Listener FAQ advertises full-text search with source references over transcribed recordings. General document-RAG citation coverage is unspecified. Sources: swissgpt:swissgpt:product. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. - 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 corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. - 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 corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared corpus was loaded. Citation correctness, cross-language retrieval, refusal behaviour and observed question-set accuracy remain unmeasured. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Users can create document-backed assistants and use prompt templates. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Creator restrictions, sharing boundaries, versioning, tool configuration and an organisation-managed directory are not established in the public pages. - create_assistants — Can users create assistants with instructions, knowledge and tools? [partial]: Users create workspaces with their own reference documents; configurable instructions and external tools are not described. Sources: swissgpt:swissgpt:product. - creator_permissions — Can admins limit who creates them? [unknown]: Can admins limit who creates them? Unknown. Creator restrictions, sharing boundaries, versioning, tool configuration and an organisation-managed directory are not established in the public pages. - sharing_scope — Can assistants be shared with users, groups or everyone? [unknown]: Can assistants be shared with users, groups or everyone? Unknown. Creator restrictions, sharing boundaries, versioning, tool configuration and an organisation-managed directory are not established in the public pages. - catalogue — Is there an internal assistant directory? [partial]: Premium adds preconfigured assistants; an organisation directory is not established. Sources: swissgpt:swissgpt:product. - prompt_library — Are shared prompt templates available? [partial]: Chat includes prompt templates for recurring tasks; shared-team template administration is not specified. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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 #### AlpineAI / SwissGPT 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. ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web search is included but requires organisation activation and user consent; queries can leave AlpineAI infrastructure. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Group-specific controls, a multi-step research/report mode and general web citation behaviour are not documented. - web_search — Is web search available? [supported]: Included across licence models and optional at use time. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:terms. - admin_toggle — Can admins disable it per organisation or group? [supported]: Administrator must enable the instance; can disable it instance-wide. Users consent per search and again for detected sensitive content. Sources: swissgpt:swissgpt:terms. - search_provider — Which search provider handles queries, and where? [supported]: DPA Annex 3 names Brave Software, Inc., US, for Brave Search API; activated search sends query/chat content outside AlpineAI infrastructure. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms. - deep_research — Is multi-step research with a report available? [unknown]: Is multi-step research with a report available? Unknown. Group-specific controls, a multi-step research/report mode and general web citation behaviour are not documented. - web_citations — Are web sources cited? [unknown]: Are web sources cited? Unknown. Group-specific controls, a multi-step research/report mode and general web citation behaviour are not documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:terms, swissgpt:swissgpt:dpa ### 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 #### AlpineAI / SwissGPT 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. ### 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 #### AlpineAI / SwissGPT 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. ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A separate AlpineAI API platform is advertised. Custom application integrations are explicitly offered under Enterprise from 10 licences; standalone API entitlement remains unknown and new accounts are activated gradually. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI API platform; version=not specified; plan=Enterprise custom application integrations from 10 licences; standalone API tariff/entitlement not established; add_ons=Individually contracted integration; API account activation required; deployment_mode=not specified; region=API portal advertises Swiss processing; endpoint-specific processing and contractual entitlement unverified; os=not specified. Limitations: - Enterprise custom integration is documented; a universal API entitlement across chat licence tiers is not. - No authenticated endpoint documentation, API account, rate-limit data or governance fixture was accessed. - chat_api — Is there an API for chat and assistants? [partial]: The product page describes requests/results through its separate API platform and explicitly places custom integrations in Enterprise. The public API landing page supports REST/SDK positioning but requires sign-in and gradual account activation. Specific chat/assistant endpoints, auth methods, standalone licensing and inclusion in Standard/Premium were not verified. Sources: swissgpt:swissgpt:review2-product, swissgpt:swissgpt:review2-api-access, swissgpt:swissgpt:university. - knowledge_api — Can documents be loaded through an API? [unknown]: No unauthenticated document-ingestion endpoint reference was retrieved from the API portal; naming general integrations is not proof of an ingestion API. - api_governance — Do audit, budgets and model rules apply to API use? [unknown]: The API landing page advertises monitoring of usage and costs, but scope of chat audit, budgets and model rules for API calls was not established without authenticated documentation. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: No AlpineAI-provided MCP server exposing the product to external agents was documented in the retrieved product or API landing pages. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:review2-product, swissgpt:swissgpt:review2-api-access, swissgpt:swissgpt:university ## 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The FAQ lists web and iOS/Android access. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI iOS and Android apps; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland; mobile clients on user devices; os=iOS, Android. Limitations: - Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. - web — Is a full web client available? [supported]: Works in Chrome, Firefox, Safari or Edge on internet-connected computers and mobile devices. Sources: swissgpt:swissgpt:product. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. - mobile_apps — iOS and Android apps with SSO? [partial]: iOS and Android apps are advertised; company SSO in those apps was not verified. Sources: swissgpt:swissgpt:product. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. Desktop OS support is only package-dependent in AGB 2.1. Browser extension, MDM/Intune deployment and mobile parity are not documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Standard and Premium include an Outlook add-in for reading, drafting and translating email. Availability: generally-available Delivery: official-integration Scope: surfaces=AlpineAI Outlook add-in; version=not specified; plan=Standard and Premium; Enterprise packaging unspecified; add_ons=none stated; deployment_mode=not specified; region=Content processed on AlpineAI hardware in Switzerland; os=not specified. Limitations: - Word, Excel, PowerPoint, Teams and Google application integrations are not specified. Outlook add-in consent and compatibility requirements remain unverified. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Unknown. Word, Excel, PowerPoint, Teams and Google application integrations are not specified. Outlook add-in consent and compatibility requirements remain unverified. - outlook — Does it work inside Outlook? [supported]: Add-in summarises messages/threads, drafts replies and translates within Outlook. The FAQ describes Get Add-Ins installation. Sources: swissgpt:swissgpt:product. - teams — Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. Word, Excel, PowerPoint, Teams and Google application integrations are not specified. Outlook add-in consent and compatibility requirements remain unverified. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Word, Excel, PowerPoint, Teams and Google application integrations are not specified. Outlook add-in consent and compatibility requirements remain unverified. - licence_prerequisites — Which licences or consents are needed? [partial]: Included with Standard and Premium. Microsoft licence/version prerequisites and tenant consent requirements are not stated. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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. #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform and Outlook add-in offer drafting, summaries and translations. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Unknown. Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - translation_engine — Which engine translates? [unknown]: Which engine translates? Unknown. Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? Unknown. Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Whole-document layout preservation, a dedicated translation engine, company glossaries, formality and de-CH controls were not specified or tested. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: The FAQ advertises drafting and replying to email, summaries and translations into Swiss national languages and English. Proofreading controls are not detailed. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Premium Listener records audio, transcribes Swiss German and creates minutes or summaries. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI iOS and Android apps; version=not specified; plan=Premium Listener; Enterprise inclusion per order; add_ons=none stated; deployment_mode=not specified; region=Audio processing on AlpineAI-owned hardware in Switzerland; os=not specified. Limitations: - Read-aloud and live bidirectional voice conversation are undocumented; recognition quality was not independently tested. - dictation — Can users dictate prompts? [partial]: Listener records dictation through the microphone and accepts existing audio files. Direct dictation into a chat prompt was not established. Sources: swissgpt:swissgpt:product. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. Read-aloud and live bidirectional voice conversation are undocumented; recognition quality was not independently tested. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Read-aloud and live bidirectional voice conversation are undocumented; recognition quality was not independently tested. - meeting_summaries — Are meetings transcribed and summarised? [supported]: Advertises complete transcripts and structured minutes, summaries, key facts and to-dos; recordings process on AlpineAI hardware in Switzerland. Sources: swissgpt:swissgpt:product. - swiss_german_speech — Is Swiss German speech recognised? [supported]: Vendor claims Swiss German and other dialect recognition, with transcript output in German, English, French or Italian. Sources: swissgpt:swissgpt:product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:product ### 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Terms specify a German and English interface; language quality was not observed. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - No authenticated German/French/Italian UI review, WCAG conformance statement or German admin-interface specification was located. - ui_languages — Which UI languages are offered? [partial]: AGB 2.1 explicitly names German and English UI. Sector pages advertise processing of Swiss national languages and English; that does not establish French/Italian UI coverage. Sources: swissgpt:swissgpt:terms. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No authenticated German/French/Italian UI review, WCAG conformance statement or German admin-interface specification was located. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated German/French/Italian UI review, WCAG conformance statement or German admin-interface specification was located. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated German/French/Italian UI review, WCAG conformance statement or German admin-interface specification was located. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:terms ## 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 #### AlpineAI / SwissGPT 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-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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web search has a sensitive-content consent step; general PII/DLP handling is unverified. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Custom patterns, external DLP integration, detection coverage and filter location are not documented; no AHV/IBAN fixture was used. - pii_detection — Is personal data detected in prompts and files? [partial]: AGB 2.5 says the system can detect potentially sensitive search-query content; it does not specify personal-data types or uploaded-file detection. Sources: swissgpt:swissgpt:terms. - pii_action — Is it redacted, masked, blocked or only warned? [partial]: Detected potentially sensitive web-search content requires renewed user consent before transmission. Redaction or blocking is not established. Sources: swissgpt:swissgpt:terms. - custom_patterns — Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. Custom patterns, external DLP integration, detection coverage and filter location are not documented; no AHV/IBAN fixture was used. - dlp_integration — Does it integrate with an existing DLP product? [unknown]: Does it integrate with an existing DLP product? Unknown. Custom patterns, external DLP integration, detection coverage and filter location are not documented; no AHV/IBAN fixture was used. - filter_location — Where does filtering run? [unknown]: Where does filtering run? Unknown. Custom patterns, external DLP integration, detection coverage and filter location are not documented; no AHV/IBAN fixture was used. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:terms ### 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 #### AlpineAI / SwissGPT 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 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Swiss RIZ application hosting is consistently described. Green/RZO Swiss inference is a vendor security-page statement; a current contracted inference-site schedule is unverified because the July DPA does not list RZO. Storage, inference, support and optional search are scoped separately. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI API platform; version=Public infrastructure page and DPA Annex 3 dated 10 July 2026; no tenant contract inspected; plan=Current AlpineAI sector offer; contract-specific residency and secret-data supplement conditional on signature; add_ons=none stated; deployment_mode=not specified; region=Advertised Swiss application hosting; current contracted inference map unverified; DPA CH/EEA with conditional third-country processing and optional external search; os=not specified. Limitations: - RZO is described as colocation, not as a foreign model API. Its absence from the July annex is not evidence of overseas inference or unauthorised processing. - The currently contracted complete inference-site list, per-index/log/telemetry locations and exhaustive staff access countries remain unknown. - storage_region — Where are chats, files and indexes stored? [partial]: The security page describes application/data storage on AlpineAI hardware at two Swiss RIZ sites. July DPA Annex 3 independently lists RIZ CH for platform hosting and support. Separate per-index/log topology and a tenant-specific deployment schedule were not established. Sources: swissgpt:swissgpt:review2-security, swissgpt:swissgpt:review2-dpa. - inference_region — Where do model calls run, per provider? [unknown]: The security page names Swiss Green and RZO GPU colocation on AlpineAI-owned/operated hardware without logical access by site operators. July DPA Annex 3 names Green and expressly describes pure colocation, but omits RZO. No newer public annex or contract-specific RZO authorisation was retrieved. The currently contracted complete inference-site map is therefore unknown; the marketing statement is not a verified current contract commitment. - backups_logs_region — Where are backups, logs and telemetry? [partial]: July DPA Annex 3 lists cloudscale.ch CH for backup; Annex 2 describes daily offsite backups. This dated schedule does not establish every current log/telemetry or backup location. Sources: swissgpt:swissgpt:review2-dpa. - support_access_region — From where can vendor staff access data? [partial]: The dated annex assigns RIZ CH to customer support and EU Atlassian/Custify to helpdesk/account functions. Physical staff access countries are not fully mapped. A separately signed secret-data supplement requires Swiss services where secret data is in plaintext. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:secrecy. - swiss_hosting — Is Swiss hosting available? [partial]: Swiss application hosting at RIZ is supported by both public sources. The full current inference-site inventory is withheld pending a current applicable schedule, so this is not an all-processing CH-residency assurance. Sources: swissgpt:swissgpt:review2-security, swissgpt:swissgpt:review2-dpa. - residency_plan — Which plan or option provides residency? [partial]: DPA 1.5 permits CH/EEA processing with conditional third-country safeguards. Optional Brave search is separately listed with US processing. The secret-data supplement, only when signed and applicable, narrows plaintext services including APIs to Switzerland. A current tenant-specific inference schedule is still missing. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:secrecy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:review2-security, swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:secrecy ### 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The terms prohibit model training on customer inputs. API zero retention has a narrow signed secrecy-agreement scope. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI API platform; version=not specified; plan=Current hosted plans; zero retention only AI API services under signed secret-data supplement; add_ons=Signed supplementary agreement for legally secret data, where applicable; deployment_mode=not specified; region=CH for plaintext secret-data services; general DPA CH/EEA with conditional third countries; os=not specified. Limitations: - Ordinary-chat/provider retention and general staff-review practice outside the signed secret-data scope are not documented. DPA anonymised-data use must be read alongside the narrower no-training clause. - vendor_training — Does the vendor train on customer content? [supported]: AGB 4.4 says customer inputs do not feed back into language-model development. DPA 2.4 separately permits anonymisation and use for service/product development; this is not a blanket prohibition on every secondary use. Sources: swissgpt:swissgpt:terms, swissgpt:swissgpt:dpa. - provider_training — Do model providers train on it under this product's contracts? [partial]: Vendor says models run on AlpineAI hardware without foreign model APIs; a separate third-party model-provider training contract is not established. Sources: swissgpt:swissgpt:product. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: Signed secrecy agreement forbids storing/logging AI API input and output for secret data. Ordinary web-chat and general API retention periods are unspecified. Sources: swissgpt:swissgpt:secrecy. - zero_retention — Is zero data retention available, and on which plan? [supported]: Available contractually for AI API services processing legally secret data when the supplementary agreement is signed. It is not a general chat-history promise. Sources: swissgpt:swissgpt:secrecy. - human_review — Can provider staff review content? [supported]: For secret data under the signed supplement, plaintext access needs individual approval, unavoidable BCM emergency or a binding Swiss order; staff abuse monitoring with plaintext access is forbidden. Sources: swissgpt:swissgpt:secrecy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:terms, swissgpt:swissgpt:dpa, swissgpt:swissgpt:product, swissgpt:swissgpt:secrecy ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The DPA requires deletion after contract end with a backup-cycle exception. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Default chat/file/index/log periods, customer retention settings, permanent user deletion and the backup-cycle deadline are not specified. - default_retention — What is retained and for how long by default? [unknown]: What is retained and for how long by default? Unknown. Default chat/file/index/log periods, customer retention settings, permanent user deletion and the backup-cycle deadline are not specified. - admin_retention — Can admins set retention periods? [unknown]: Can admins set retention periods? Unknown. Default chat/file/index/log periods, customer retention settings, permanent user deletion and the backup-cycle deadline are not specified. - user_deletion — Can users delete their chats and files permanently? [unknown]: Can users delete their chats and files permanently? Unknown. Default chat/file/index/log periods, customer retention settings, permanent user deletion and the backup-cycle deadline are not specified. - contract_end_deletion — What is deleted at contract end, and when? [partial]: DPA 9.1 requires deletion of provided customer data on termination. Backup copies delete on restoration and ultimately as backup cycles expire; no cycle duration is given. AGB 7.5 offers written confirmation on request with legal-retention exceptions. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A public July 2026 DPA annex lists operational suppliers and contract notification/transfer terms. It is a dated source, not proof of the complete current provider list: RZO appears only on the security page and its current contractual status remains unknown. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI API platform; version=DPA Annex 3 dated 10 July 2026; re-retrieved 21 October 2026; plan=AlpineAI platform contracts; current tenant-specific supplier schedule not inspected; add_ons=none stated; deployment_mode=not specified; region=Dated annex CH/EU/US supplier locations; current complete country/supplier schedule unverified; os=not specified. Limitations: - No current complete provider/country schedule or RZO-specific authorisation was retrieved; no inference is made that RZO is approved, unauthorised or a separate model provider. - Ultimate ownership and supplier-specific US transfer instruments remain unknown. - subprocessor_list — Is a dated sub-processor list published? [partial]: A public Annex 3 dated 10 July 2026 is downloadable through /avv/. It includes RIZ hosting/support and Green colocation. The security page additionally names RZO. No updated public annex, RZO approval notice or tenant-specific schedule was obtained, so completeness/current applicability is unknown. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:review2-security. - subprocessor_countries — Which countries do sub-processors operate in? [partial]: The dated annex lists CH data locations for RIZ, Green, cloudscale, accounting and IT operations; EU for helpdesk/payments/customer success; US for CRM and opt-in Brave search. Green is described as rack/power/network colocation without logical access, not model-provider API processing. These are the annex entries, not an exhaustive current content-processing country map. Sources: swissgpt:swissgpt:review2-dpa. - change_notification — Are customers notified of sub-processor changes? [supported]: DPA 7.3 requires text notice of intended additions/replacements and gives 14 days for an objection supported by an important reason. No customer-specific change notice was inspected. Sources: swissgpt:swissgpt:review2-dpa. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The contracting entity is AlpineAI AG in Davos, Switzerland; ultimate parent/beneficial-owner jurisdiction was not established. Sources: swissgpt:swissgpt:imprint, swissgpt:swissgpt:terms. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [partial]: DPA 1.5 conditions third-country processing on prior written notice and adequate safeguards such as SCCs or adequacy. It does not map a particular transfer instrument to each US supplier. Sources: swissgpt:swissgpt:review2-dpa. - government_access_policy — Is there a published government-access or transparency policy? [supported]: DPA 2.1 requires notice of legally mandated processing unless prohibited. The separately signed secret-data supplement adds Swiss-order notice, challenge assistance and minimal disclosure, within its Swiss secret-data scope. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:secrecy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:review2-dpa, swissgpt:swissgpt:review2-security, swissgpt:swissgpt:imprint, swissgpt:swissgpt:terms, swissgpt:swissgpt:secrecy ### 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. #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public DPA and secrecy supplement address Swiss data protection and professional/official secrecy. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - DPA negotiability, EU AI Act provider/deployer documents and a FINMA-specific pack are not provided in the reviewed public materials. - dpa — Is a DPA available, and is it negotiable? [partial]: A public DPA applies to individuals without AlpineAI signature; companies may obtain a countersigned copy. Negotiation rights are not established. Sources: swissgpt:swissgpt:dpa. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [supported]: DPA expressly cites Art. 9 Swiss DSG and Art. 28 GDPR and defines controller/processor roles. Sources: swissgpt:swissgpt:dpa. - governing_law — Which law and court govern the contract? [supported]: DPA 11.4 specifies Swiss law and exclusive Zürich jurisdiction; AGB 11.4 preserves AlpineAI rights to sue elsewhere. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? Unknown. DPA negotiability, EU AI Act provider/deployer documents and a FINMA-specific pack are not provided in the reviewed public materials. - sector_materials — Are FINMA or other sector materials provided? [partial]: Public signed supplement covers legally secret data including official/professional secrecy, CH plaintext services and annual assurance evidence. No FINMA-specific outsourcing dossier was located. Sources: swissgpt:swissgpt:secrecy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:terms, swissgpt:swissgpt:secrecy ### 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. #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial AlpineAI claims ISO 27001:2022 and VDSZ issued by SQS; certificates were not inspected. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - No issuer certificate or full report was obtained. ISO/VDSZ validity and scope, SOC 2 type/period, C5 and independent penetration-test summary remain unverified. - iso_27001 — ISO 27001 with scope and validity? [partial]: Vendor identifies AlpineAI AG, SQS and ISO 27001:2022. Certificate scope and validity were not retrieved, so this remains vendor-claimed. Sources: swissgpt:swissgpt:security. - soc2 — SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. No issuer certificate or full report was obtained. ISO/VDSZ validity and scope, SOC 2 type/period, C5 and independent penetration-test summary remain unverified. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No issuer certificate or full report was obtained. ISO/VDSZ validity and scope, SOC 2 type/period, C5 and independent penetration-test summary remain unverified. - other_certifications — Which other certificates (27701, 42001, TISAX)? [partial]: Vendor claims VDSZ, issued by SQS. No certificate number, scope or expiry was retrieved. Sources: swissgpt:swissgpt:security. - report_access — How can customers obtain reports? [supported]: DPA 6.1 permits documentary assurance such as ISO records/internal audits; signed secret-data supplement promises annual certification/report covering the processing without extra charge. Sources: swissgpt:swissgpt:dpa, swissgpt:swissgpt:secrecy. - pentest — Are independent penetration test summaries available? [partial]: DPA Annex 2 promises regular penetration testing; independence and a public summary are not established. Sources: swissgpt:swissgpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:security, swissgpt:swissgpt:dpa, swissgpt:swissgpt:secrecy ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The vendor describes AES-256 at rest, TLS in transit and isolation on its own hardware. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Customer-managed or customer-held keys, key location, customer private connectivity and technical tenant-isolation model remain unspecified. - encryption_at_rest — Is data encrypted at rest? [supported]: Security page names AES-256 at rest and TLS between clients and platform; DPA Annex 2 requires encryption. Sources: swissgpt:swissgpt:security, swissgpt:swissgpt:dpa. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. Customer-managed or customer-held keys, key location, customer private connectivity and technical tenant-isolation model remain unspecified. - private_networking — Is private connectivity or IP restriction available? [partial]: GPU partners are described as VPN-only infrastructure. A customer Private Link, VPN or IP allow-list option is not established. Sources: swissgpt:swissgpt:security. - tenant_isolation — How are customers separated in shared SaaS? [partial]: Vendor claims isolated/private-cloud environments and least-privilege RBAC. Exact shared-SaaS tenant separation and single-tenancy guarantees are not documented. Sources: swissgpt:swissgpt:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:security, swissgpt:swissgpt:dpa ### DATA-09: Professional secrecy Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment. #### LibreChat 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial AlpineAI publishes a separate bilateral undertaking for Swiss official, professional and other statutory secret data. It binds staff and subcontractors, restricts plaintext access and requires Swiss plaintext services when signed. Plan eligibility, any supplement fee and German § 203 coverage remain unverified. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client, AlpineAI API platform; version=Supplement printed 30 March 2026; plan=AlpineAI platform under a signed main contract and supplementary secrecy agreement; eligible plan tiers unpublished; add_ons=Signed supplementary secrecy agreement; price unpublished; deployment_mode=not specified; region=Swiss statutory secrecy; services exposing secret data in plaintext, including APIs, exclusively in Switzerland; os=not specified. Limitations: - The supplement is conditional on both signatures and processing Swiss legally secret data. Its Swiss Art. 320 ff. reference is not evidence of a German § 203 agreement or a legal suitability assessment for a particular profession. - Plan eligibility, any supplement fee, executed customer agreements and the actual downstream staff/subcontractor agreements remain unverified. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [supported]: The public two-party signature template supplements the platform main contract and DPA. It takes effect on the last signature and only while the customer processes data subject to Swiss official, professional or other statutory secrecy (example: Art. 320 ff. Swiss StGB). Section 3 requires equivalent contractual obligations for AlpineAI staff who may access plaintext. This establishes a published undertaking for signature, not an inspected executed customer agreement or an express German § 203 instrument. Sources: swissgpt:swissgpt:secrecy. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [supported]: Section 3 requires AlpineAI to impose at least equivalent contractual obligations on its subcontractors and staff who may access secret data in plaintext. The DPA safeguards also apply to secret data, with the stronger secrecy supplement taking priority. Actual downstream signed agreements were not public and were not inspected. Sources: swissgpt:swissgpt:secrecy. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [partial]: The security page offers corporate customers an additional secrecy agreement; the public template is separate from the main contract and DPA and requires both parties to sign. No named eligible package, paid add-on tariff or general supplement fee was established. The annual assurance evidence is promised without extra cost, which does not establish that the agreement itself is free. Sources: swissgpt:swissgpt:security, swissgpt:swissgpt:secrecy. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [supported]: Under the signed supplement, AlpineAI and subcontractor staff may access plaintext only on a need-to-know basis plus individual prior customer approval, an unavoidable urgent business-continuity emergency, or a binding Swiss authority order. AlpineAI must take reasonable measures to prevent third-party plaintext access. AI API inputs and outputs must not be stored or logged, human abuse monitoring with plaintext access is prohibited, and plaintext services including APIs must remain in Switzerland. The security page separately says AlpineAI operates the models and colocation providers have no logical access to systems or data. These are contract terms and vendor disclosures, not a hands-on verification of every data flow. Sources: swissgpt:swissgpt:secrecy, swissgpt:swissgpt:security. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [supported]: A public two-page contract template, printed 30 March 2026, sets scope, precedence, secrecy duties, staff/subcontractor flow-down, plaintext access, Swiss processing, API retention and signature blocks. Section 3 also promises annual assurance evidence covering secret-data processing at no extra cost and a customer audit right at customer expense. The security page explains the supplementary agreement. No executed customer contract was inspected. Sources: swissgpt:swissgpt:secrecy, swissgpt:swissgpt:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:secrecy, swissgpt:swissgpt:security ## 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Prices differ by sector and billing period; Enterprise is quoted from 10 licences. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Enterprise rates, VAT treatment, university monthly-toggle verification, model/search quotas, overage prices and integration charges are not established. Do not treat the annual default shown by text extraction as monthly billing. - pricing_unit — What is the pricing unit? [supported]: Standard/Premium price per individual user licence. Enterprise package starts at 10 licences. Sources: swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-pricing, swissgpt:swissgpt:university. - list_prices — What are list prices per plan, with date and currency? [partial]: As retrieved 2026-10-21: administration Standard/Premium CHF 79/89 per user/month with monthly billing, CHF 74/80 per month with annual billing. Healthcare CHF 89/99 monthly or CHF 80/90 per month annual. University page displays annual CHF 74/80; monthly amounts were not independently toggled. Tax inclusion is not stated clearly, so no ex-VAT conversion is asserted. Sources: swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-pricing, swissgpt:swissgpt:university. - included_usage — What usage is included? [partial]: Standard has chat/search, uploads, Outlook and 2 assistants; Premium adds Listener, prebuilt assistants and 5 assistants, each listed at 50 documents / max. 100 MB. General inference/search token allowances are not published. Sources: swissgpt:swissgpt:university. - add_ons — Which features cost extra? [partial]: Premium adds Listener and preconfigured assistants; Enterprise covers custom integrations. AGB 2.3 permits charges for new major functionality; numeric integration/service fees are unspecified. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms. - overage — What do usage beyond limits and premium models cost? [unknown]: What do usage beyond limits and premium models cost? Unknown. Enterprise rates, VAT treatment, university monthly-toggle verification, model/search quotas, overage prices and integration charges are not established. Do not treat the annual default shown by text extraction as monthly billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-pricing, swissgpt:swissgpt:university, swissgpt:swissgpt:terms ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21. The required 200, 1,000 and 5,000-seat annual scenarios cannot be priced from the public individual plans. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; 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]: Enterprise applies from 10 licences and is quote-only; fixed package, usage, integrations, service charges and tax treatment remain unknown. No sales quote was requested. Sources: swissgpt:swissgpt:university. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt: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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Sector pages offer online free tests; Enterprise evaluation scope is not published. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - A permanent business free tier, trial duration/card requirements, Enterprise SSO/admin/connector coverage and fixture access are not established. - free_tier — Is there a free tier for business use? [unknown]: Is there a free tier for business use? Unknown. A permanent business free tier, trial duration/card requirements, Enterprise SSO/admin/connector coverage and fixture access are not established. - self_serve_trial — Is a self-serve business trial available? [partial]: Standard/Premium pages link free testing through Stripe and AGB 3.1 allows self-registration. Trial duration, card requirement and quotas were not verified. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms. - trial_scope — Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? Unknown. A permanent business free tier, trial duration/card requirements, Enterprise SSO/admin/connector coverage and fixture access are not established. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Individual plans can be purchased by self-registration; the Enterprise integration offer routes to consultation. No account or sales contact was used. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Small plans renew monthly or yearly; Enterprise starts at 10 licences with quoted terms. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Seat-reduction/downgrade timing, future price-change rules, EUR invoicing and complete Enterprise commitments are not specified. - minimum_commitment — What seat or spend minimum applies? [supported]: Standard/Premium cover up to 9 individual licences; Enterprise starts at 10. Sources: swissgpt:swissgpt:university. - contract_length — What contract lengths are offered? [supported]: AGB 3.1 defaults to one calendar month or twelve months with renewal for the same term; an order may set other terms. Sources: swissgpt:swissgpt:terms. - cancellation — How can the contract be cancelled or reduced? [partial]: Either party may cancel for term end through the platform where available or support; prepaid fees are not refunded. Downgrade rules are not specified. Sources: swissgpt:swissgpt:terms. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Prices are displayed in CHF and AlpineAI AG is Swiss. Standard offers use credit card; invoices can be offered case by case with 14-day payment. EUR invoicing is unverified. Sources: swissgpt:swissgpt:terms, swissgpt:swissgpt:public-pricing. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified individual-sector prices; quote-only Enterprise from 10 licences. Public prices do not establish tax or all usage/service charges. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms, swissgpt:swissgpt:public-pricing, swissgpt:swissgpt:health-pricing ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Terms grant a contractual right to use a proprietary platform. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Component licences, branding or user-count restrictions beyond purchased licences, and a separate enterprise source edition are not published. No public implementation repository was identified. - licence_type — Which licence applies to each component? [supported]: AGB 4.1-4.3 grants non-exclusive, non-transferable access during the contract and reserves platform software, algorithms, documentation and branding rights to AlpineAI. Open-model use is separate. Sources: swissgpt:swissgpt:terms. - branding_restrictions — Do licence terms restrict branding or user counts? [unknown]: Do licence terms restrict branding or user counts? Unknown. Component licences, branding or user-count restrictions beyond purchased licences, and a separate enterprise source edition are not published. No public implementation repository was identified. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. Component licences, branding or user-count restrictions beyond purchased licences, and a separate enterprise source edition are not published. No public implementation repository was identified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:terms ### 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 #### AlpineAI / SwissGPT 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Support uses a service portal and email fallback; terms promise 99% availability. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - DE/FR/IT support guarantees, support hours, response times, SLA credits and an official public status/incident history were not located. - support_channels — Which support channels are available on each plan? [supported]: Service Desk/email is listed in sector plans. AGB 9.2 requires support-portal tickets, with email when the portal is technically unreachable. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. DE/FR/IT support guarantees, support hours, response times, SLA credits and an official public status/incident history were not located. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: AlpineAI AG lists a Davos, Switzerland address. Sources: swissgpt:swissgpt:imprint. - uptime_sla — Is there an uptime SLA with credits? [partial]: AGB 9.1 promises 99% availability during the licence term with planned/urgent maintenance exceptions. No credit schedule or response-time commitment was located. Sources: swissgpt:swissgpt:terms. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? Unknown. DE/FR/IT support guarantees, support hours, response times, SLA credits and an official public status/incident history were not located. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:terms, swissgpt:swissgpt:imprint ### 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 #### AlpineAI / SwissGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Sector offers describe guided rollout, workshops and a six-lesson e-learning course. Availability: generally-available Delivery: native Scope: surfaces=AlpineAI platform browser client; version=not specified; plan=Standard and Premium, up to 9 licences; Enterprise from 10 licences. Current healthcare, public-administration and university offer.; add_ons=none stated; deployment_mode=not specified; region=Switzerland infrastructure; contract permits CH/EEA and conditional third-country processing; optional external web search; os=not specified. Limitations: - Champion programmes, training languages, mandatory onboarding scope and separate professional-service charges are not published. - onboarding_service — Is guided onboarding included? [partial]: University and healthcare pages offer implementation help and onsite team training; inclusion in licence price is not stated. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:health-pricing. - user_training — Is end-user training offered, in which languages? [partial]: Six e-learning lessons and prompting/use-case workshops are offered; delivery languages are not specified. Sources: swissgpt:swissgpt:product, swissgpt:swissgpt:university. - use_case_library — Are role-based use cases and templates provided? [supported]: Sector pages describe university, authority and healthcare use cases; Premium adds preconfigured assistants. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:product. - adoption_programme — Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Unknown. Champion programmes, training languages, mandatory onboarding scope and separate professional-service charges are not published. - service_cost — Which services cost extra? [unknown]: Which services cost extra? Unknown. Champion programmes, training languages, mandatory onboarding scope and separate professional-service charges are not published. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: swissgpt:swissgpt:university, swissgpt:swissgpt:health-pricing, swissgpt:swissgpt:product ## 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 ### swissgpt:swissgpt:product AlpineAI product and FAQ. Describes browser and mobile access, Mistral Large 3 on AlpineAI hardware, document assistants, Outlook, Listener and Enterprise integrations. - URL: https://alpineai.swiss/produkt/ - Locator: Chat; Assistants; Listener; FAQs on models, Outlook, licences - 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 ### 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 ### swissgpt:swissgpt:university AlpineAI universities. Lists licence limits and Enterprise threshold, university integration process and onboarding. - URL: https://alpineai.swiss/en/universities/ - Locator: Prices; Integration & Licenses; Features & Languages - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### swissgpt:swissgpt:product-20261026 AlpineAI product and FAQ. Describes browser and mobile access, Mistral Large 3 on AlpineAI hardware, document assistants, Outlook, Listener and Enterprise integrations. - URL: https://alpineai.swiss/produkt/ - Locator: Chat; Assistants; Listener; FAQs on models, Outlook, licences - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-26 ### swissgpt:swissgpt:security-20261026 AlpineAI security and compliance. Separates RIZ application hosting from Green and RZO inference and describes encryption, access restrictions and external-search opt-in. - URL: https://alpineai.swiss/sicherheit/ - Locator: Infrastructure; isolation; encryption; security FAQ - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-26 ### swissgpt:swissgpt:public-pricing-20261026 AlpineAI authorities and institutions. Monthly billing is CHF 79 Standard or CHF 89 Premium per user; annual billing displays CHF 74 or CHF 80 per month; Enterprise is quoted from 10 licences. - URL: https://alpineai.swiss/behoerden/ - Locator: Prices; pricing-toggle applyMode(monthly/yearly) and billing labels in delivered HTML - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### swissgpt:swissgpt:health-pricing-20261026 AlpineAI healthcare. Healthcare monthly billing is CHF 89 Standard or CHF 99 Premium per user; annual billing displays CHF 80 or CHF 90 per month. - URL: https://alpineai.swiss/gesundheitswesen/ - Locator: Prices; pricing-toggle applyMode(monthly/yearly) and billing labels in delivered HTML - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### 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 ### 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 ### swissgpt:swissgpt:terms AlpineAI general terms. Defines cloud licensing, no-training promise, web-search consent and quotas, subscription cancellation, 99 percent availability and Swiss law. - URL: https://alpineai.swiss/agb/ - Locator: Sections 2.1-2.5, 3, 4, 7.5, 9 and 11 - Evidence kind: documented - Source date: 2026-05-25 - Retrieved: 2026-10-21 ### swissgpt:swissgpt:dpa AlpineAI data processing agreement. Sets CH/EEA processing with a third-country exception, anonymised-data use, deletion and backup exception, safeguards and a dated subprocessor list. - URL: https://alpineai.swiss/wp-content/uploads/2026/07/AlpineAI-AVV_zu_GTC_2026-07-10.pdf - Locator: Pages 1-4 sections 1.5, 2.4, 7, 9 and 11; pages 6-7 Annexes 2-3 - Evidence kind: documented - Source date: 2026-07-10 - 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 ### swissgpt:swissgpt:review2-product AlpineAI product and FAQ. The product page assigns Standard/Premium to assistants, not autonomous agents; it explicitly assigns custom integrations to Enterprise. - URL: https://alpineai.swiss/produkt/ - Locator: Integrations; Assistants & Agents; Operations & Licences - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:review2-api-access AlpineAI API platform. Public API portal redirects to authentication and states that access is limited with gradual account activation; no authenticated endpoint/entitlement documentation was accessed. - URL: https://platform.prod.alpineai.ch/ - Locator: Authentication landing page; limited access notice - 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 ### 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 ### swissgpt:swissgpt:secrecy AlpineAI supplementary agreement for secret data. When signed for legally secret data, requires Swiss plaintext services, restricted access and zero prompt/response retention for AI API services. - URL: https://alpineai.swiss/wp-content/uploads/2026/03/AlpineAI_Zusatzvereinbarung_Geheimnisdaten.2025-03-30-1.pdf - Locator: Printed version 30 March 2026; section 3 on both pages - Evidence kind: documented - Source date: 2026-03-30 - Retrieved: 2026-10-21 ### swissgpt:swissgpt:review2-security AlpineAI security and compliance. Security page describes RIZ application hosting and Green/RZO inference as colocation on AlpineAI-owned/operated hardware, without logical access by site operators. This is a vendor infrastructure disclosure, not an updated DPA schedule. - URL: https://alpineai.swiss/sicherheit/ - Locator: Certified infrastructure; FAQ on storage and processing - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:review2-dpa AlpineAI data processing agreement. Re-retrieved July 10 Annex 3 lists RIZ hosting/support and Green pure colocation with no logical data access, plus CH/EU/US operational suppliers; RZO is not listed. No newer public schedule or RZO approval was retrieved. - URL: https://alpineai.swiss/wp-content/uploads/2026/07/AlpineAI-AVV_zu_GTC_2026-07-10.pdf - Locator: Annex 3 page 7, dated 10 July 2026; section 1.5 and 7.3 - Evidence kind: documented - Source date: 2026-07-10 - 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 ### swissgpt:swissgpt:imprint AlpineAI imprint. Identifies AlpineAI AG at Obere Strasse 22b in Davos, Switzerland. - URL: https://alpineai.swiss/impressum/ - Locator: Address - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:security AlpineAI security and compliance. Separates RIZ application hosting from Green and RZO inference and describes encryption, access restrictions and external-search opt-in. - URL: https://alpineai.swiss/sicherheit/ - Locator: Infrastructure; isolation; encryption; security FAQ - Evidence kind: vendor-claimed - Source date: Not stated - 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 ### swissgpt:swissgpt:public-pricing AlpineAI authorities and institutions. Monthly billing is CHF 79 Standard or CHF 89 Premium per user; annual billing displays CHF 74 or CHF 80 per month; Enterprise is quoted from 10 licences. - URL: https://alpineai.swiss/behoerden/ - Locator: Prices; pricing-toggle applyMode(monthly/yearly) and billing labels in delivered HTML - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### swissgpt:swissgpt:health-pricing AlpineAI healthcare. Healthcare monthly billing is CHF 89 Standard or CHF 99 Premium per user; annual billing displays CHF 80 or CHF 90 per month. - URL: https://alpineai.swiss/gesundheitswesen/ - Locator: Prices; pricing-toggle applyMode(monthly/yearly) and billing labels in delivered HTML - Evidence kind: documented - Source date: Not stated - 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 ### swissgpt:swissgpt: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