Live public example
Read a real LoreBranch chapter
LoreBranch is already serving public fiction with live chapter reading, visible release diffs, and block-level reader signals.
For fiction writers and readers
LoreBranch helps writers publish stories that change over time.
Built for novelists, serial writers, and worldbuilders who keep revising. Writers can publish updates as they go. Readers can read the latest version, look back at older versions, and see what changed.
Made for writers who revise as they build. Want the simple version? Read the FAQ. Want to write on LoreBranch? Join the beta
Built for a real beta
Trust signals that do not depend on future promises.
LoreBranch already ships account export, series export for collaborators, deletion controls, documented beta limitations, and a direct support route. The point is to prove the product in public, not ask for blind trust first.
Portability
Your writing stays yours.
Signed-in users can already export account-linked data. Series collaborators can also download one canon as JSON with chapters, immutable versions, Decision Log entries, The Canon Engine, and Timeline nodes.
Read privacy baselineClosed beta scope
The limitations are documented, not hidden.
LoreBranch is early software, but the beta notes already spell out what is live, what is limited, and when resets could happen.
Read beta notesSupport route
Privacy, safety, and bug reports have a real path.
The support flow is already wired for operational help, privacy requests, and safety issues instead of waiting on a future launch desk.
Open supportHow it works
The platform
Version control for the written word.
LoreBranch is built around a Git-style writing model: chapter versions, public diffs, trusted suggestions, and feedback anchored to the text that caused it.
Commit-based chapters
Every draft save can become a permanent record.
Attach a commit message to meaningful revisions. LoreBranch builds a readable changelog so the shape of a chapter is never lost.
Readable diffs
Compare versions without losing the prose.
See what changed between chapter versions in a fiction-first layout, with additions and removals kept in story context.
Anchored feedback
Reader signals attach to the exact passage.
Comments, reactions, confusion notes, typo marks, and edit suggestions can stay tied to a block as the chapter evolves.
Single canon
Collaboration supports the author's line.
Trusted readers can suggest edits. Authors decide what lands. The published story remains one canonical branch.
Readable diffs
Revisions that read like prose.
Compare any two chapter versions. Changes surface in context, so every edit can be judged against the surrounding scene.
Chapter 7 - The Duela3f9c12 to 77b2e40
+14 / -9 linesThe square was empty save for the two of them.
-He drew first. The shot echoed off the cobbles and it was over.
+He stood still. She could hear his breathing - shallow, too fast.
+Neither of them moved for what felt like half a minute.
+Then his hand went to the pistol, almost reluctantly, and the world folded.
She did not look at him after.
- end of section -
Anchored feedback
Signals that stay with the text.
Reactions, confusion marks, typo notes, plot-hole signals, comments, and edit suggestions attach to a specific passage instead of floating loose in a review thread.
The letter had no date. She turned it over twice looking for one, but there was only the handwriting - small and careful, nothing like her mother's usual scrawl.
She read it standing up, by the window, not trusting herself to sit. The words did not change no matter how many times she went back to them.
Outside the street was getting dark. She folded the letter and put it exactly where she had found it.
For readers
Read stories while they are being sharpened.
Browse public fiction, inspect what changed between releases, react to exact passages, and become a trusted reader whose signals land in the manuscript instead of drifting into a loose comment thread.
Read a live chapterFor authors
Keep manuscript, canon, and revision history together.
The author base opens into LoreBranch Git, The Canon Engine, the Timeline, and the Decision Log, so the public story and the private working memory stay on one line.
Join the beta