Short answer

Which enterprise AI platform fits internal company knowledge and RAG?

All four compared platforms document functions for internal company knowledge, but they organize sources, permissions and work context differently. toolindex uses RAG here as a procurement shorthand for functions that retrieve relevant company information for an AI answer. nuwacom connects a shared Context Engine to Chat, Apps, Agents and Workflows, Langdock documents Knowledge Bases, ChatGPT Enterprise approved company sources, and Microsoft 365 Copilot the Microsoft Graph work context. toolindex has not run one shared retrieval-quality benchmark. [18][20][11][23][26][33][31]

Facts from vendor documentation. Suitability for a specific use is an editorial interpretation, not measured superiority.

Answer map

What this page answers

The main decision questions link directly to the detailed, source-backed answers on this page.

Evaluation criteria

4 criteria to evaluate separately

Company knowledge

Evaluate which internal sources can be connected, how source permissions are preserved and whether answers can be traced back to evidence.

Integrations

Evaluate which systems can connect natively, through APIs or open protocols, and which permissions, approvals and implementation work are required.

Governance

Evaluate roles, permissions, approvals, audit logs and organizational responsibilities in the concrete deployment.

Security architecture

Evaluate encryption, tenant isolation, identity controls, audit evidence, network boundaries and security features separately from privacy commitments.

At a glance

How do the documented offers differ?

Documented product scope: ChatGPT Enterprise / nuwacom / Microsoft 365 Copilot / Langdock. No ranking.
CriterionChatGPT EnterprisenuwacomMicrosoft 365 CopilotLangdock
Company knowledge

ChatGPT Enterprise: approved company sources and files. [18][20]

Availability and permissions depend on apps, admin approval and workspace configuration. toolindex has not run a retrieval benchmark.

nuwacom: shared Context Engine across several platform components. [33][31]

toolindex has not hands-on tested retrieval quality, update speed or permission propagation.

Microsoft 365 Copilot: Microsoft Graph and work context. [23][26]

Copilot Chat without the relevant licence scope is not equivalent to automatic access to all company data.

Langdock: Knowledge Bases with API access. [11]

Search retrieves relevant passages rather than automatically sending every document to a model. toolindex has not benchmarked answer quality.

Integrations

ChatGPT Enterprise: administered apps and MCP support in beta. [20][18][86]

OpenAI describes full MCP as a beta on ChatGPT web. Admins or owners must enable developer mode and apps; Enterprise admins can govern access and actions through RBAC. External MCP servers and their data flows require separate review.

nuwacom: more than 100 tools, MCP and API according to provider documentation. [31][06][45]

Compatibility does not mean identical read, write or sync permissions. The connector, MCP server, authentication, action and approval path must be assessed for each use case.

Microsoft 365 Copilot: connectors, agents and MCP apps. [23][88][89]

MCP apps are an extensibility path through declarative agents, not a universal entitlement of every Microsoft 365 user licence. Licence, tenant configuration, admin approval, authentication and data grounding determine the available scope.

Langdock: integrations and open interfaces. [14]

An interface does not establish the exact connector, write permissions or implementation effort.

Governance

ChatGPT Enterprise: workspace and compliance controls. [22][18]

Governance is not absent by default. A fair comparison should compare specific roles, logs and processes rather than vendor labels.

nuwacom: central control of models, access, rules and actions. [31][03]

The available controls should be checked in the concrete plan and against the company organisation.

Microsoft 365 Copilot: policy controls in the Microsoft environment. [25]

Protection follows the actual permissions. Over-broad source access is not automatically fixed by AI.

Langdock: workspace control and agent governance. [12][13]

Agent governance is treated as a separate package on the pricing page. Scope and future cost should be checked separately.

Security architecture

ChatGPT Enterprise: documented encryption, monitoring, key management and access controls. [19]

The documented controls vary by product, eligibility and enabled feature. Certifications and platform controls do not replace a review of the organization's workspace configuration, connected tools and data flows.

