For GMs whose wiki nobody opens

A living campaign knowledge graph your whole party actually uses.

You built a beautiful wiki and your players never read a page of it. This is different: a shared map of your world where people, places, factions, items, and threads are linked, your secrets stay GM-only, and the same lore doubles as the memory your familiar reads.

Start free Explore the graph

A sample world, linked. Tap a thread to follow it.

Tap any thread to follow it
The Lore section of The Lantern Company, bursting into the living graph. Every page, quest, faction, and clue becomes a node, and every edge is a connection you can follow in the app.

Everything, connected

A relationship map, not a stack of pages.

A wiki keeps pages. Your campaign keeps relationships. Every entity is a node, every connection is an edge you can follow, so the thread you tug always leads to the next thing that matters at your table.

People

Every NPC and PC your table has met, with the version of the truth each one knows.

Places

Where things happened, what is watched, and which door your party plans to leave through.

Factions

Who is leaning on whom, which deal is still owed, and why a name still opens doors.

Items and threads

The objects that carry the plot and the questions still hanging over your table.

Shared, but not all of it

Share the world. Keep the twist.

Your players browse what they have actually earned in play. The reveal you are saving stays yours alone, GM-only, until you decide the table has earned it. Party roles draw the line, so you stop being the only person who remembers the world without spoiling the story you are still telling.

From The Lantern Company

What the Cinder Guild really wants GM only
Mother Vane holds Pell's debt-marker Party can see
The Emberseal is failing GM only

An example of role-gated visibility from The Lantern Company. You choose which entities the party sees and which stay behind the screen.

Lore your familiar can read

This is the memory your familiar draws on.

A wiki can only be read by a person. Your graph can be read by your familiar. Ask who is behind a threat and it answers from the factions and clues your table built, then recalls, connects, and updates them with your approval. That is the real difference from a wiki: lore that just sits there versus lore that can be acted on.

Meet your familiar

Asked of The Lantern Company

Who holds Pell's debt, and why should the party worry?

Your familiar answers

Mother Vane holds the debt-marker for the Cinder Guild, the black market the Crown forbids. She runs it from the Cinderhall back room in the Ashmarket, and her enforcer Bask Greel is the thread to pull next.

The Cinder Guild Pell's debt-marker Mother Vane

How the graph fills

The graph builds itself from what you already wrote.

You do not have to build the graph node by node. Bring in the notes you already keep, and ScryRPG reads them, pulls out the people, places, factions, and threads, and links them the way they actually connect. You review what it found before any of it lands, then keep adding by hand whenever you want.

See how import works
The ScryRPG Lore section for The Lantern Company: a header counting pages, quests, factions, events, and links, above a quest board with cards sorted into Available, Active, Completed, Failed, and Abandoned columns.
The Lore section from The Lantern Company. The header tallies the pages, factions, events, and links in the graph; below it the quest board sorts every thread into Available, Active, Completed, Failed, and Abandoned.

Lore FAQ

Quick answers.

How is this different from World Anvil or Kanka?

A traditional campaign wiki gives you pages and links you maintain by hand, then nobody at the table opens them. ScryRPG gives you a living relationship graph: people, places, factions, items, and threads are connected entities, GM-only secrets sit beside party-shared truth, and the same lore is the memory your familiar reads when you ask it a question. Your worldbuilding does not just sit there to be read; it can be acted on.

Can my players see the lore, or just me?

Both, by design. Party roles decide who sees what. Players get the shared world they have actually earned in play, while GM-only secrets stay hidden until you choose to reveal them. You can keep what a faction really wants to yourself and still let the whole table browse everything they know.

Does the familiar actually read my lore?

Yes. Your lore is the memory your familiar draws on. Ask who is behind a threat and it answers from the factions and clues your table built, not generic fantasy. That is the difference from a wiki only a person can open: this knowledge graph is something your familiar can read and act on.

How does the lore get in there in the first place?

Import it. Drop in your session notes and ScryRPG pulls out the people, places, factions, and threads and links them for you. You review what it found before any of it lands, and you can build entities by hand whenever you prefer.

More questions about getting started, your data, and how it all fits? Read the full FAQ, or step back to the ScryRPG overview to see how the graph connects to the rest of your table.

Map your world.

Start free. Paste your notes and watch your people, places, factions, and threads become a graph your whole table will actually use, and one your familiar can read.

Start free