Central LLM Wiki vs Obsidian
What Central LLM Wiki exports is an Obsidian vault. The question is who writes it, where it lives, and who can read it.
Choose Obsidian if
You like local files, the plugin ecosystem and organising by hand; you already have an Obsidian workflow and AI is an assistant.
Choose Central LLM Wiki if
You want to drop sources in and have the AI compile the wiki, shared between your phone, Cursor and Claude, without maintaining sync and plugins yourself.
| Feature | Obsidian | Central LLM Wiki |
|---|---|---|
| Who writes | You, or community plugins (including LLM-Wiki style compilers) | Built in: one click after a source lands in raw/, or hand it to your agent |
| Where the data lives | Local vault; optional Sync | The self-hosted environment you choose; export the whole vault any time |
| Agent access | No official MCP; community MCPs need the desktop app running | Built-in MCP server, token or OAuth, always on |
| Graph, backlinks, versions | Graph and backlinks are native; versions via Sync or git | All included: graph (filters, timeline), backlinks, a version per save with rollback |
| Bibliography | Not offered | DOI/BibTeX/CSL in and out, and [@citekey] citations |
| Deployment | The app is free to use; Sync costs extra | Self-host on infrastructure you control with the full feature set |
| Lock-in | None | None: Markdown zip export, open source, self-hostable |
Trade-offs we admit
- If your whole workflow lives in Obsidian, it wins on offline use, plugins and customisation; Central LLM Wiki shows only an offline page without a connection; there is no offline copy of the knowledge base.
- They are not exclusive: many people compile in Central LLM Wiki and export a zip into Obsidian to read.
- Prices are as published on Obsidian’s site.
Get started on your own serverTheir facts checked on 2026-09-04 · Obsidian Website