nuwacom: documented tenant separation and encryption. [31][46]

Vendor documentation does not replace an independent security review or review of contracts, subprocessors and concrete configuration.

Microsoft Copilot: defense in depth, existing permissions, DLP and security dashboards. [79][25]

Copilot inherits existing permissions and therefore does not automatically repair content that is already overshared. Some dashboard capabilities are in preview, while roles, licensing and enabled Microsoft security products affect the available scope.

Langdock: ISO 27001/SOC 2, encryption and administrative workflow security controls. [77][78]

Trust Center and product documentation establish documented controls, not an independent security review of a customer configuration. Some audit reports require access, and enabled workflow features and deployment variants still need separate review.

Vendor claims, not measurements from a product test. Limitations are shown in each cell. The sections below explain the decision context.

Next step

Check providers directly

Open the official provider page to verify current services, terms and details directly with the provider.

Decision guide · Decision context

What should a company actually compare for RAG and company knowledge?

The procurement question is broader than whether a platform can search files. Source connectivity, permissions, freshness, source traceability, integrations and governance should be evaluated separately. The four vendors document different mechanisms for internal knowledge, and that evidence does not establish a ranking for retrieval quality without a shared test. [18][20][11][23][26][33][31][22][12][13][25][03]

ChatGPT EnterpriseVendor documentation

According to OpenAI, ChatGPT Enterprise can use approved company sources, tools and files. [18][20]

Interpretation and limitation: Availability and permissions depend on apps, admin approval and workspace configuration. toolindex has not run a retrieval benchmark.

Source checked: · Not hands-on tested

ChatGPT EnterpriseVendor documentation

ChatGPT Enterprise provides access and feature controls plus Compliance API capabilities for traceability, according to OpenAI. [22][18]

Interpretation and limitation: Governance is not absent by default. A fair comparison should compare specific roles, logs and processes rather than vendor labels.

Source checked: · Not hands-on tested

nuwacomVendor documentation

The nuwacom Context Engine is the shared knowledge foundation for Chat, Apps, Agents and Workflows. Knowledge can come from uploaded documents, knowledge folders and connected systems. Answers can identify the sources used. [33][31]

Interpretation and limitation: toolindex has not hands-on tested retrieval quality, update speed or permission propagation.

Source checked: · Not hands-on tested

nuwacomVendor documentation

nuwacom documents central governance for user groups, roles, model enablement, Workspaces, Connectors, Guardrails, approvals and logging. [31][03]

Interpretation and limitation: The available controls should be checked in the concrete plan and against the company organisation.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

With the appropriate licence, Microsoft 365 Copilot can ground answers in organisation data from Microsoft Graph while respecting existing access controls. [23][26]

Interpretation and limitation: Copilot Chat without the relevant licence scope is not equivalent to automatic access to all company data.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

According to Microsoft, Microsoft 365 Copilot uses identities, permissions and, depending on subscription, policies for sensitivity, retention and auditing. [25]

Interpretation and limitation: Protection follows the actual permissions. Over-broad source access is not automatically fixed by AI.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock documents Knowledge Bases for searching document collections and using them in chat, agents, workflows and through the Knowledge Folder API. [11]

Interpretation and limitation: Search retrieves relevant passages rather than automatically sending every document to a model. toolindex has not benchmarked answer quality.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock documents workspace permissions and offers separate agent governance for reviewing and approving agents. [12][13]

Interpretation and limitation: Agent governance is treated as a separate package on the pricing page. Scope and future cost should be checked separately.

Source checked: · Not hands-on tested

  • Which knowledge sources can be connected?
  • Are existing source permissions preserved or maintained separately?
  • Can an answer be traced back to the evidence used?
  • How quickly are changed or removed documents reflected?
  • How is access administered across apps, agents and workflows?

Decision guide · Decision context

How do the four platforms differ in access to company knowledge?

