What is in a company knowledge base?
The written answers your teams rely on every day: internal wiki pages, runbooks, onboarding guides, troubleshooting articles, policy pages and the public help centre built from the same material. The edit history matters as much as the latest version, because it shows how an answer changed when a product, a rule or a customer problem changed. Workspace documents of this kind are already changing hands: one wound-down startup was awaiting payment for "the workspace data in Google, Notion, Figma, and Slack" (MIT Technology Review, Oct 13 2026).
Who owns knowledge base data held in a vendor's software?
Usually your company, though the vendor's contract decides. Atlassian's customer agreement, for example, says that "as between the parties, Customer owns all intellectual property and other rights in Customer Data" (Atlassian Customer Agreement). Under US copyright law, a work "prepared by an employee within the scope of his or her employment" is a work made for hire (17 U.S.C. § 101), and the employer is treated as its author (17 U.S.C. § 201). Pages written by contractors, or pasted from third-party material, can be different; ask counsel about your own.
What does knowledge base data mean for what you get paid and control?
It is already written, organised and kept current. Much of a company's data already lives in third-party software. Licensing it means re-licensing what already exists, and getting paid for it rather than giving it away for free. Internal pages can still hold staff names, phone extensions and customer examples. fearofgod.ai de-identifies the data before it goes to buyers. Your company can keep ownership of its data. This is agreed case by case. Your company's name stays confidential until the agreement is fully signed, and a completely anonymous partnership is also possible.