Compare
Kition vs Notion
Notion is great for light collaboration and presentation. Kition is for local-first work where the agent actually ships things. Different problems.
In one paragraph
Notion stores everything in a proprietary block model in the cloud — slick UX but your data is locked. Kition stores .md on disk — slightly more "software-feeling" UX, but the data is yours and the agent can do more.
Feature-by-feature
| Capability | Kition | Notion |
|---|---|---|
| Content stored as Markdown | ✓ Yes | ✗ No |
| Fully offline-capable | ✓ Yes | ✗ No |
| AI agent can run commands | ✓ Yes | ✗ No |
| AI agent applies file patches | ✓ Yes | ✗ No |
| Real browser agent | ✓ Yes | ✗ No |
| MCP integrations | ✓ Yes | ✗ No |
| Hooks / audit interception | ✓ Yes | ✗ No |
| Multi-user team collaboration | 〜 Partial | ✓ Yes |
| Rich block embeds | 〜 Partial | ✓ Yes |
| Public publishing | 〜 Partial | ✓ Yes |
Where Kition wins
- Data stays 100% local
- Agent actually ships (files, commands, browser)
- Bring your own model — no vendor lock-in
- Buy once, leave anytime
- Hooks make AI behavior auditable
Where Notion still wins
- Real-time team collaboration is still smoother on Notion
- Richer media block embeds
- "Public site" publishing is one click on Notion
Our recommendation
If your work is "solo or small team + lots of AI execution + sensitive data", pick Kition. If it is "30-person company wiki + lots of co-editing", Notion is still solid.
Ready when you are.
Kition is a local-first AI workspace. Markdown documents, structured tables, and an AI agent — running on your own machine, against the model provider you choose.