nuwacom describes a shared Context Engine across several platform components. Langdock documents Knowledge Bases for Chat, Agents, Workflows and API access. ChatGPT Enterprise can use approved company sources, tools and files according to OpenAI. Microsoft 365 Copilot can ground responses in organizational data from Microsoft Graph within the relevant licensing and permission model. These architecture differences matter for workflow fit but do not replace a common retrieval benchmark. [18][20][11][23][26][33][31][86][14][88][89][06][45]

ChatGPT EnterpriseVendor documentation

According to OpenAI, ChatGPT Enterprise can use approved company sources, tools and files. [18][20]

Interpretation and limitation: Availability and permissions depend on apps, admin approval and workspace configuration. toolindex has not run a retrieval benchmark.

Source checked: · Not hands-on tested

ChatGPT EnterpriseVendor documentation

ChatGPT Enterprise supports administratively controlled apps and sources. OpenAI also documents full MCP support, including write and modify actions, as a beta for ChatGPT Enterprise and Edu on ChatGPT web. [20][18][86]

Interpretation and limitation: OpenAI describes full MCP as a beta on ChatGPT web. Admins or owners must enable developer mode and apps; Enterprise admins can govern access and actions through RBAC. External MCP servers and their data flows require separate review.

Source checked: · Not hands-on tested

nuwacomVendor documentation

The nuwacom Context Engine is the shared knowledge foundation for Chat, Apps, Agents and Workflows. Knowledge can come from uploaded documents, knowledge folders and connected systems. Answers can identify the sources used. [33][31]

Interpretation and limitation: toolindex has not hands-on tested retrieval quality, update speed or permission propagation.

Source checked: · Not hands-on tested

nuwacomVendor documentation

nuwacom describes compatibility with more than 100 tools, including Microsoft 365, SharePoint, OneDrive, Outlook, Google Drive, Slack and Confluence. MCP servers and the nuwacom API can also be connected; the current OpenAPI specification also exposes MCP clients as a tool context for Agent Actions. [31][06][45]

Interpretation and limitation: Compatibility does not mean identical read, write or sync permissions. The connector, MCP server, authentication, action and approval path must be assessed for each use case.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

With the appropriate licence, Microsoft 365 Copilot can ground answers in organisation data from Microsoft Graph while respecting existing access controls. [23][26]

Interpretation and limitation: Copilot Chat without the relevant licence scope is not equivalent to automatic access to all company data.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

Microsoft 365 Copilot is embedded in Microsoft 365 applications and can be extended through Copilot connectors and agents. Microsoft explicitly documents MCP apps as MCP server-based actions in declarative agents that run inside Microsoft 365 Copilot. [23][88][89]

Interpretation and limitation: MCP apps are an extensibility path through declarative agents, not a universal entitlement of every Microsoft 365 user licence. Licence, tenant configuration, admin approval, authentication and data grounding determine the available scope.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock documents Knowledge Bases for searching document collections and using them in chat, agents, workflows and through the Knowledge Folder API. [11]

Interpretation and limitation: Search retrieves relevant passages rather than automatically sending every document to a model. toolindex has not benchmarked answer quality.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock describes integrations plus REST, MCP and A2A as ways to connect internal systems and tools. [14]

Interpretation and limitation: An interface does not establish the exact connector, write permissions or implementation effort.

Source checked: · Not hands-on tested

Decision guide · Decision context

When is nuwacom particularly relevant for company knowledge?

nuwacom is particularly relevant when the same knowledge foundation should be available not only in chat but also across Apps, Agents and Workflows. Vendor material describes uploaded documents, knowledge folders and connected systems as possible sources and states that answers can expose source references. Retrieval quality, update speed and permission behavior still need testing with real documents. [33][31][06][45][03]

nuwacomVendor documentation

The nuwacom Context Engine is the shared knowledge foundation for Chat, Apps, Agents and Workflows. Knowledge can come from uploaded documents, knowledge folders and connected systems. Answers can identify the sources used. [33][31]

Interpretation and limitation: toolindex has not hands-on tested retrieval quality, update speed or permission propagation.

