Why We Built Lorebase
After years of writing short stories, 3D modeling characters, and designing environments, we hit a wall. The technical art debt was crushing us. We had stories, drafts, notes, storyboards, mood boards, and production schedules scattered across a dozen different applications that refused to talk to each other.
We tried the off-the-shelf tools. We tried forcing wikis to act like databases and word processors to act like production managers. None of it worked for the scale of what we were trying to do.
So, over the past several years, we built Lorebase to solve our own in-house problems. We needed a single, local-first production pipeline to manage the chaos.
We live in a moment where spinning up a flashy demo over a weekend is easier than ever. Modern frameworks and APIs let you mock up slick interfaces that look great in a screenshot. But we knew from the start that a weekend prototype wouldn't survive the weight of an actual production pipeline.
Having built web applications professionally since 2004, we knew exactly what kind of foundational engineering this would take. Two decades of software development teaches you the hard difference between an app that holds together for a demo and load-bearing architecture built to last.
We began conceptualizing and building Lorebase long before the current AI boom took over the industry. It wasn't conceived to ride a hype train, and it definitely wasn't built to be a thin cloud wrapper. It was forged out of sheer necessity. We needed a robust, offline-first engine that respected our digital sovereignty and could actually handle the intricate, messy reality of our own worldbuilding and game design processes.
Building something resilient requires patience, deep technical planning, and a refusal to compromise on data ownership. Lorebase is the culmination of a career spent learning exactly how things break, and how to build them so they don't.
It was created in-house to serve our own purpose and help us survive our own projects. But maybe you and your team will find it useful, too.



