Choose the workflow, not the longest feature list
The real comparison starts after the recap is written.
Most tools can summarize a session. The difference that matters is what happens next: how names get corrected, how discoveries become durable lore, how uncertain claims are handled, and whether the campaign is still useful fifty sessions later.
Everlore fits when...
- Your campaign has history worth carrying forward.
- You want AI assistance without automatic canon.
- You care where a fact came from and how a page changed.
A broader alternative may fit when...
- Your priority is a wide suite of integrations or table tools.
- A standalone recap is enough for the way you prepare.
- You prefer feature breadth over one focused editorial workflow.
At a glance
Three ways to keep a campaign remembered
This is a category-level guide, not a scorecard for a named competitor. Individual tools change quickly, so verify the capabilities that matter to your table before choosing one.
| Decision | Everlore | Closest campaign-memory alternative | Manual notes or wiki |
|---|---|---|---|
| What you get | A session chronicle plus proposed updates to a connected campaign wiki | A recap and a collection of generated campaign records | Exactly the documents you make by hand |
| Where your audio goes | Cloud transcription with the file deleted afterward, or local transcription that never uploads it | Usually cloud only, with retention set by the service | Wherever you put it |
| Canon control | One reviewable change set before the wiki changes | Varies by product and feature | Complete control, with every update done manually |
| Long-term continuity | Aliases, revisions, source sessions, relationships, and unresolved threads stay connected | Usually organized around sessions or separate feature surfaces | Depends on the system and upkeep you maintain |
| Many campaigns | Campaign views can belong to one shared World | Usually handled campaign by campaign | Flexible, but repeated lore must be reconciled by hand |
| Portability | Obsidian-ready Markdown with useful links and structure | Export support depends on the service | Your files are already yours |
Review before truth
Everlore prepares a change set. You approve, reject, separate, or merge before the campaign wiki moves.
Keep the evidence
Source sessions, page history, aliases, and review decisions make campaign memory inspectable instead of mysterious.
Leave with useful files
Export an Obsidian-ready Markdown vault so years of approved lore are not trapped inside one service.
An honest note about the closed beta
Everlore is narrower and earlier than the established alternatives. Integrations and public sharing are not what this beta is about. The whole product is one dependable path from session evidence to GM-reviewed, portable campaign memory. If you need a broad suite of table tools today, another product will serve you better.
Closed beta for experienced DMs
Bring the campaign that already has history.
Tell us what you run, how you remember it today, and what Everlore should help you preserve.
Request a beta invitation