At first glance, the Obsidian Canvas vs. Heptabase debate looks like a choice between two similar spatial note-taking tools. Both give you an infinite 2D canvas, both let you arrange notes side by side, and both let you draw arrows between ideas. Under the hood, however, their data architectures are fundamentally opposite.
The short answer: Obsidian Canvas stores visual arrangements inside individual .canvas files using the open JSON Canvas format. In Heptabase, whiteboards are non-owning visual views over a central card library. In practice, this means a line drawn on an Obsidian Canvas creates no link between notes in your vault, while a line drawn on a Heptabase whiteboard creates a connection both cards remember.
In short: Obsidian’s connections are portable across external tools but unindexed in your vault’s graph; Heptabase’s connections are indexed across your cards but locked into its proprietary ecosystem. If you are trying to decide whether to build your long-term knowledge workflow in Obsidian Canvas or invest in a dedicated spatial tool like Heptabase, looking at UI features won't give you the answer. You have to look at how each tool models files, cards, and context.
Architectural Breakdown: Obsidian Canvas vs. Heptabase
Architectural Dimension Obsidian Canvas Heptabase
First-Class Citizen Files (.md notes and .canvas files) Atomic Cards (Global entities across the workspace)
Spatial Organization Embeds Markdown files or local text cards inside an open JSON Canvas file Maps global cards as live views across multiple whiteboards simultaneously
What Connection Lines Mean Visual coordinates stored in the board file; portable across tools, but unindexed in the vault graph Relational connections surfaced in the Card Info panel; indexed in the workspace, but locked into the app
Context Awareness Canvas-bound: Context lives in the canvas file, not in the note itself Context-aware: Every card tracks all whiteboards it belongs to and all connected cards
Portability vs. Indexing Portable, but unindexed: The .canvas file uses open JSON Canvas, but notes remain unaware of connections Indexed, but proprietary: Connections compound across boards, but cannot be exported as an open interactive graph
Best Fit Project roadmaps, system architecture diagrams, and visual brainstorming sketches Cumulative research and long-term thinking bridging spatial exploration and linear writing
Source: Hacker News · Summarized by HeadlinesBriefing