Skip to content
KRPUS
Sign up

COMPARE

Notion, Obsidian, Confluence, SharePoint, Korpus.

All five keep what a team knows. They were built for different jobs. Here is what each does best, where Korpus fits and where it does not.

WHAT EACH DOES BEST

Good tools, built for different jobs.

Korpus

One shared memory for people and their AI agents.

  • Claude (listed in its connector directory), ChatGPT or any MCP client; an API, and an SDK for programs
  • Every delegation (an AI agent, a script, a program) has its own rules: which paths, and create, read, update or delete
  • Every change names who made it, through which agent, the revision it read and why
  • An open format (OKF): Markdown with YAML frontmatter, exported at any time; free to start, Plus €5

Pick it when your AI agents should work from the same knowledge your team reads, within limits you set.

WHAT IT DOES NOT DO

  • No boards, calendars or timelines: Markdown, tables, diagrams and typed tables
  • Works online: the app opens without a network, your bundles do not
  • No Office co-editing: files are kept beside the documents that explain them
  • New in 2026: no Jira or Microsoft 365 integration, a small ecosystem

If you need one of these first, one of the tools above serves you better today.

SIDE BY SIDE

Five tools, side by side.

Korpus, Notion, Obsidian, Confluence and SharePoint compared
QuestionKorpusNotionObsidianConfluenceSharePoint
Built forPeople and their agents, togetherDocs, wikis and projectsNotes on your deviceThe team wiki beside JiraSites and files in Microsoft 365
FormatMarkdown with YAML frontmatter, in the open OKF formatBlocks and databasesMarkdown filesPages, live docs, whiteboards, databasesOffice files, pages and lists
AI agentsClaude, ChatGPT, any MCP client; API; SDKNotion AI; official MCP serverCommunity plugins and MCP serversRovo; Rovo MCP serverMicrosoft 365 Copilot (paid add-on); MCP server in preview
What an agent may touchOnly the paths and rights its person gives itEverything its person can reachWhat the plugin or server can read on diskEverything its person can reachIts person’s access, or sites granted to an app
Who changed whatEvery change: person, agent, revision and whyPage history: 7 days on Free, longer on paid plansFile recovery snapshots; Sync version historyPage historyVersion history in libraries
Working togetherShare a bundle with a person, read only or read and write, down to a folderA shared workspaceShared vaults through Sync, up to 20 people, no live co-editingShared spacesCo-authoring of Office files
OfflineNoPages you mark, in the desktop and mobile appsYes, the files are localEditing pages opened while onlineFiles synced through OneDrive
Where data livesFrankfurt, or your own AWS accountUnited States; Frankfurt on EnterpriseYour deviceAtlassian cloud; a region of your choice on paid plansMicrosoft cloud; EU Data Boundary for EU tenants
Taking it with youAn OKF folder as a zip: Markdown, your files, index and logMarkdown, HTML, CSV or PDFNothing to do: they are filesPDF, HTML, XML or CSV per spaceDownload the files
To startFree, no card; Plus €5 per person and monthFree plan; paid plans per memberFree; Sync and Publish paidFree up to 10 users; paid per userIn Microsoft 365 Business plans, or on its own
SourcesEvery claim about another tool is from its maker’s own pages, checked 2026-10. Products change; if one is out of date, tell us.show

OPEN FORMAT · NO LOCK-IN

What you put in comes out as plain files.

Every Korpus bundle is a bundle in the Open Knowledge Format (OKF) v0.2: a folder of Markdown files with YAML frontmatter. OKF is an open specification published by Google Cloud under the Apache License 2.0, not by us. Export a bundle at any time and you hold it in that format, readable without Korpus.

  • An open specification

    OKF v0.2 is published by Google Cloud under the Apache License 2.0 and describes itself as vendor-neutral. Korpus follows it; it does not own it.

  • Everything in the bundle

    One Markdown file per document with its frontmatter (type, tags, status, relations, who wrote it), every file beside the document that explains it, and an index and a change log in every folder.

  • On every plan, three ways

    Anyone who can read a bundle can export it: in the web app (Contents → Export), over MCP (export_bundle) or over the API. Free plan included.

  • Readable without us

    Open it in a text editor or Obsidian, put it in Git, hand it to another agent. Up to 50 MB of documents and files per export.

An exported bundle (example)
  • incident-response/
  • index.mdokf_version: "0.2"
  • log.mdevery change, who, why
  • runbooks/
  • index.md
  • log.md
  • db-failover.mdtype: runbook
  • postmortems/
  • index.md
  • log.md
  • INC-0042.mdtype: postmortem
  • INC-0042.pdfits file

THE QUESTION THAT DECIDES IT

Will your AI agents work from it?

If people alone read and write, any of the five will do, and the one your team already knows is often the right one. Once agents read your runbooks, follow your decisions and write back what they did, you want the lightest thing that lets them do it safely.

  1. Light to start

    No workspace to design, no admin, nothing to install. Sign up, connect Claude from its connector directory, take a template from the catalog or start empty.

  2. Light to keep

    Your agents write back what they did, each only where its rules allow. Every change carries a name, a revision and a one-line reason, so you can follow it.

  3. Light to leave

    Export a bundle at any time as a folder in the open OKF format: Markdown with frontmatter, your files beside it. No Korpus software is needed to read it.

No need to switch.

Korpus does not ask you to move everything. Start with one subject your agents need, beside the tools you keep.

  • With Notion or Confluence: keep your project pages and the wiki people browse. Give your agents a bundle for the knowledge they work from.
  • With SharePoint: keep the Office files and the intranet. Put the runbooks and decisions your agents act on in a bundle.
  • With Obsidian: keep your private vault. Share what your team and its agents need in a bundle: it is Markdown either way.

The lightest way to start is to start.

Nothing to migrate, nothing to install, nothing to decide for the whole company. One bundle, one agent. Keep it, grow it, or export it.

  1. 1Sign upFree, no card. Create your first bundle.
  2. 2Connect your agentSearch for Korpus in Claude’s connector directory, or add it to ChatGPT or any MCP client as a custom connector.
  3. 3Give it a subjectStart from a template or from nothing. Ask your agent to fill it with what it should know.
Start freeSee how to connect

Free to start · Plus €5 per person and month · hosted in Frankfurt