Compare
Kiori vs Capacities
Knowledge Compounding vs Object-Based Note-Taking
The short version
Capacities rethinks note organization around objects. Instead of pages and folders, everything is a typed object (person, book, meeting, project) connected in a knowledge graph. The structure is the product.
Kiori focuses on what you do with knowledge after it's organized. Upload documents, get cited AI answers, curate insights visually, and create new pages that automatically feed back into your knowledge base. The loop is the product.
Feature Comparison
| Feature | Kiori | Capacities |
|---|---|---|
| AI retrieval | Built-in with confidence scores and source citations | AI assistant available on Pro plan, no confidence grounding |
| Organization model | Documents, pages, canvases. Flat structure with AI retrieval. | Object-based: typed objects (person, book, meeting) with custom types |
| Knowledge graph | No graph view. Relies on AI retrieval to surface connections. | Built-in bidirectional linking and knowledge graph |
| Visual knowledge mapping | Canvases with 14+ card types, spatial drag-and-drop | No canvas/spatial view. Graph view for linked objects. |
| Public workspaces | Native. Share knowledge bases publicly with AI Q&A for visitors. | No public sharing |
| Document import | 15+ formats with OCR (PDF, DOCX, slides) | Limited. Primarily manual note creation. |
| Daily notes | Not a core feature | Built-in daily notes with calendar integration |
| Calendar integration | No | Events become objects, linked to notes and tasks |
When to choose Capacities
- •You think in objects and relationships, not documents. You want to model people, books, meetings, and projects as connected entities.
- •Daily notes and calendar integration are central to your workflow.
- •You want a knowledge graph that visualizes how your ideas connect.
- •You prefer building structure manually over relying on AI to surface things.
- •You need good mobile apps for capture on the go.
When to choose Kiori
- You work with existing documents (PDFs, research papers, reports) rather than creating notes from scratch.
- You want AI answers grounded in your content with source citations.
- You need visual canvases for spatial thinking and curation, not just a graph view.
- You want to share knowledge publicly: wikis, community pages, team resources.
- You need multimodal search across images, audio, and video.
- EU data residency matters to you.
- You want a compounding loop where creating new pages automatically enriches your knowledge base.
The philosophical difference
Capacities asks: "How do I model the structure of what I know?" Kiori asks: "How do I build on what I already know?"
Capacities gives you powerful tools for structuring knowledge. Objects, types, properties, a graph. If you enjoy building taxonomies and seeing how entities relate, it's one of the best tools for that.
Kiori skips the taxonomy step. You upload your documents, the AI retrieves what's relevant, you curate on canvases, and you create pages that feed back into the system. The structure emerges from use rather than upfront design.
Both approaches work. The question is whether you want to spend time modeling knowledge or working with it.