Ownership beats policy
A page without a named owner is a page nobody will fix. So every page gets one, and reassigning is a single click, not a migration project.
About Lorebrary
Meet the Librarians
We make a team wiki for one stubborn reason: the answer you find should still be the right one. Lorebrary connects your docs, threads and tribal know-how, then keeps watch over all of it.
The problem
Wikis Don’t Fail Loudly. They Drift.
Nobody sets out to build a bad wiki. The first month it’s lovely: a handbook, a few runbooks, a refund policy somebody actually wrote down. Then the policy changes in a chat thread, the runbook gets a quiet edit in a shared drive, and the page that everyone still links to keeps cheerfully saying the old thing.
The damage is slow and invisible. A new hire follows the stale checklist. A support macro quotes last year’s window. Someone asks in the channel, three people answer three ways, and the wiki loses another point of trust it will never earn back.
Search tools made it worse in one respect: they find everything with equal confidence. A signed-off policy and a rambling draft from two years ago look like neighbours in the results.
So we built the library to notice its own age, and to tell a human before a customer finds out.
What we hold to
Four House Rules, Shelved in the Product
These aren’t slogans on a wall. Each one decides something specific about how Lorebrary behaves.
Age should be visible
Freshness isn’t buried in a settings screen. It sits in the page header, in search results and in a table that sorts the oldest first.
Trust is earned by a person
A verified badge means a named human reviewed the page on a named date. Software can suggest; only people can vouch.
Knowledge lives where it’s born
Answers start in threads, files and tools. Lorebrary reads from them instead of asking your team to move house first.
How it’s built & supported
A Small Product, Kept Carefully
We’d rather ship fewer things that work than a long list that half-works. That shows up in how the product is made and how we look after it.
- One paymentPlans are bought once per shelf. There’s no seat meter ticking in the background while your library sits still.
- Search firstEvery feature is judged against one test: does it get someone to the right page faster?
- Real repliesSupport is an email to hi@lorebrarylabs.com, answered by the people who work on the product.
- Changes on recordPage history, comments and verification stamps are kept so you can see who vouched for what, and when.
Where it’s going
The Next Few Chapters
Direction, not promises with dates attached. The common thread is a library that does more of its own upkeep.
Sharper freshness
Review rhythms per section, escalation when an owner stays quiet, and a freshness table that makes the oldest pages impossible to miss.
More sources, one search
Deeper connections to the tools teams already write in, with verified pages always ranked above loose threads.
Fewer orphans
Better prompts for linking related pages, so the knowledge map fills in as people write rather than after the fact.
Plans stay one payment each as the product grows. See what each shelf includes today.
Take a shelf
Start Filing What Everyone Keeps Asking
Three shelves, one payment each. Choose the one that fits your library and give your answers an owner.
See plans