Unit tests for lore.Catch canon conflicts before they reach production.
DragonKeep checks new quests, dialogue, scripts, and narrative changes against the project's governed sources. Each finding points to the supporting evidence, and the reviewed decision stays with the change through history and handoff.
Your narrative owners stay authoritative. DragonKeep surfaces the evidence and keeps their decision with the change.
Start with the files you already have. No wiki, authoring, or production-tracker replacement is required for the first audit.
The production problem
Lore breaks in silence. The cost arrives later.
The approved world is scattered across bibles, scripts, tickets, chat, spreadsheets, and people. A line written eighteen months ago conflicts with a scene being written today. It survives review because the one person who would notice is already a bottleneck.
In the draft
One editorial fix
The sentence is still cheap to change and the writer still has the context.
After script lock
Another review cycle
Design, narrative, QA, or a licensor has to reopen an approved decision.
After VO and localization
Multiplied production work
Pickups, retranslated lines, partner re-approval, and schedule risk compound.
DragonKeep moves the catch toward the draft—where the correction costs the least it ever will.
Evidence before assertion
A finding your team can inspect—in the real product.
This is the running Studio surface, not a mockup. Every finding shows the proposed claim, the governed source it contradicts, and where that evidence lives—then waits for the narrative owner to decide.
- Proposed claim. The new line entering the world, checked as it was written.
- Conflicting source. The governed passage it breaks, down to the exact file location.
- Human resolution. Correct, accept, suppress, or record an exception—kept with the change.
The checked-change loop
From governed source to production handoff.
A controlled evidence and review layer between the narrative sources you already have and the work moving downstream.
Ask with evidence
Get a project-grounded answer and open the cited sources. If approved sources disagree, see the disagreement.
Check the change
Run a check at file, draft, or bounded project scope. Inspect the claim, severity, and supporting passages.
Decide as a team
Correct, accept, suppress, or record an exception. The narrative owner remains authoritative.
Keep the history
Carry the reviewed decision through the diff, ChangeSet, approval history, and agreed handoff format.
Design partner pilot
Start with a result, not a rollout.
Every pilot starts with a canon-risk audit of one agreed corpus — no authoring migration required. You receive a coverage map, cited findings, a human-reviewed risk list, and hands-on onboarding, with success criteria agreed before we start.
Pilot offer
$500
One project · design partner program
- Canon-risk audit with cited findings on your material
- Hands-on onboarding and direct roadmap influence
- Export or deletion at the agreed close
- Credited in full toward your first annual license
Pricing
Priced by editor seats. Free for everyone who relies on canon.
Only the people who change canon need a licensed seat. Everyone else — artists, QA, localization, producers — reads, searches, and gets cited answers free.
Design Partner Pilot
$500
One project · credited in full toward the first year
Studio
$25 / editor seat / mo
Billed annually ($30 monthly) · viewer seats free · 3-seat minimum
Enterprise & self-hosted
Custom
Your infrastructure, your model providers · franchise scale
A three-editor indie team runs on $900 a year; a ten-editor production team on $3,000. Founding design partners lock today's seat pricing for two years.
Deployment and control
Deployment is part of the scope, not a footnote.
Studio runs on our managed cloud deployment by default — nothing to install. Before content moves, we document where it is processed, which model and infrastructure are used, who can access it, what is logged, how long it is retained, and when it is exported or deleted. Customer-hosted and local-model configurations are available at enterprise scope.
AI-assisted changes do not silently write to governed files; they enter the same reviewable ChangeSet path as other proposed edits.
Review the deployment postureWho it is for
Teams accountable for a world that has to survive production.
Narrative-heavy studios
Multi-writer teams protecting a growing world while quests, dialogue, live content, VO, and localization move in parallel.
Teams inheriting a world
Franchise handoffs, co-development, and licensed IP where the canon arrived as documents but the reasons stayed with the previous team.
Narrative and production leads
The people accountable for continuity who need shared, cited project memory without becoming a permanent lookup bottleneck.
Questions buyers ask
Clear limits build useful trust.
Does DragonKeep replace our wiki or production tracker?
No. The first audit is additive and can begin with exported or connected source material. Deeper workflow adoption is proved during the pilot.
Does DragonKeep decide what is canon?
No. DragonKeep surfaces evidence and keeps the narrative owner’s resolution with the change. A finding is evidence for review, not an automatic declaration of truth.
Is contradiction detection exhaustive?
No automated reviewer should claim that. DragonKeep prioritizes supported findings, exposes the corpus boundary, and lets the team review the evidence behind each surfaced risk.
Is this an AI writing tool?
No. Studio is positioned around cited recall, contradiction review, and governed change. AI-assisted work stays secondary, reviewable, and cannot silently become canon.
Where is our content processed?
Pilots and standard licenses run on our managed cloud deployment by default. Customer-hosted and local-model configurations are available at enterprise scope. Either way, before content moves, the hosting mode, model provider, access, retention, export, and deletion path are documented and approved.
See it on material that matters.
Request a focused demo, or start with a $500 pilot and keep your current tools.