SiYuan: Refactor Notes Like Code Without Broken Links
SiYuan uses permanent block IDs for unbreakable references and built-in SQL databases, letting developers organize technical notes like structured codebases locally, outperforming Obsidian's file links and Notion's cloud lock-in.
Permanent Block IDs Enable Refactoring Without Breaks
Link to specific blocks (paragraphs, lists, code snippets) using unique, permanent IDs instead of file paths. Move or reorganize content freely—the embedded references stay intact, eliminating broken links common in Markdown folders or Obsidian vaults. For example, embed a Python code block in multiple notes; relocate the original, and all embeds update automatically. This shifts focus from file locations to utility, ideal for docs, bug tracking, or architecture diagrams where knowledge evolves.
Add interactive graph views to visualize block connections, revealing how bugs link to tasks or decisions tie to code snippets. Self-host via Docker Compose in 1-2 minutes for full local control and offline access.
Built-in SQL Databases Structure Dev Knowledge
Create task databases with fields like status and priority directly in notes. Query them inline with SQL—no plugins needed—for filtering high-priority bugs or overdue tasks. This turns scattered notes into a structured system design document or personal wiki, supporting project docs, code snippets, and knowledge bases.
Unlike plugin-dependent tools, databases are native, with export to Markdown available. Graph views integrate seamlessly, showing relational pins across your workspace.
Outperforms Obsidian and Notion for Local Power
Obsidian's file-based linking breaks on refactors; SiYuan's block-level granularity feels like a structured system. Notion offers similar blocks and databases but requires cloud subscription and lacks ownership—SiYuan delivers both locally and open-source, free of vendor lock-in.
Devs switch for stable large workspaces, fast updates, and performance on huge note sets (run occasional optimizations). Use SiYuan if notes grow into long-term systems; stick with Obsidian for Markdown/plugin-heavy setups or Notion if deeply invested despite switching pain.
Key Trade-offs: Ownership vs Familiarity
Pros: Unbreakable links stabilize big notes; Docker self-hosting; native SQL outperforms plugin hunts; Notion-like UI with graph interactivity.
Cons: Stores in proprietary .psi format (not plain Markdown); smaller English plugin ecosystem (Chinese-origin); UI feels dated to some; large workspaces need optimization.
Try if current tools fail on structure—import existing notes and test block embeds on a project doc to validate fit.