# License company knowledge base to AI: what AI data companies name

> Looking to sell a company knowledge base to AI? Companies license it. Mercor names Confluence and Notion, and micro1's partnership page names knowledge bases.

By Matt Burns, Vaultfish. Canonical: https://vaultfish.com/answers/sell-company-knowledge-base-to-ai  
Published: 2026-08-01  
Updated: 2026-10-14

## The short answer

To license a company knowledge base to AI, export your wiki and documentation as a record of how the company works. Mercor names Confluence and Notion, and micro1's partnership page lists knowledge bases. Notion says it does not train models on your data by default. Atlassian's settings differ by plan.

A knowledge base is the part of a company's data written to be read. Parts of it may also sit on a public help center.

## Who names knowledge bases?

[micro1's data page](https://www.micro1.ai/data-partnerships) lists SOPs, knowledge bases, internal documentation, project histories and QA processes. [Mercor's page](https://www.mercor.com/data/) names nine tools, including Confluence and Notion. [Troveo's page](https://www.troveo.ai/business-data) names Notion under work and knowledge tools, next to Jira, Linear and Asana.

All of this is buyer self-description. No page I read says how often a lab asks for wiki content or what it pays.

## What do the vendors say?

[Notion's security page](https://www.notion.com/help/notion-ai-security-practices) says that by default Notion and its AI subprocessors do not use Customer Data to train any models.

[Atlassian's Customer Agreement](https://www.atlassian.com/legal/customer-agreement) says the customer owns all intellectual property and other rights in Customer Data. Its data contribution settings are separate, so see [licensing Confluence data to AI](/answers/sell-confluence-data-to-ai).

## What sits inside a knowledge base?

My reading: runbooks, policies, onboarding pages, product notes and pasted customer detail. Some of that was written by staff, some copied from vendors or clients, and some may already be on a public help center.

I found no source on how buyers treat content that is already public. Ask any buyer before you assume.

## What should you check first?

Sort pages by author and origin, and look for customer names, contract terms and credentials pasted into pages.

The [rights check](/rights-check) asks whose records these are and what your contracts allow. Related pages are [licensing internal documents to AI](/answers/sell-internal-documents-to-ai) and [licensing Jira data to AI](/answers/sell-jira-data-to-ai).

Talk to a privacy or commercial lawyer in your state before you sign.

micro1 may pay us a referral fee if a company we introduce goes ahead with it. [How we are paid](https://vaultfish.com/disclosure)

Figure: comparison of Companies that name knowledge-base content: micro1 (emphasized: Names the data type itself, Names knowledge bases), Mercor (Names Confluence, Notion), Troveo (Names Notion). micro1 is emphasized because it names knowledge bases as a data type, where Mercor and Troveo name tools.

[Apply to micro1's data partnership (paid link)](https://req.micro1.ai/post/74520e8b-4673-4da5-b855-53609aaf6710?referralCode=f82e519e-5d64-4e0e-9574-760c84371cf2&utm_source=referral&utm_medium=share&utm_campaign=data_referral) · [micro1's own data-partnerships page](https://www.micro1.ai/data-partnerships)

_Paid link. [How we are paid](https://vaultfish.com/disclosure)_

_Vaultfish helps you run the process. We are not lawyers and this is not legal advice. If you need counsel who knows this area, we can point you to one._

## Sources

- [micro1's data page](https://www.micro1.ai/data-partnerships)
- [Mercor's page](https://www.mercor.com/data/)
- [Troveo's page](https://www.troveo.ai/business-data)
- [Notion's security page](https://www.notion.com/help/notion-ai-security-practices)
- [Atlassian's Customer Agreement](https://www.atlassian.com/legal/customer-agreement)