Codex
Campaign command center

Host the whole campaign in one place.

Codex gives your table one home for scheduling, lore, maps, membership, and session conversation, so the campaign feels organized before session zero and stays that way afterward.

Browse public campaigns
  • Schedule sessions
  • Run polls
  • Build a wiki
  • Link maps
  • Invite players

Session 12 scheduling

Active poll

6 slots · 4/5 voted

Leading slot: Thu, Mar 21 · 7:30 PM

Northern Reach map

7 hotspots

Public map

Linked to locations, factions, and travel notes

Member flow

Access

2 pending requests

Invites, approvals, and campaign identity in one place

One campaign shell. Sessions, polls, forum, wiki, maps, files, announcements, and member access all point back to the same table.

What Codex already does

Built for the campaign work that usually gets split across tools.

Run the table

Keep table logistics visible, current, and easy for every player to follow.

  • Scheduling polls

    Share candidate dates, collect availability, and surface the leading slot.

  • Sessions and RSVPs

    Track who is confirmed, tentative, or still pending for each session.

  • Forum and play-by-post

    Keep campaign discussion, recaps, and async scenes tied to the same table.

Product surfaces

A landing page built from the product you already have.

Session command

Plan the next night without chasing the group chat

Live logistics

Polls, RSVPs, deadlines, and session pages stay attached to the campaign instead of vanishing in chat history.

Session 16 scheduling4/5 voted
Leading slot: Thu, Mar 21 · 7:30 PM
4 confirmed1 tentative
  • Active poll with a visible leading slot
  • RSVP counts for confirmed, tentative, and pending players

Launch the campaign hub

Get the campaign organized before the next session starts drifting.

Create the campaign, invite the group, and give every note, schedule, and map a place to live.

Browse public campaigns

Build a living world

Turn campaign memory into a codex players can actually use between sessions.

  • Typed wiki pages

    Organize NPCs, PCs, locations, factions, items, and lore in one searchable structure.

  • Journal and house rules

    Publish session recaps and table rules without splitting them into separate tools.

  • Maps with hotspots

    Link clickable map regions directly into the wiki so geography stays connected to lore.

Manage the campaign

Control access, present the campaign well, and keep shared resources under one roof.

  • Public or private visibility

    Let players browse public campaigns and request access, or keep discovery locked down.

  • Invites and member controls

    Approve requests, send invites, and moderate membership without leaving the app.

  • Campaign presentation

    Post announcements, customize identity and theme, and keep files ready for the group.

  • Session comments anchored to the calendar entry

    • World codex

    Keep lore, recaps, and house rules in one readable structure

    Linked knowledge

    The wiki, journal, and rules index live together, with internal links that turn scattered notes into campaign memory.

    NPCsLocationsJournalHouse Rules

    New journal entry: Ashfall Market aftermath

    Internal links connect people, places, and session notes.

    • NPC, PC, location, faction, item, and lore pages
    • Journal entries published alongside the rest of the wiki
    • House rules that players can find without asking again

    Map + members

    Share what players need while keeping GM controls intact

    GM controls

    Maps, requests, invites, approvals, and visibility settings work together so access stays intentional.

    Northern ReachPublic map

    7 hotspots linked into the wiki. 2 pending requests. 3 files ready for players.

    Keep private pages and GM-only context behind membership.

    • Public and private maps with wiki-linked hotspots
    • Browse and request-to-join flows for public campaigns
    • Member approvals, announcements, files, and campaign identity

    Why host in Codex

    Keep the campaign coherent from the first invite to the next recap.

    Stop scattering session logistics, lore, and access decisions across separate docs and chats.

    Run scheduling, worldbuilding, and player coordination inside one campaign shell.

    Share only what players should see while keeping GM-only context protected.