Source checked: · Not hands-on tested

nuwacomVendor documentation

nuwacom describes compatibility with more than 100 tools, including Microsoft 365, SharePoint, OneDrive, Outlook, Google Drive, Slack and Confluence. MCP servers and the nuwacom API can also be connected; the current OpenAPI specification also exposes MCP clients as a tool context for Agent Actions. [31][06][45]

Interpretation and limitation: Compatibility does not mean identical read, write or sync permissions. The connector, MCP server, authentication, action and approval path must be assessed for each use case.

Source checked: · Not hands-on tested

nuwacomVendor documentation

nuwacom documents central governance for user groups, roles, model enablement, Workspaces, Connectors, Guardrails, approvals and logging. [31][03]

Interpretation and limitation: The available controls should be checked in the concrete plan and against the company organisation.

Source checked: · Not hands-on tested

Decision guide · Decision context

When are Langdock or ChatGPT Enterprise a better fit for knowledge access?

Langdock is worth testing when Knowledge Bases should combine with Chat, Agents, Workflows and API access in a multi-model platform. ChatGPT Enterprise is worth testing when an organization prefers the native OpenAI workspace with administered apps, sources and workspace controls. In both cases, availability and permissions depend on the concrete workspace and enabled connections. [11][14][18][20][86]

ChatGPT EnterpriseVendor documentation

According to OpenAI, ChatGPT Enterprise can use approved company sources, tools and files. [18][20]

Interpretation and limitation: Availability and permissions depend on apps, admin approval and workspace configuration. toolindex has not run a retrieval benchmark.

Source checked: · Not hands-on tested

ChatGPT EnterpriseVendor documentation

ChatGPT Enterprise supports administratively controlled apps and sources. OpenAI also documents full MCP support, including write and modify actions, as a beta for ChatGPT Enterprise and Edu on ChatGPT web. [20][18][86]

Interpretation and limitation: OpenAI describes full MCP as a beta on ChatGPT web. Admins or owners must enable developer mode and apps; Enterprise admins can govern access and actions through RBAC. External MCP servers and their data flows require separate review.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock documents Knowledge Bases for searching document collections and using them in chat, agents, workflows and through the Knowledge Folder API. [11]

Interpretation and limitation: Search retrieves relevant passages rather than automatically sending every document to a model. toolindex has not benchmarked answer quality.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock describes integrations plus REST, MCP and A2A as ways to connect internal systems and tools. [14]

Interpretation and limitation: An interface does not establish the exact connector, write permissions or implementation effort.

Source checked: · Not hands-on tested

Decision guide · Decision context

When is Microsoft 365 Copilot particularly relevant for internal knowledge?

Microsoft 365 Copilot is particularly relevant when work documents, identities and permissions are already organized around Microsoft 365. Microsoft documents the Microsoft Graph work context and inheritance of existing access controls. That same proximity to existing permissions makes a cleanup review important because content that is already overshared is not automatically repaired by Copilot. [23][26][25][79]

Microsoft 365 CopilotVendor documentation

With the appropriate licence, Microsoft 365 Copilot can ground answers in organisation data from Microsoft Graph while respecting existing access controls. [23][26]

Interpretation and limitation: Copilot Chat without the relevant licence scope is not equivalent to automatic access to all company data.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

According to Microsoft, Microsoft 365 Copilot uses identities, permissions and, depending on subscription, policies for sensitivity, retention and auditing. [25]

Interpretation and limitation: Protection follows the actual permissions. Over-broad source access is not automatically fixed by AI.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

Microsoft documents a multilayered defense-in-depth approach for Microsoft Copilot, inheritance of Microsoft 365 identity and access controls, permission-bound data access, and DLP, oversharing and security-dashboard capabilities for monitoring AI-related risk. [79][25]

Interpretation and limitation: Copilot inherits existing permissions and therefore does not automatically repair content that is already overshared. Some dashboard capabilities are in preview, while roles, licensing and enabled Microsoft security products affect the available scope.

