LoreHub
Dialogue BuilderWorldbuilderPricingDocumentationGuidesNews
LoginStart Free
For narrative leads who need the whole studio on board

Ship branching stories your whole studio can trust

LoreHub is where writers, narrative designers, translators and programmers work on the same story at the same time. It checks every route between your dialogues, keeps every translation in step with its line and records who changed what, so the problems your producer worries about are caught while you write, not in QA.
Start FreeWhat your team getsBook a team demo
CI  ·  pull request #42
Check failed
LoreHub  /  arc_1_war  /  Tom at the mill

Writers build each scene visually, the route planner checks how scenes connect, and the osf command line tool runs the same checks on every pull request.

Built to get a yes

Everyone who signs off gets a reason to say yes

You know your team needs a better way to write branching dialogue. Here is what LoreHub changes for each person you need on your side.

You, the narrative lead
Stop being the human link checker
See every route between your dialogues, and where a player can arrive in a state a scene doesn't accept.
Writers, designers and translators work in the same story at once, without overwriting each other.
Every change has a name and a time, and any change can be reverted.
Your producer
Fewer late surprises in the schedule
Broken routes, dead ends and missing translations show up while the scene is written, not in QA.
Each language shows what is missing, outdated or falling back, and what blocks the build.
A price per world, not per seat: Team is €29 a month for up to 10 people.
Your programmers
Clean data and no tool to maintain
Engine-independent JSON for Unity, Unreal, Godot or your own engine, with every language included.
Stories as plain-text files in Git or Perforce, reviewed as normal diffs.
The osf command line tool runs the same checks on every pull request.
Your studio head and IT
Low risk to adopt, easy to leave
Hosted on Microsoft Azure in the EU. Enterprise adds SSO and a private dedicated tenant.
Your story is saved in an open format, so it is never locked inside LoreHub.
Every feature on every plan: start free and pay only for more capacity.
What your team gets

Everything a narrative team needs, on every plan

Plans differ in capacity and seats, never in features.

Dialogue Builder
Visual canvas for branching dialogue: nodes, player options and links
Variables and conditions that lock or open options
Play any dialogue in the browser while you build
Fix a line while you play and see it right away
Learn more
Route planner
New
One map of how your dialogues connect, from START to END
What each dialogue requires and produces
Every link checked as OK, partly OK or a conflict
Learn more
Localisation
Translate every line in the Translate tab, with no language caps
Enforced or fallback, set for each language
Translations marked outdated when their source line changes
Every language included in the export
Missing translations reported in the Problems panel and osf validate
Working together
Live presence and edits without reloading
History and revert for every line
Owner, writer, artist and viewer roles for every member
Learn more
Worldbuilder
Wiki of lore documents for characters, places and factions
Custom relations between documents, in editable tables
Art gallery with the entities marked on each picture
Timeline of events, from minutes to decades
Learn more
Export and integration
JSON export (Export Schema v1 and v2) for Unity, Unreal, Godot or any engine
Stories as OSF plain text in Git or Perforce
The osf command line tool checks every pull request
A documented API for your tools and CI/CD
The LoreHub interface in 8 languages
For your tech lead

An open foundation your programmers will approve

.osfin Git or PerforceLoreHubvisual editorVS CodecodeCode reviewreview diffsOther OSF toolsand AI tools
Your story stays yours

LoreHub saves to an open format instead of a private database. Keep the files in Git or Perforce next to your game, review every change like any other code change, and open them in any tool that speaks OSF. If you ever leave LoreHub, your story comes with you.

Example output
Catch story bugs before QA does

Validation checks the schema, every jump between dialogues, every character and variable reference, unreachable nodes and missing translations. The osf command line tool runs the same checks on every pull request.

AI draftnew scene.osfplain textValidate✓ checksReviewyour teamerrors go back before anyone merges
Ready for AI, with a safety net

Plain text with a strict schema is easy for AI assistants to read and write. Run validation on every AI edit to catch broken links and missing translations, then review it as a normal diff.

Dialogue.01_intro_scene.nodes.node_03.content.text
Eng
Am I dreaming?
source
Rus
Я сплю?
enforced ✓
Zho
我在做梦吗？
enforced ✓
Jpn
Am I dreaming?
falls back to Eng
Translations built in

Every line has a stable key, and translations mirror your story files. For each language you decide whether a missing line blocks the build or falls back to the source, so you can ship a language early and finish it later.

Open format
Plain text in Git or Perforce
Versioned spec, upgrades are explicit
For your programmers: how a change reaches the game

From a writer's edit to a playable scene

  1. 1
    Write
    LoreHub
    LoreHub or plain OSF

    A writer changes a scene in the LoreHub visual editor, or edits the .osf file directly in any text editor. Either way the result is a plain .osf file.

  2. 2
    Review
    Git or Perforce

    The change arrives as a normal diff. A developer reviews it like any other code change, in a pull request or a Perforce changelist.

  3. 3
    Check
    osf validate

    Broken jumps, unknown characters and variables, unreachable nodes and missing translations are reported with file and line.

  4. 4
    Build
    osf build

    The project compiles to JSON or YAML, one resource per dialogue, character and variable.

  5. 5
    Play
    LoreHub
    CLI, LoreHub or your engine

    Play the scene in the terminal with the osf CLI, in the LoreHub dialogue player, or load the JSON or YAML in your game engine.

Make the case

Get a yes in two weeks, with one scene

You don't need a migration plan to win the decision. Run one scene through LoreHub, then show your team what it caught.

  1. 1
    Week 1: pick one scene

    Choose a branching scene that already gave you trouble and rebuild it on the Free plan with the people who work on it.

  2. 2
    Week 2: run it the new way

    Link its dialogues on the route map, add a language, and let writers and translators work on it at the same time.

  3. 3
    Then: show what it caught

    Bring the route conflicts, outdated translations and change history to your producer and tech lead. We can join that call.

What to tell your producer
Free plan for 3 people to run the trial
Every feature on every plan; Team is €29 a month per world
EU hosting on Microsoft Azure; SSO on Enterprise
Open format: the story stays ours if we leave
Book a demo for your teamOpen the Trust Center
FAQ

Questions your team will ask

Something else on your mind? Ask us on the demo call.

Book a team demo

Bring your team, we'll bring the answers

In 30 minutes we show the route planner, localisation and export on one of your scenes, answer your producer's and programmers' questions, and agree on a two-week trial you can run on your own.
The route planner, localisation and export on your scene
Your producer's and programmers' questions, answered
A two-week trial plan you can run on the Free plan
Open the booking page