Notion for your team. Markbase for your agents.

Notion is a workspace for humans collaborating. Blocks, mentions, comments, databases, presence, permissions, beautiful pages. For docs your team reads and edits together, it's hard to beat.

Markbase doesn't try to compete with any of that.

Where Notion stops being enough for agents

The moment Notion stops being the thing humans look at and starts being the place agents read and write, three things bite.

1. It isn't pure markdown. Notion's content model is blocks. When an agent reads a page, what comes back isn't the markdown it wrote — it's been parsed, restructured, and serialized through a block tree. Round-tripping markdown through Notion is lossy, and agents end up reasoning about a format that isn't the one they were trained on.

2. It's built for human collaboration, not agent collaboration. Comments, mentions, real-time presence, rich permissions, database views — these are strengths for a team and friction for an agent. The agent doesn't need a comment thread. It needs a file, a read, a write, an answer. Every feature that costs you nothing as a human costs an agent surface area, latency, and a chance to do the wrong thing.

3. There's no native concurrency primitive. Run two agents in parallel against the same page and one overwrites the other. There's no ETag, no If-Match, no "fail if it changed since I read it." Last write wins, silently. For an agentic system, that's the bug.

Conventions agents actually follow

Notion has rich structure for humans — databases, properties, templates, page hierarchies. None of it is something an agent reads as instructions. If you want a fleet of agents to follow a convention ("decisions go in this database, with these properties; bug postmortems go in that one") you encode it as a prompt in each harness. The opinion lives outside the data, replicated by hand into every place an agent runs.

Markbase puts the opinion inside the memory store. Every folder can carry an _markbase.md: what this folder is for, how docs in it are organized, what frontmatter they need, who's allowed to write here. Agents read the _markbase.md chain root-to-leaf before acting on a path and apply the conventions they find. The rules travel with the data — you write them once, every agent picks them up.

Use both

This isn't a migration story. It's a layering story.

• Keep Notion as your team's workspace — docs, OKRs, meeting notes, the things humans read.
• Put Markbase underneath your agents — the memory they reach for between turns, between sessions, between models.
• Bridge them where useful: have an agent summarize a Notion doc into Markbase, or publish a Markbase doc up to Notion for human review.