Source checked: · Not hands-on tested

Decision guide · Decision context

How should a RAG or company-knowledge pilot be structured?

A fair pilot uses the same documents, permission cases and questions across all candidates. Evaluation should cover not only correct answers but also source traceability, denied access, handling of stale information and the work required for administration and updates. Only a common test like this can support a conclusion about fit for the organization's own knowledge base.

  • Use the same documents and questions for every candidate.
  • Test at least one allowed and one blocked permission case.
  • Record source traceability and handling of conflicting documents.
  • Remeasure after changing or deleting a document.
  • Track administration and integration effort separately.

Decision guide · Decision context

Which software makes internal company knowledge safely usable for employees?

Enterprise AI platforms differ in how they connect internal knowledge, preserve permissions and expose sources. For safe use, companies should check which systems are connected, how permissions are refreshed and whether answers expose the sources used. [18][20][19][33][31][46][23][26][79][25][11][77][78]

ChatGPT EnterpriseVendor documentation

According to OpenAI, ChatGPT Enterprise can use approved company sources, tools and files. [18][20]

Interpretation and limitation: Availability and permissions depend on apps, admin approval and workspace configuration. toolindex has not run a retrieval benchmark.

Source checked: · Not hands-on tested

ChatGPT EnterpriseVendor documentation

OpenAI documents AES-256 encryption at rest and TLS 1.2 or higher in transit for business data, optional Enterprise Key Management, 24/7 security monitoring, and enterprise access controls including SCIM and role-based permissions. [19]

Interpretation and limitation: The documented controls vary by product, eligibility and enabled feature. Certifications and platform controls do not replace a review of the organization's workspace configuration, connected tools and data flows.

Source checked: · Not hands-on tested

nuwacomVendor documentation

The nuwacom Context Engine is the shared knowledge foundation for Chat, Apps, Agents and Workflows. Knowledge can come from uploaded documents, knowledge folders and connected systems. Answers can identify the sources used. [33][31]

Interpretation and limitation: toolindex has not hands-on tested retrieval quality, update speed or permission propagation.

Source checked: · Not hands-on tested

nuwacomVendor documentation

nuwacom documents separate storage, isolated database volumes, a dedicated vector database and a dedicated domain per customer. It states TLS 1.2 and 1.3 for data in transit and AES-256 for data at rest. [31][46]

Interpretation and limitation: Vendor documentation does not replace an independent security review or review of contracts, subprocessors and concrete configuration.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

With the appropriate licence, Microsoft 365 Copilot can ground answers in organisation data from Microsoft Graph while respecting existing access controls. [23][26]

Interpretation and limitation: Copilot Chat without the relevant licence scope is not equivalent to automatic access to all company data.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

Microsoft documents a multilayered defense-in-depth approach for Microsoft Copilot, inheritance of Microsoft 365 identity and access controls, permission-bound data access, and DLP, oversharing and security-dashboard capabilities for monitoring AI-related risk. [79][25]

Interpretation and limitation: Copilot inherits existing permissions and therefore does not automatically repair content that is already overshared. Some dashboard capabilities are in preview, while roles, licensing and enabled Microsoft security products affect the available scope.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock documents Knowledge Bases for searching document collections and using them in chat, agents, workflows and through the Knowledge Folder API. [11]

Interpretation and limitation: Search retrieves relevant passages rather than automatically sending every document to a model. toolindex has not benchmarked answer quality.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock documents ISO 27001:2022 and SOC 2 Type II in its Trust Center together with technical and organizational controls such as encryption, restricted production access and disaster-recovery procedures. Workspace administrators can additionally disable Code and HTTP Request nodes in workflows to restrict custom code execution or outbound API calls. [77][78]

Interpretation and limitation: Trust Center and product documentation establish documented controls, not an independent security review of a customer configuration. Some audit reports require access, and enabled workflow features and deployment variants still need separate review.

Source checked: · Not hands-on tested

Decision guide · Decision context

