Skip to content

Every session recapped. Every roll counted.

For GMs and their players: the recap, the wiki and every roll, waiting for your approval by morning.

Free while in pilot. No card, no commitment, and you can take all your data out again.

The Mechanics view for session 6 of a demo campaign: 135 events captured, 52 d20 rolls, a d20 distribution, and a per-character roll and hit point table
From a demo campaign, Emberwatch.
hours of real sessions recorded
127
sessions transcribed
50
campaigns with our pilot GM
6

Pilot figures as of 30 September 2026.

One table, two ways in

The GM runs the session. Every player gets their own side of it.

The rules lookup with Fireball searched: the spell card, related items, and a Voice button for asking out loud

For the GM

The recap, the wiki you approve, encounter maths, and a rules lookup you can ask out loud: say a spell and its card comes up, from 933 SRD entries, without leaving your browser.

What the GM gets
A player's character page, written in their own words, with each section set to private or shared

For your players

Their own character page in their own words, each section private or shared with you. A party chat you cannot read unless they grant you a window, and a quick check-in after each session.

What players get

What game night actually looks like

Three steps, and you keep running the table exactly the way you do now.

  1. Record the session

    Play the way you already do. The Discord bot records your voice channel with each player on their own track; in person, it reads the dice and the numbers your table says out loud; and on D&D Beyond, the Chrome extension catches every roll. Everyone opts in first, and anyone can stop it at any time.

  2. It does the after-work you never get to

    Once you wrap, Six Axes transcribes the night, sorts out who did what, and pulls out both halves of the game: the mechanics (attacks, saves, damage, hit points) and the story (the NPCs, places, factions, and threads that came up). It drafts the recap and files the rest, in the background, while you pack up.

  3. Review, and get your night back

    You skim what it found and approve what goes in, nothing lands without your say. Out comes a player-ready recap, your campaign wiki brought up to date, and a fresh read on how each player is engaging across the six axes, so you know who to aim next session at.

What lands the morning after

The recap your players actually read, and the read on your table. An example from a demo campaign.

The recap page a player reads for session 2 of the demo campaign, written as prose
The recap, as your players read it.

Your table's read

What the GM gets alongside it:

  • Tharn hasn't had a scene to himself in three sessions.
  • The party is sitting on 2,400 gp of unspent loot, most of it Kessa's.

Your table already tells the story. This writes it down.

Nobody has to take notes. The Discord bot hears everyone, the Chrome extension catches every D&D Beyond roll, and nothing reaches the wiki until you approve it.

That Moderate fight left them on a third of their hit points. Your Moderates are landing like Hards.

A campaign wiki that writes itself

Every NPC the party meets, every place they go, every faction and thread and piece of loot gets captured from what was narrated and filed where you can find it. You approve what goes in. By session five you have the campaign bible you were never going to write.

When it is worth sharing, publish it as a page anyone can read, no account needed. You choose exactly what appears, so the setting and the cast can go public while the things your players have not found yet stay yours.

The Codex editor: a faction page with linked NPCs and places, an image, and a reveal setting

See who each player is at the table

Which threads you have left hanging for four sessions. Who has not had a scene in a while. The things you half-notice on the night and have forgotten by the next one.

It also builds a read of how each player engages, across six axes. It is not a score and no axis is the good one. It exists so you can give someone a scene that plays to what they actually enjoy.

  • TacticsTactical play
  • ArcanaOptimization & mastery
  • VoiceNarrative & immersion
  • ExplorationExploration & discovery
  • RapportSocial & cohesion
  • NerveEngagement intensity
Player disposition radar cards across the six axes for six characters in a demo campaign

Build the world, four scales deep

Generate a hex world from a seed, or paint biomes by hand up to 250 by 250, then have it rendered as a finished map. Drop pins, link each to a place or an NPC, and trace where a session actually went.

City, dungeon, and building maps use the same brush-and-render loop. Inside a campaign it ties to your codex, your sessions, and what your players are allowed to see.

The world map editor with a painted continent, mountains, forests and coastlines, and a sidebar of map icons

You're recording your table. We take that seriously.

All of it is spelled out in full on the privacy page.

The players' party chat, with a panel showing the GM sees nothing unless the players grant a time window
Party chat: the GM sees nothing unless the players grant a window.
  • Everyone opts in, every time

    No one is recorded until they have agreed, and anyone at the table can stop it at any point in the session.

  • The audio is on a clock

    Recordings delete themselves 60 days after the session. Only the transcript and the moments you choose to keep stay.

  • Never used to train AI

    The services that transcribe and analyze your sessions do not train their models on your table's data.

  • Encrypted on the way

    Your session data is encrypted in transit between your table and us.

  • Yours to take, or to erase

    Export everything as a single file whenever you want. Delete your account and your personal data and recordings go with it.

  • No mystery vendors

    Every outside service that touches your data is named in the privacy policy, with exactly what it does.

Works with your system

Honestly, because the depth varies by system.

Full toolset

Character builder, monsters or NPCs, encounter maths, system-correct dice.

D&D 5e (2014 and 2024) · Pathfinder 2e · Draw Steel · Daggerheart

Themed table and dice

The right roller and the system's look, character and monster builders still to come.

Call of Cthulhu · Lancer · a generic d10 pool

Planned

On the roadmap, waiting on the publisher's permission before we can ship them.

Cyberpunk RED · Vampire: The Masquerade

The Forge character builder for D&D: identity, class, species, background and spells tabs, with rules and partnered content toggles
The Forge, building a D&D character.

The record, recap, wiki and player insight work the same on every system. System names are referenced for compatibility only; see the Terms for the Lancer, Daggerheart and Draw Steel attributions.

Discord. The bot records your voice channel with each player on their own track.

D&D Beyond and Roll20. Rolls come in through the browser extension, with no separate setup on the night.

Foundry VTT. A module pipes every roll straight in. Set it up

Looking for pilot tables

This is early. It works, it is in use at real tables, and it is not finished. What it needs most is more campaigns and honest feedback, including the unflattering kind. The pilot is invitation-based right now, so tell us about your table and we will get you in.

Six Axes is built by Terry Mickail at Kerf and Code. Questions first? Use the contact page.

The session check-in a player fills in after the game: a 1 to 5 rating and how much of the spotlight they got