About Lore Engine
An interactive, spoiler-filtered atlas for the sprawling story worlds that consume us. Built by hand, paced by chapters, and guarded against the accidental discovery of tomorrow’s tragedies.
The Problem We Kept Running Into: The “Wiki Trap”
Every obsessive reader knows the exact feeling. You are on chapter fourteen of a sweeping, thousand-page epic. You’re utterly enthralled, but sixty-four different characters have stepped onstage with names that sound like unpronounceable spells. A squad captain walks through the tent flap, and you pause: Wait, was this the guy from the siege of Pale, or did he march with the host in Seven Cities?
You turn to Google or the community fandom wiki for a quick sanity check. You only wanted to remember his rank or who his commanding officer was. But before your eyes can even find the first paragraph, the bold infobox at the top announces in plain text:
Status: Deceased (Beheaded during the Betrayal of Book 5, Chapter 22)
“Former soldier whose secret identity as the prophesied traitor was revealed following the fall of the capital...”
Just like that, three books of tension vanish in four seconds. The wonder of the slow burn, the calculated dread of foreshadowing, the shock of a hard-won reveal—ruined by an unshielded database.
We built Lore Engine because we believe complex fiction deserves better tools. We wanted a reading companion where time freezes right where you put your bookmark down. If you are on Book 2, Milestone 4, nothing beyond that chapter exists in this engine. Attributes, allegiances, titles, fallen comrades, and even visual portraits reflect only the exact truth of the story as you have experienced it so far.
Crafting Each Universe with Intention
The easiest way to build a wiki platform is to create a single generic database schema, slap on an off-the-shelf theme, and dump scraped paragraphs into identical boxes. But great worlds do not feel identical, and navigating them shouldn’t either.
In Lore Engine, every universe is an independent bespoke tenant with its own visual language, custom telemetry, and narrative architecture:
Malazan: Book of the Fallen
Steven Erikson & Ian C. Esslemont
Ten monumental volumes of empires, ascendants, Warrens, and tragic mortal squads marching across dust-choked continents. A world where mortal bone and divine will clash in blinding convergences.
Aesthetic: Ancient parchment tones, weathered bronze, quiet sorcery, and tactical campaign field dossiers.
Dungeon Crawler Carl
Matt Dinniman
Earth is flattened into an 18-level underground reality show televised to a sadistic galaxy. A man in heart-print boxer shorts, an aristocratic Persian cat, and an increasingly psychotic AI.
Aesthetic: Hazard stripes, glitchy broadcast telemetry, synth-amber CRT flickers, and caustic AI achievement readouts.
Halo Archive
Bungie, 343 Industries & Greg Bear
Humanity’s desperate stand against the Covenant hegemony, ancient Forerunner ringworlds, Flood bio-terrors, and the solitary weight of the Spartan-II program.
Aesthetic: UNSC cold emerald telemetry, Cole Protocol command terminals, and tactical waypoint scanlines.
We deliberately prioritize quality over volume. There are dozens of fantasy sagas, sci-fi franchises, and tabletop campaigns we would jump at the chance to support. But each one demands hundreds of hours of manual narrative milestone indexing, custom image generation pipelines, and nuanced timeline verification.
“We would rather build three universes with obsessive care, gorgeous art, and bulletproof spoiler shields than churn out fifty hollow wiki shells that fail the reader when it matters most.”
Who We Are
Lore Engine is not a venture-backed startup. There are no pitch decks, no aggressive growth metrics, and no intrusive ads crowding out the lore.
We are a small circle of friends, software engineers, and hopelessly passionate readers who spend our weekends tinkering on open-source web tech, generative art models, and reading companions. We build Lore Engine because it is the exact tool we wish had existed when we cracked open our first Steven Erikson brick or listened to Jeff Hays narrate Carl and Donut plunging into the World Dungeon.
Everything in this project—from the Turborepo monorepo plumbing to the custom ComfyUI diffusion workflows and pure state reducers—is written with genuine joy and craftsman pride.
Join the Conversation & Suggest Lore
Have you spotted a continuity nuance in a particular chapter? Want to help index milestones for a favorite character, suggest a new story universe, or share your thoughts on the reading companion? We would love to hear from you.