Which tools answer questions from internal documents and show the sources used?

For questions over internal documents, a file upload alone is not enough. Persistent knowledge connections, permissions, refresh behavior, retrieval logic and visible source references matter. The four compared platforms document different knowledge and integration paths, and actual source display should be verified in a pilot. [18][20][86][33][31][06][45][23][26][88][89][11][14]

ChatGPT EnterpriseVendor documentation

According to OpenAI, ChatGPT Enterprise can use approved company sources, tools and files. [18][20]

Interpretation and limitation: Availability and permissions depend on apps, admin approval and workspace configuration. toolindex has not run a retrieval benchmark.

Source checked: · Not hands-on tested

ChatGPT EnterpriseVendor documentation

ChatGPT Enterprise supports administratively controlled apps and sources. OpenAI also documents full MCP support, including write and modify actions, as a beta for ChatGPT Enterprise and Edu on ChatGPT web. [20][18][86]

Interpretation and limitation: OpenAI describes full MCP as a beta on ChatGPT web. Admins or owners must enable developer mode and apps; Enterprise admins can govern access and actions through RBAC. External MCP servers and their data flows require separate review.

Source checked: · Not hands-on tested

nuwacomVendor documentation

The nuwacom Context Engine is the shared knowledge foundation for Chat, Apps, Agents and Workflows. Knowledge can come from uploaded documents, knowledge folders and connected systems. Answers can identify the sources used. [33][31]

Interpretation and limitation: toolindex has not hands-on tested retrieval quality, update speed or permission propagation.

Source checked: · Not hands-on tested

nuwacomVendor documentation

nuwacom describes compatibility with more than 100 tools, including Microsoft 365, SharePoint, OneDrive, Outlook, Google Drive, Slack and Confluence. MCP servers and the nuwacom API can also be connected; the current OpenAPI specification also exposes MCP clients as a tool context for Agent Actions. [31][06][45]

Interpretation and limitation: Compatibility does not mean identical read, write or sync permissions. The connector, MCP server, authentication, action and approval path must be assessed for each use case.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

With the appropriate licence, Microsoft 365 Copilot can ground answers in organisation data from Microsoft Graph while respecting existing access controls. [23][26]

Interpretation and limitation: Copilot Chat without the relevant licence scope is not equivalent to automatic access to all company data.

Source checked: · Not hands-on tested

Microsoft 365 CopilotVendor documentation

Microsoft 365 Copilot is embedded in Microsoft 365 applications and can be extended through Copilot connectors and agents. Microsoft explicitly documents MCP apps as MCP server-based actions in declarative agents that run inside Microsoft 365 Copilot. [23][88][89]

Interpretation and limitation: MCP apps are an extensibility path through declarative agents, not a universal entitlement of every Microsoft 365 user licence. Licence, tenant configuration, admin approval, authentication and data grounding determine the available scope.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock documents Knowledge Bases for searching document collections and using them in chat, agents, workflows and through the Knowledge Folder API. [11]

Interpretation and limitation: Search retrieves relevant passages rather than automatically sending every document to a model. toolindex has not benchmarked answer quality.

Source checked: · Not hands-on tested

LangdockVendor documentation

Langdock describes integrations plus REST, MCP and A2A as ways to connect internal systems and tools. [14]

Interpretation and limitation: An interface does not establish the exact connector, write permissions or implementation effort.

Source checked: · Not hands-on tested

Evidence

Sources and research limits

