Stop scrolling a 200-page doc while your table waits.
Scry sits in your Discord call and records the session. Afterwards it builds your campaign wiki out of what was said, and every entry shows the line it came from. You run the game, it keeps the notes.
No card required · Free tier · Import your notes in minutes
THE PROBLEM
Half your campaign is in a doc. The rest is in your head.
Your campaign lives in three places and none of them agree.
- The doc, where the innkeeper has two spellings and one of them is crossed out.
- The vault you set up in January, with 47 session files and two called Untitled.
- Your head, which is also holding a job, a family and the rules for grappling.
So when someone asks what happened three sessions back, you fluff it, and they can tell. It happens every week, and each time your players learn that the world only exists while you can find the page.
I've run the same group for five years. I built Scry because I was tired of this.
It records the session and turns what was said into a wiki that keeps itself in order, every NPC and place linked back to the moment it came up. You don't write any of it. You play, and by next week it's there.
WHAT CHANGES ON A SUNDAY
Four things that used to stop the game.
A player tries to grapple and the book comes out.
Type it into Ask Scry and the answer comes back with the page it's from, out of the sourcebook you imported. Nobody reaches for the book, and you're not writing any of this down either.
Writing notes when you're meant to be listening.
Scry sits in the voice channel with the rest of the table, and the transcript comes back with your players' names on it instead of Speaker 1 and Speaker 2. You put the pen down and listen. That's what they came for.
Writing the recap on a Tuesday night.
By the time you've closed Discord, the session is on its page, and anything new it found is waiting for you to approve. Who was there, what they found out, the innkeeper's name spelt one way, each of them linked so you can follow it back. Walk into next week knowing what happened last week.
Two hours of prep on a Saturday.
Ask for a prep sheet and you get one page, built from your wiki, your open quests, your sourcebook and your players' backstories. Prep is ten minutes and there's something on it for everyone. It remembers the innkeeper's brother, who a player wrote into his backstory in session four and nobody has mentioned since.
WHERE THE LINE IS
It won't write your campaign.
That prep sheet is as close as Scry gets to writing anything, and it stops there on purpose. I've watched a good campaign go through an AI and come out smoother and worse. The prose got cleaner, the life went out of it, and the players noticed before the DM did.
So Scry only remembers. Everything it proposes shows you the line from the session it came from, and nothing goes into your wiki until you've read that line and hit approve.
That's built into the code. There's no setting for it, and I'm not adding one.
THE PART NOBODY ELSE DOES
Your wiki, and theirs.
That source line is what makes two wikis possible. Yours has everything, including the part the party doesn't know yet.
Your players get their own, built from the recording alone. Your notes never touch it, so if the table hasn't found something out yet, there is no page for it to leak from.
You send them a link once. They read the recap on the bus, look up the name they forgot, and turn up on Sunday knowing where they were. You never write a recap post again.
YOUR TABLE
Your players see exactly what's kept.
Recording starts when you start it and stops when you stop it.
- Audio is deleted within 72 hours. That's a rule in the storage layer, so it runs whether anyone remembers or not.
- Scry says so in the channel when a session starts.
- Every player gets a link to their own wiki, so they can read what's been kept.
- Anyone who'd rather sit out of the recording says so once, and it sticks.
You signed up for this. Your players didn't, so it has to work for them too.
The player who went quiet.
The innkeeper's name was the cheap mistake. The expensive one is the player who handed you three pages of backstory, with the innkeeper's brother in it, then watched everyone else's story get picked up while theirs sat in a doc you meant to reread.
They didn't complain. They went a bit quiet, and by session twelve they were the one checking their phone.
When the prep sheet remembers the brother, he walks into the scene in session fourteen and the quiet player sits forward. You go back to running the game, which is the part you were good at in the first place.
No card required
Built at my own table.
Every scene on this page is a real problem from my Sunday game.
I built Scry so I'd stop scrolling for the innkeeper's name, and I kept building it because of a player whose backstory I let die.
It's rough in places and I'm building it in the open. If you take your campaign seriously, come break it and tell me what's missing. The email in the FAQ goes to me.
Peter
PRICING
Priced for a weekly game.
Save 2 months with annual billing
Pro
Most popular$150/year
About $2.90 per weekly game
- Unlimited campaigns
- PDF import
- 6 sessions a month, enough for a weekly game
- Unlimited Ask Scry
- Player wiki for your whole table, no per-seat cost
Max
$240/year
About $4.60 per weekly game
- Everything in Pro
- 12 sessions a month, for DMs running more than one table
- Commercial licence
Pause any time. Your campaign stays readable as a wiki until you come back.
Export to markdown whenever you want.
Questions I get asked
What happens to the recordings?
Audio is deleted within 72 hours, every time. It's a storage rule that runs on its own, so it doesn't depend on anyone remembering. The transcript and the wiki stay, the audio doesn't.
Do my players need accounts?
No. You send them a link and they read their wiki. No signup, no password, no app.
What if one of my players wants to be left out?
They say so once and their audio is left out of the recording from then on. It's per person and it sticks, so nobody has to say it again every week. The session still records for everyone else.
Is my campaign used to train AI models?
No. It isn't training data and it never gets pooled with anyone else's.
Does it work for in-person games?
Not yet. Scry records Discord voice. If you play at a physical table, this isn't for you right now.
Does it work with systems other than D&D 5e?
D&D 5e and Pathfinder today, with more on the way. Recording, transcription and the wiki don't much care what you play.
What if we stop playing for a while?
Pause any time. Your campaign turns into a read-only wiki and stays readable. Everything you built is still there when you come back, and nothing gets deleted because your group skipped three months.
Can I get my stuff out?
Any time. Export gives you a folder of markdown files with the wiki links intact, which opens straight in Obsidian or anything else that reads markdown. Your campaign is yours and you can walk out with it.
Who do I talk to when it breaks?
Me. I'm one person building it in the open. Email peter@getscrying.com and I'm the one who reads it.
Never lose the thread.
Run Sunday with Scry in the channel. By Monday there's a session page waiting for you.
No card required