Story Bible Software
A living story bible connected to the novel you write.
A story bible should not become another document you have to maintain by hand. Lokee connects structured characters, relationships, locations, and events to the manuscript itself, so the reference material can evolve with the story.
Try the story bible demo →Four views of one story fact
A single fact — Sera Nightingale, known to the Ashen Circle only as “Kestrel” — shown from the manuscript, the entity card, the relationship graph, and the plot board. This is the actual seeded content in Lokee’s public demo.
Manuscript — Chapter 1
“Rowan knew who he meant before he turned. @Sera Nightingalesat with her hood low... Most of the Circle knew her only as Kestrel.”
Entity card
Sera Nightingale
Alias: Kestrel · Character · Rowan’s contact inside the Ashen Circle
Relationship graph
Sera Nightingale —member of→ The Ashen Circle
Plot board (Sticky Mindmap)
“Sera / ‘Kestrel’ — Circle contact” note, linked to her entity card
What a story bible must solve in a complex novel
A novel with more than a handful of characters, locations, and factions quickly outgrows what a person can hold in their head. A story bible exists to answer one question fast: what do I already know about this? The harder it is to answer, the more continuity errors slip through.
Why static documents and spreadsheets drift out of date
A Google Doc or spreadsheet story bible only stays accurate if you remember to update it every time something changes in the manuscript — and most writers don’t, because the bible lives in a different window than the writing. The two documents drift apart until the bible can no longer be trusted.
Write or import an existing manuscript
Start a new manuscript directly in Lokee Writer, or import an existing .docx and get a proposed chapter structure to review before committing it. Either way, the manuscript and the story bible share the same vault from the start.
Connect characters and story facts to the text
Mention a character while writing and it links to their entity record with a rename-proof reference — rename the character later and every mention across the manuscript still resolves correctly.
Review extracted information instead of entering everything manually
Run AI extraction on a chapter, a selection, or the whole book, and review proposed characters, relationships, attributes, and events before anything is written into your vault. Nothing is added automatically.
Explore relationships and chronology
Open the relationship graph to see how everyone connects, or the timeline to see when things happened and to whom — both stay in sync with the same entity records the manuscript links to.
Keep local control and exportability
A local vault is a folder of readable JSON files on your own machine — no account required, nothing uploaded unless you turn on Sync. Export your manuscript to Word, PDF, or Markdown at any time.
Who should use Lokee as a story bible
Novelists writing a single complex book, authors managing a multi-book series, and worldbuilders who need their reference material to stay trustworthy as the story grows.
FAQ
What is a story bible?
A structured reference of everything true about your fictional world — characters, locations, relationships, and events — kept separate from the manuscript prose so you can check facts without re-reading chapters.
Can Lokee create a story bible from an existing manuscript?
Yes. Import a .docx and run AI extraction to propose characters, relationships, attributes, and events from your existing text; you review and approve each suggestion before it becomes part of your vault.
Is Lokee suitable for a multi-book series?
Yes — a vault isn’t scoped to a single manuscript. Entities, relationships, and timelines persist across books in the same series.
Does AI decide which facts are correct?
No. AI only proposes candidates from text you choose to run it on. You accept, reject, or edit every suggestion — nothing is written into your vault automatically.
Can I export my story bible?
You can export manuscripts to Word, PDF, or Markdown. Entity and relationship data lives in your vault’s local JSON files, readable without the app.
Can I use it offline?
Yes. A local vault runs fully offline on desktop — no account or internet connection required unless you enable Sync.