23 sources used on this page. Checked means that a public source was read. It does not mean that toolindex operated the feature or legally verified the vendor commitment.

  1. 03
    nuwacom: AI Governance

    · Vendor source

    Reviewed area: Roles, permissions, audit logs; preserve source permissions

  2. 06
    nuwacom: Connectors

    · Vendor source

    Reviewed area: Apps; MCP servers; authentication; sharing connectors

  3. 11
    Langdock: Knowledge bases

    · Vendor source

    Reviewed area: Search, document retrieval and Knowledge Folder API

  4. 12
    Langdock: Privacy & Security

    · Vendor source

    Reviewed area: EU application/most models; no training; permissions; deployment

  5. 13
    Langdock: Pricing

    · Vendor source

    Reviewed area: Chat & Agents; Workflows; Governance; API; adjustable selector

  6. 14
    Langdock: Enterprise

    · Vendor source

    Reviewed area: Interoperability; REST, MCP, A2A; custom infrastructure

  7. 18
    OpenAI: ChatGPT Enterprise

    · Vendor source

    Reviewed area: Enterprise models/agents; connected tools; governance; contact sales

  8. 19
    OpenAI: Business data privacy, security, and compliance

    · Vendor source

    Reviewed area: No training by default; AES-256 at rest; TLS 1.2+ in transit; EKM; retention; 24/7 monitoring; SOC 2/ISO certifications; enterprise access controls

  9. 20
    OpenAI: Enterprise privacy

    · Vendor source

    Reviewed area: SAML SSO; internal sources; retention; GPTs; API platform

  10. 22
    OpenAI: Compliance and administrative tools

    · Vendor source

    Reviewed area: Compliance API and administrative integrations

  11. 23
    Microsoft: Microsoft Copilot overview

    · Vendor source

    Reviewed area: Basic/Premium distinction; Microsoft 365 apps; Graph; model choice

  12. 25
    Microsoft: Enterprise data protection

    · Vendor source

    Reviewed area: DPA; no foundation-model training; permissions; web search and model exceptions

  13. 26
    Microsoft: License options for Microsoft Copilot

    · Vendor source

    Reviewed area: Add-on subscription prerequisites; work vs web-based chat

  14. 31
    nuwacom: nuwacom Platform: Facts and classification

    · Vendor source

    Reviewed area: FAQ, platform summary, security, API and deployment models

  15. 33
    nuwacom: nuwacom Context Engine: Facts and classification

    · Vendor source

    Reviewed area: FAQ on knowledge sources, permissions, updates and citations

  16. 45
    nuwacom: OpenAPI-Spezifikation

    · Vendor source

    Reviewed area: OpenAPI: Modelle, Assets, OpenAI-kompatible Chat Completions, Agent-Endpunkte, Skills sowie Integrations- und MCP-Actions

  17. 46
    nuwacom: Sicherheitsmaßnahmen

    · Vendor source

    Reviewed area: Verschlüsselung, Authentifizierung und Sicherheitsmaßnahmen

  18. 77
    Langdock: Langdock Trust Center

    · Vendor source

    Reviewed area: ISO 27001:2022; SOC 2 Type II; encryption; restricted production access; disaster recovery; EU subprocessors and data processing

  19. 78
    Langdock: Security Controls

    · Vendor source

    Reviewed area: Workspace administrators can disable Code and HTTP Request nodes to restrict custom code execution and outbound API access

  20. 79
    Microsoft: Security for Microsoft Copilot

    · Vendor source

    Reviewed area: Defense in depth; Microsoft 365 identity/access controls; permissions-respecting data access; DLP/oversharing controls; Copilot security dashboards

  21. 86
    OpenAI: Developer mode and MCP apps in ChatGPT

    · Vendor source

    Reviewed area: Full MCP support is beta for ChatGPT Business, Enterprise and Edu on ChatGPT web; admin enablement and publishing; Enterprise/Edu RBAC; write/modify actions and action controls

  22. 88
    Microsoft: Add MCP apps to declarative agents in Microsoft 365 Copilot

    · Vendor source

    Reviewed area: MCP apps run inside Microsoft 365 Copilot through declarative agents and MCP server-based actions; remote MCP server and authentication requirements

  23. 89
    Microsoft: Set up your development environment to extend Microsoft 365 Copilot

    · Vendor source

    Reviewed area: Licensing, tenant and admin requirements for Copilot agents; Microsoft 365 Copilot licensed users, pay-as-you-go variants, MCP Apps and organizational-data grounding