Slash commands
Type a slash on an empty line and insert headings, callouts, or images without touching the mouse. Notes keep pace with the table.
The prose layer
A campaign wiki your whole table can type in at once.
Block-based pages with slash commands, real-time co-editing, and secrets kept per block. It is the note-taking app for your campaign and the wiki your players read, and the same page can safely be both.
On the free tier, players included.
What is a campaign wiki?
A campaign wiki is the prose layer of a campaign: the lore pages, handouts, session write-ups, and house rules the table actually reads. It is where the world gets written down in sentences, as opposed to the database where it lives as fields.
Inside the editor
Blocks built for the table
Every page is a stack of blocks, and every block earns its keep three ways.
Per-block visibility
Any block can carry its own tier. The tavern page your players read and the paragraph about who owns the tavern's debts can be the same page.
Blocks you can rearrange
Headings, callouts, and images are all blocks you can drag to reorder, so restructuring a lore page is a move, not a rewrite.
The wiki lives beside the campaign knowledge graph: structure in the database, prose in the wiki, one campaign underneath. Each page keeps a table of contents and the entities it mentions in a right-hand rail, so long lore pages stay navigable.
Six hands, one page
Real-time, no locks, no merge
The whole table can be in one page at once, each cursor visible, every keystroke shared live. Nobody waits for a lock, nobody overwrites anybody, and undo behaves even when four people are typing.
It runs on conflict-free replicated documents, the same collaborative-editing approach the big document suites use, and every editing session verifies campaign membership server-side before a connection opens. The recap your player writes while you referee the argument about the plan: that is the wiki working as intended.
Whose pen is it
Three spaces, three owners
Yours
Campaign wiki
The world as you publish it: lore, handouts, house rules. Read-only for players unless you open it up with one toggle.
The table's
Party wiki
Always player-editable. Plans, theories, the loot ledger, recaps in their own words. The campaign's memory, co-authored.
Each player's
My wiki
A private notebook per player, visible only to them and to you. Character journals and suspicions that are not ready to be said out loud.
All three surface in the player portal, each with the right pen in the right hands. The wiki also keeps a Home page that cannot be deleted and a Trash that restores, because collaborative editing without an undo story is a trust exercise nobody asked for.
From scribble to canon
The note-taking app that remembers forward
Session notes in Grimoire are not a dead end. Capture during play with slash commands; afterward, the notes become a session recap, and the recap's key events can be marked canon.
Canon is what the rest of the system runs on. The campaign journal threads it onto the timeline, and under the Revealed world setting the player portal uses it to reveal the NPCs, places, and items the session actually touched. Write the recap, and the world your players can browse catches up to the world they have seen.
That loop is the difference between a note-taking app for D&D and a notes app that happens to contain D&D: your Tuesday-night scribbles end up driving reveals, timelines, and next week's prep.
Recently shipped
-
Grimoire 1.5: The UX Revamp
The wiki gained full-content search with a command-palette Wiki mode, a right rail with page contents and mentioned entities, a safe Home-and-Trash story, and undo/redo that holds up in collaborative sessions.
Optional
Notes that feed a world your AI can query
Grimoire runs fully without a single AI feature. If you already use Claude, ChatGPT, or another MCP-compatible client for prep, the canon your notes produce (the entities, the relationships, the recorded events) is exactly what Grimoire MCP serves your assistant as structured data: it queries your world instead of skimming pasted prose.
You bring your own client, so there is no token markup and no model lock-in. Turn it on when you want it. Ignore it forever if you do not.
See how Grimoire MCP works →FAQ
Campaign wiki questions, answered
What is a campaign wiki?
A campaign wiki is the prose layer of your campaign: lore pages, handouts, session write-ups, and house rules, linked together so the table can browse them. Grimoire's is block-based and collaborative, and it lives beside a typed campaign database, so your lore pages and your NPC records share one home instead of drifting apart across separate apps.
Can my players edit the wiki?
Where you allow it. The party wiki is always editable by everyone at the table, each player has a private wiki only they and the GM can see, and the campaign wiki you author is read-only for players unless you flip the toggle that opens it up. All three use the same real-time editor.
Can I keep secrets on a page my players can read?
Yes. Visibility is per-block, not just per-page. A location page can be player-visible while the paragraph about what sleeps under it is marked GM Secret, and that block simply does not exist in the player portal's copy of the page. One page, two audiences, no duplicate documents.
Is it good for taking session notes?
It is built for exactly that. Slash commands insert blocks without leaving the keyboard, and search plus a command-palette Wiki mode make mid-session lookups fast. When the session ends, the notes become a recap whose key events you can mark canon, which is what drives the timeline and player-portal reveals.
Does it work offline?
No. Grimoire is a hosted, collaborative tool, and the wiki's real-time co-editing depends on a live connection. If offline-first local files are your hard requirement, an Obsidian vault is honestly the better fit; the Obsidian comparison covers that tradeoff.
Hand the table a pen.
The recap they write and the secret you keep can live on the same page.
Free tier, no credit card. The whole table gets the editor.