Comparison
Calliope vs Obsidian
A blank, infinitely flexible graph you shape into a writing system — or a fiction editor where the writing system is already there.
| Calliope | Obsidian | |
|---|---|---|
| Purpose-built for fiction | A fiction editor — book, parts, chapters, and a cast are first-class | A general-purpose knowledge base; fiction is one of many uses |
| Story bible / canon | The Map is built in — characters, locations, facts you own | You build one yourself from folders, backlinks, and plugins |
| Consistency aimed at your prose | Author-triggered checks measure your prose against your canon | None — links and search, but no consistency pass on your writing |
| AI companion | Built-in, augmentation-only — never writes your prose | Community or bring-your-own-key plugins; nothing native |
| Setup | Zero-config — you land in the editor and write | Flexible, but you assemble the writing system yourself |
| Manuscript export | Free export to DOCX, EPUB, PDF, Google Docs, or Markdown | Markdown by default; formatted export via plugins |
Obsidian is excellent, and it deserves to be said plainly. It is local-first, private, free to use, and quietly beloved — a Markdown knowledge base built on linked notes and a graph you can bend to almost any shape. Many writers keep their whole world in it: a story bible stitched together from folders, backlinks, and a well-chosen stack of community plugins.
Calliope is a narrower thing on purpose. It is not a knowledge base you could shape into a writing tool — it is a writing tool for long-form fiction, and only that. The difference between the two is mostly the difference between a blank canvas and a built surface.
The flexibility, and its cost
Obsidian’s great strength is that it assumes nothing. It hands you an empty, infinitely flexible graph and lets you invent the system that fits your book. That freedom is real, and for some writers it is exactly right.
It is also the setup burden. Before Obsidian holds your story the way you want, you have to decide the folder structure, the note conventions, which plugins to trust, how backlinks stand in for a cast list. Nothing about the manuscript — parts, chapters, a sense of the whole book — is native; you model it. The tool is powerful because it is general, and general is work.
What comes built-in instead
Calliope starts from the other end. The book structure — parts, chapters, a manuscript — is already there. The story bible is the Map: characters, locations, and facts as records you own, that the editor recognises inside your prose and can jump to. Consistency checking is built in too — an author-triggered pass that measures your own writing against your own canon and leaves calm margin notes where something drifted. And the AI is a companion in the margin that researches and checks with you, never a blank plugin slot to wire up.
There is nothing to assemble. You land in the editor and write, and the writing system is already around you.
The honest trade
Obsidian is more flexible and more fully yours — local by default, free, portable Markdown, a plugin for nearly anything. If you want to own every layer of your setup and you enjoy building the system, it is a superb choice, and Calliope deliberately doesn’t compete on that ground.
When Calliope is the better choice
If you’d rather not build a writing system before you write in it — if you want the story bible, the consistency checks, and an AI companion to be there on the first day, purpose-built for fiction — Calliope is that tool. And the one line that never moves: its AI helps you write, but it will never write your prose.
Write with help. Without the ghostwriter.
Calliope is the purpose-built fiction alternative to Obsidian — the story bible, prose consistency checking, and an augmentation-only AI companion come built-in and zero-config, instead of assembled from folders and plugins.
Start for free