An all-in-one cloud workspace where a "note" is a database record with typed properties — title, status, tags, dates, relations to other records. Structure comes from relations, rollups, and multiple filtered views over the same underlying data, not from folders.
Best-in-class structured tagging — typed properties, cross-table relations, rollup aggregation, and task-specific views (Kanban, Calendar, Gallery) over one shared dataset. Mature collaboration, templates (Thomas Frank's Ultimate Brain, August Bradley's PPV), Notion AI, and a genuinely large existing user base. Free for a single user, paid per-seat for team plans — cost that scales with headcount rather than usage, the opposite of Mimir's per-token ingestion cost.
Both reject "which folder?" in favour of tag/facet-driven retrieval, and both front their store with a serving-layer API rather than raw file access — the Notion API plays a similar automation role to Mimir's serving core, just without a lens engine behind it.
A compulsory governance layer Notion has no equivalent of — Notion's sharing permissions decide who can see a page, not whether a standard gets force-injected into a relevant answer. Mimir's classification tiers are enforced by the database itself (Postgres row-level security) rather than page-sharing settings, and its storage is an open Postgres schema rather than a proprietary block format — our research notes Notion's own export is documented as lossy: relations, rollups, and formula properties don't survive a migration out cleanly.
Notion's relational model — typed properties, rollups, and simultaneous filtered views of one dataset — is more mature and more usable today than Mimir's four blunt facets (tags, domain, classification, principal); closing that gap is now a named roadmap item. Notion also has a mature template ecosystem and a far deeper automation surface (Zapier, Make, Readwise, the Notion API) than Mimir's six-endpoint daemon.
Worth splitting, because "Notion has multiplayer" actually bundles two different things. Multi-user access with permissions — several people, and their agents, working against one shared Well, each seeing only what their role permits — is not a Notion advantage: it's core to Mimir's design, already in the hardening chain (see the governance walkthrough), not a gap. What Notion does have that Mimir doesn't yet is real-time collaborative editing — simultaneous cursors, live presence, and a CRDT merge on the same page. That's the genuine, specific gap, and it's now on the roadmap, scoped to the note/wiki/canvas surfaces where it actually matters.
Grounded in our research on the relational-database-first school.