Overview

Capacities is an object-based knowledge-worker tool (capacities.io) that turns ideas into connected objects — people, books, projects, ideas — rather than files in folders. It is a commercial alternative to the markdown-native LLM Wiki approach, emphasizing objects, properties, and connections over file hierarchies.

Key Facts

  • Type: object-based knowledge tool (not markdown-native)
  • Audience: knowledge workers wanting structured objects; writers, researchers, students, developers, founders
  • Paradigm: “think in things, not files” — everything becomes an object with properties and connections
  • Userbase: 50,000+ knowledge workers; Product Hunt “Product of the Day”; featured in Fast Company
  • Features:
    • Daily notes as inbox (no upfront organization)
    • Backlinks and “Related Content” (auto-discovers implicit connections)
    • Custom object types (create types as you go)
    • No configuration, no markdown syntax, no plugin management
    • Full export to standard formats (no lock-in)
  • Privacy: Hosted in Europe, GDPR compliant, encrypted servers, certified EU data centers
  • Business model: User-funded (no VCs), free forever plan (no credit card required)

Relationships

  • “belongs-to” second-brain — a second-brain tool

  • “contradicts” knowledge-management-approaches-vs-llm-wiki — contrast: object-based vs artifact-first markdown

  • “sibling-of” obsidian — sibling PKM front-end (Obsidian is markdown-native; Capacities is object-based)

  • “sibling-of” llm-wiki — alternative approach to personal knowledge

  • “sibling-of” notion — sibling commercial PKM tool (Notion is team-focused; Capacities is individual-focused)

Implications

Capacities represents the “structured objects, not files” branch of PKM — a different paradigm from this vault’s markdown+frontmatter. Its “related content” auto-discovery mirrors the compounding invariant of wikis (connections emerge), but implemented via object properties rather than wikilinks. Useful as a contrast case in the knowledge-management comparison. The user-funded model and “no collaboration chaos” stance positions it distinctly from enterprise-focused tools.

Sources