SaaS Ranking
Menu

SaaS transparency ranking · Content, media and collaboration

Knowledge base and wiki software

46 vendors · updated 2026-10-17 · 3 without enough data for a score

Internal wikis and knowledge bases, ranked by what they publish about how they handle your data.

Public transparency score, not a product or security rating. Transparency means: published on the vendor's own site, readable without a login, found by us at the addresses we checked.

+5points above the median of every category we measure

  • Knowledge base and wiki22
  • All categories17
Median transparency score, out of 100. Knowledge base and wiki sits above the median across every category we measure.
  1. A0 0%
  2. B0 0%
  3. C0 0%
  4. D5 12%
  5. E12 28%
  6. F26 60%
43 vendors with a score; 3 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.
All filters
Show only vendors where we found

Transparency band

3 without enough data for a band

46 vendors

Sort by

Before the demo

Knowledge base software: a practical trial checklist

Find the right answer, under the right permissions, after the author leaves.

Test retrieval with the language your readers use

Prepare several questions before the demonstration. Include an acronym, a phrase used by a new colleague and a question whose answer does not exist. Search as an ordinary reader and record which article appears, how much context the result shows and whether the reader can identify the current version. Repeat after editing an article and note when the result changes. A demonstration using the exact document title tests title lookup; it does not establish whether an unfamiliar reader can find the answer. Keep a record of unsuccessful searches as well as successful ones.

Follow permissions into every route to the content

Create a public article, a team-only article and a restricted page. Test each through direct links, search results, embeds and connected tools using the relevant reader accounts. Remove one reader from the team and repeat in a fresh session. Ask how a connected source updates permissions when access changes there. Distinguish the article title appearing in a result from the full article being accessible: both can matter to your review. Record the configuration and the plan used rather than assuming the same controls exist in every edition.

Give every answer an owner and a review route

Assign an owner and a review date to a sample policy. Change the policy, request approval and test how a reader sees the approved version while an edit is pending. Reassign ownership when the original author leaves. Ask whether reminders, review history and approval are included features, integrations or manual steps. If the product relies on a manual process, test that process with the team who will maintain it. A field called last updated does not establish that someone checked whether the answer is still correct.

Full trial checklist and CSV worksheet

A trial you can repeat

A wiki trial needs more than an attractive article. Use a small set of invented policies, troubleshooting notes and restricted team documents. Give one person the author role and another the reader role. Ask the reader to solve a task without help from the author. Keep the search terms, document version, access level and answer together so the next product can be tested with the same scenario.

Kipwise documents editing, search integrations, folders and teammate roles. These are examples of separate capabilities to examine. The trial tasks here are our editorial questions for any knowledge base, not findings about a particular product. Kipwise: getting started and content organisation. Source reviewed 2026-10-03. The trial questions are editorial guidance, not additional measured criteria.

Narrow it down

Each of these lists the Knowledge base and wiki vendors that meet one condition, with the source for each, and appears only where at least 8 of them meet it.

This category, criterion by criterion

How this market does on each criterion, with its own share and how it compares with the rest.

Every result links its source on the vendor page. A grey segment means we could not measure it, not that it is missing. See how we score.