Everlore vs Archivist AI · Last checked July 16, 2026
Which turns a session into trusted campaign memory faster?
Archivist AI offers more integrations, input methods, analytics, and public-sharing tools. Everlore concentrates on a faster session-to-canon workflow: capture more of the story, resolve uncertain identities, and let the game master approve exactly what enters the campaign record.
Comparison prepared by Everlore using official product documentation and internal same-session testing. Everlore is not affiliated with Archivist AI.
Choose Archivist AI if…
- You need Discord or Foundry integration now.
- You want cast analytics, handouts, public campaigns, or campaign chat.
- You need 35-plus documented languages or several session-input methods.
Choose Everlore if…
- You want a faster, focused path from session upload to reviewed campaign canon.
- You care about identity decisions, source sessions, revisions, and portable Markdown.
- You prefer a focused post-session workflow over a larger tool suite.
Everlore internal same-session comparison
The strongest Archivist result in our 20-session suite still favored Everlore.
We explored 20 different sessions and selected this session because it produced Archivist's most favorable result relative to Everlore. Both products received the same session material. Even in that case, Everlore completed the core workflow faster and retained more of the session's structured campaign knowledge.
less core processing time
Everlore completed in 3:47 compared with 8:27 for Archivist AI.
as many matched entities
Characters, items, locations, and factions totaled 46 in Everlore and 24 in Archivist.
as many lore records
Everlore produced 14 detailed lore pages; Archivist retained three brief lore points.
| Measured output | Everlore | Archivist AI | What we observed |
|---|---|---|---|
| Core processing | 3 min 47 sec | 8 min 27 sec | Everlore completed core processing in about 55% less time. |
| Character entities | 12 | 8 | Everlore also retained historical figures mentioned through newly discovered lore. |
| Items | 8 | 5 | The evaluator found that Archivist omitted the session's most consequential newly acquired artifact. |
| Locations | 21 | 7 | Everlore retained distant lands, sub-locations, and a newly revealed ancient kingdom that were absent from the Archivist record. |
| Factions | 5 | 4 | One Archivist faction was a false positive created from the generic term “Crossbowman,” increasing cleanup. |
| Events and consequences | 18 key events plus 8 loot/consequence details | 13 Moments | Archivist Moments were one- or two-sentence snippets; Everlore separated event chronology from loot and consequences. |
| Summary length | 4,350 characters | 4,105 characters | The summaries were similar in raw length; character count alone is not treated as a quality score. |
| Quests | 3 detailed quests in the core pass | 1 quest after a separate processing step | Archivist's quest step added 1 min 8 sec to 3 min 56 sec for this workflow and must be repeated per session. |
| Lore records | 14 detailed lore pages | 3 brief lore points | Everlore created structured records for battles, regional dragons, a cult, an undead uprising, and other discoveries. |
This was an Everlore-conducted internal comparison, not an independent laboratory test. The session shown was selected as Archivist's strongest relative result from an exploratory 20-session suite. Results can vary with session length, audio quality, campaign complexity, settings, and product changes. Entity count, record length, and descriptive detail measure coverage—not factual accuracy. Material omissions and the faction false positive reflect the evaluator's transcript-based review and have not been independently audited.
At a glance
Everlore and Archivist AI compared
| Decision factor | Everlore | Archivist AI | What it means for you |
|---|---|---|---|
| Core approach | Focused session-to-canon workflow with a reviewable campaign wiki. | Broad campaign suite spanning capture, recaps, compendium, analytics, sharing, chat, and integrations. | Choose based on focused review versus feature breadth. |
| Session input | Single mixed audio, separate player tracks, or an existing transcript. | Discord, audio, aligned multitrack, transcripts, raw notes, Google Docs, and play-by-post. | Archivist currently supports more ways to bring a session in. |
| Campaign records | Characters, places, items, factions, lore, quests, events, mysteries, and sessions. | Characters, items, locations, factions, timeline beats, moments, quests, and journals. | Everlore emphasizes a broad story taxonomy; Archivist exposes more separate feature surfaces. |
| Review workflow | The AI prepares changes for the game master to compare, accept, separate, or reject before wiki canon changes. | Session Review covers timeline, summaries, entities, and moments; quests are compiled and approved separately. | Everlore is designed around a more unified editorial decision. |
| Names and duplicates | Candidate comparison, aliases, match confidence, merge, create-new, and never-merge decisions. | Merge, split, reclassify, Find & Replace, and Compendium Cleanup workflows. | Both recognize fantasy-name cleanup as a core problem; the practical difference is correction effort. |
| Source evidence | Stores source sessions and evidence-backed discoveries for review and lore provenance. | Provides transcripts, session context, timeline beats, entity links, and some session provenance. | Everlore's intended advantage is placing the source beside the proposed canon change. |
| Undo and recovery | Wiki revision restoration, merge safety, and protected manual content are part of the beta contract. | Some quest merge rollback is documented; entity removal during Session Review is documented as irreversible. | Everlore prioritizes reversible canon operations. |
| Integrations | Obsidian-compatible Markdown export; a deliberately narrower private-beta surface. | Discord, Foundry VTT, Obsidian, a developer API, and an MCP server. | Archivist is the stronger choice when integrations are the deciding factor. |
| Analytics and sharing | Not a private-beta priority. | Cast Analysis, sentiment, talk share, Data Studio, handouts, public campaigns, and GM profiles. | Archivist is stronger for groups seeking analytics and public presentation tools. |
| Export and ownership | Obsidian-ready Markdown and YAML built as the campaign's portable canonical format. | Campaign ZIP export in Obsidian Vault, Markdown, or HTML formats. | Both products support taking campaign material elsewhere. |
| Audio privacy | Uploaded audio is deleted from Everlore storage after a transcript is created successfully. | Archivist says audio is deleted after transcription and campaign content is not used to train AI models. | Audio deletion is a shared strength, not an exclusive Everlore claim. |
| Pricing and access | Invite-only private beta; public paid pricing has not been announced. | $10–$60 per month, with usage capacity increasing by tier; current pricing checked July 16, 2026. | Archivist can be purchased now; Everlore is still admitting beta cohorts. |
The central difference
Archivist optimizes for breadth. Everlore optimizes for fast, reviewable editorial control.
Archivist's documented workflow can produce a recap, three-level timeline, Compendium entries, Moments, quests, handouts, cast analysis, relationship views, journals, and a campaign chatbot. That is meaningful breadth. It also means a campaign can involve separate timeline, summary, entity, moment, quest, cleanup, and analytics workflows.
Everlore's workflow is narrower by design: analyze characters, world details, and story developments; combine them into reviewable campaign changes; concentrate attention on uncertain identities or conflicts; and keep the resulting wiki portable. The goal is not to win a feature-count contest. It is to reach trusted canon faster without flattening the session into a short summary.
Already using Archivist AI?
Archivist offers campaign-wide exports in Obsidian, Markdown, and HTML. Everlore is preparing a private-beta migration pilot around user-owned exports so existing campaigns do not have to be rebuilt by hand.
See the planned import workflowSources and methodology
Archivist product facts were checked against its official features, documentation, integrations, pricing, and developer platform pages. Everlore descriptions reflect the current private-beta product contract. The measured section reports one same-session output selected as Archivist's strongest relative result from an exploratory 20-session suite. Timing was recorded directly; entity and content counts were manually reviewed. The comparison was conducted by Everlore and was not independently audited. Raw coverage and detail are not presented as a standalone factual-accuracy score.
Private beta
Want campaign memory built around your approval?
Join the Everlore waitlist and tell us whether you are bringing an existing campaign.
Join the waitlist