Skip to content
notdocs
notdocs
Use itFeaturesEverything notdocs does, from the editor and query blocks to merges, search and agents, with the page that explains each.AgentsGive Claude Code, Cursor or any MCP client the workspace: tokens, tools, resources and prompts.CLIEvery notdocs command: documents, import, comments, tokens and the organization, for a local folder or a hosted workspace.TemplatesEvery built-in template with the file it starts, from a task to a data processing agreement.PricingFree for one person, Solo and Team for a few. What each plan allows.
Move inSwitch from NotionImport a Notion export as typed markdown documents in your repository.Switch from ObsidianImport an Obsidian vault and keep working on the same files.notdocs vs NotionMarkdown in your git repository or pages in Notion's database: how agents reach each, and what each tool does better.notdocs vs ObsidianBoth keep markdown files. What differs is where they live, who edits them, and how.ChangelogWhat changed in notdocs, from the CHANGELOG in the repository.
notdocsAboutWhy the repository should be the workspace, and the decisions notdocs is built on.SecurityWhere data lives, how access is scoped, and how to report a vulnerability.ContactHow to reach notdocs for support, privacy, security and legal matters.
PoliciesLegalEvery policy and agreement that applies to notdocs.

notdocs vs Notion

Markdown in your git repository or pages in Notion's database: how agents reach each, and what each tool does better.

Last revised

On this page

The difference in one line

Notion keeps your pages in its own database and gives you an app to edit them. notdocs keeps your pages as markdown files in your git repository and gives you an app to edit them, plus an MCP server and a CLI so your coding agents edit the same files.

What follows describes Notion from its public documentation as of the date above. Notion changes often; if something here is out of date, write to hello@notdocs.dev.

Side by side

notdocsNotion
Where content livesMarkdown files in your git repositoryNotion's cloud database
Getting it outIt is already out: the files are the exportExport to Markdown & CSV, HTML or PDF
HistoryGit history, plus a per-document history with diffsPage history, length depending on the plan
AgentsMCP server and CLI over the same operations as the app, with project tokensAPI and an MCP server over the Notion workspace
Structured dataTyped documents with frontmatter; query blocks as boards, tables, lists, calendars and galleriesDatabases with properties, relations, rollups, formulas and many views
Editing togetherOne shared session per open document, with everybody's carets; a save from an agent or another branch is three-way mergedLive co-editing with cursors
Sharing outside the teamBy link, or published as a site on a subdomain or your own domain, every page also served as markdownPublished pages and Notion Sites
AppsWeb app and CLIWeb, desktop and mobile apps
PricingFlat per organization, see pricingPer member

Pick notdocs when

  • Your docs belong next to your code. Specs, decisions, runbooks and tasks sit in the repository they describe, are reviewed in pull requests, and ship with the branch.
  • Coding agents do a lot of the writing. Claude Code, Cursor and other MCP clients read and write the same files a person edits, and a merge keeps either side from overwriting the other. See Agents.
  • You do not want a second source of truth. Nothing syncs between notdocs and your repository, because there is nothing to sync.
  • You want to be able to leave. Uninstall the GitHub App and you still have every file. See data portability and exit.
  • You are a handful of people. One flat price per organization, not per seat.

Pick Notion when

  • You live in databases. Relations, rollups and formulas across many linked databases are what Notion is built for; notdocs query blocks filter, sort and group, and stop there.
  • Most of your team never opens a repository. Notion needs no git account, and has desktop and mobile apps.
  • You want wikis, sites and forms in one tool for a whole company, well beyond engineering and product.

Moving over

The importer turns a Notion export into typed markdown documents, keeps the folder shape, turns database rows into frontmatter and rewrites the links between pages. See Switch from Notion.