The command palette
Ctrl+K or Cmd+K anywhere in the app jumps to any entity, page, graph, or setting by name, with a Wiki mode that searches page contents. The fastest lookup at the table is the one you never leave the keyboard for.
How it fits together
Not six tools. One world, seen six ways.
The record you fill in draws the graph. The graph explains the page you write. The page reveals itself to your players. The recap you write afterward updates all of it, and the home tells you where you left off. Here is a campaign, start to finish, the way it actually runs.
Everything below ships today. Nothing here is a roadmap.
01 · The home
Start where you left off, not at a blank page.
The campaign home is a briefing, not a dashboard of counts. It opens on the last session's recap, the threads still hanging with how long they have hung, the arcs in motion, who was on stage last time, and your party. Everything on it is generated from the campaign, so it is never out of date and never needs tending.
Which means prep starts from what is open. The favor promised in session 3 is still raising its hand in session 8, on the first screen you see.
02 · The database
Fill in a record, not a template.
Fourteen typed categories ship with the fields a GM actually needs: NPCs with motivations and faction ties, locations with a parent, factions with allies and rivals, quests with a status, items that change hands, sessions with key events, and eight more. Pick a genre and the nouns reshape; the structure underneath does not.
Which means every field you fill in is something the rest of the app can use. Name Queen Mira as the leader here and the political web draws the line for you, her page lists the house, and both show up when your players are allowed to see them.
See the campaign database →03 · The graphs
Record the relationship once. The graph draws itself.
The political web of who answers to whom, the timeline of what happened when, and the geography of what sits inside what are projections of the records you just filled in. Nothing to lay out, nothing to maintain. Custom graphs let you assemble a view by hand when you want one, and World Foundations holds the bedrock canon underneath: pantheons, the laws of magic, the bones of the setting.
Which means "who would move against House Vale" is a view you open, not a memory test you fail at midnight.
Explore the knowledge graph →04 · The wiki
Write it in sentences. The sentences know the records.
Lore, handouts, house rules, and session notes live in a block editor the whole table can type in at once. Mention any entity with @ and the page links to its record, which lists every page that mentions it back. Link pages with [[, drop a table with /table, and mark any single block GM Secret on a page your players can otherwise read.
Which means the prose and the records never disagree. Rename the abbess in one place and every page that mentions her follows.
Tour the campaign wiki →05 · The player portal
Hand the table the world they have earned.
Every record and every wiki block carries a visibility tier, and the filter runs server-side, so a GM Secret never leaves the building. Under the Revealed world setting the portal fills in as you play: when a recap mentions an NPC, a place, or an item, it appears in your players' codex. They get the shared party wiki to write in and a private wiki each. Players are free, always, on every plan.
Which means reveals are a game mechanic you run from one toggle, and the same page shows each reader exactly their slice.
See the player portal →06 · The recap
Five minutes after the session, and the loop closes.
Write what happened. Mark the key events canon. That one recap adds the session to the timeline, reveals the NPCs and places it touched to your players, ages every open thread by one more session, and becomes the "where you left off" on next week's home. Open threads are typed and dated, so a promise made in session 3 keeps raising its hand until the table pays it off.
Which means the campaign remembers forward. Next week's first screen already knows what happened tonight.
Open the campaign journal →Optional · your AI client
Already use Claude or ChatGPT? It reads the same world.
Grimoire runs fully without a single AI feature. When you want it, Grimoire MCP connects your campaign to Claude, ChatGPT, or any MCP-compatible client with one sign-in: the same records, graphs, and wiki pages, read live under the same visibility rules, and written back with the same chips. You bring your own client, so there is no token markup and no model lock-in.
Which means your assistant stops inventing your world and starts citing it. Everything above stays true whether or not you ever turn this on.
See how Grimoire MCP works →Also in the book
The small print, which is also good news.
The genre engine
Fantasy, Sci-Fi, Horror, Post-Apocalyptic, Modern, Superhero, or Historical, with facets on top. Category names, field vocabularies, and tone reshape to fit; the structure underneath stays the same.
Try the genre picker →Your data exports
Full campaign export in standard formats, on every plan, any time. Wiki pages leave as markdown, tables as markdown grids. If a subscription lapses your world stays readable.
Custom fields on Pro
The fourteen schemas cover most tables. When yours needs a Blood Type on every NPC, Pro adds custom fields to any category without breaking the typed structure.
Players are free
Every player joins on a free account with no seat limit, on every plan. One login runs your own worlds and plays in someone else's.
A free tier that is the product
One full campaign, every feature on this page, no credit card. Upgrade when the campaign outgrows it, not before.
New in 1.5.1: page links, @ mentions, tables, and a wiki your AI client can search. Read the changelog →
One world. Every lens.
Session zero is free. Every step above is live today, and the demo is a full campaign you can break.
Want the inventory instead of the workflow? See what a campaign manager should do, or compare Grimoire to the field.