Your session space (Live theaters)
Catharsis, First Theater, and Victory Theater are live session spaces built on the same engine. They hold maps, tokens, cues, drawings, and other things you put on the table.
Manage rosters, scenes, and cues from a production workspace. Write and revisit a persistent campaign. Bring a prepared session to the table without rebuilding it from scratch.

Victory is built for stories that have a world behind them and a performance in front of them. The live theaters power the VTT, while Storyboards, writing tools, the Library, and production spaces support everything that happens before and after a session. It is designed for GMs and organized production teams who want a persistent world they can revisit.
Victory is built for organized groups running persistent campaigns and audience-facing performances - not casual game-night groups who just need a map and dice.
Build the game into the table. Victory has a system-agnostic foundation for putting a particular game's rules, content, and play flow into the VTT, so other people can open it and play that game instead of rebuilding it around a generic tabletop.


The Audience sees the performance, the Cast sees their character, the Director sees everything - from one running stage.
This is a four-minute screen recording from the current alpha, showing the map surface, empty theater, chat tray, Cartography tools, grid configuration, and a story/character panel. It is a product capture, not a polished promotional film.
The recording has no spoken narration. Visual captions are available in the player.
Catharsis, First Theater, and Victory Theater are live session spaces built on the same engine. They hold maps, tokens, cues, drawings, and other things you put on the table.
A planning board for arranging scenes as cards, columns, rows, and bands before they go on the live table.
eWrite is Victory’s Markdown-based editor for manuscripts, rulesets, and skill lists. Your manuscript workspace (Writer’s Room) is where this work is written and revised.
The Library holds reusable scenes and reference material. Asset tools and storage (Workshop and Warehouse) handle images, metadata, and permissions.
Discord identity, chat, and audio surfaces can connect an existing group setup to the stage, where configured.
Join the Victory Discord ↗Four levels, from your installation down to the session you are running right now. Victory’s own name for each level is in brackets: your campaign (Show) persists over time; a session (Showing) is one night of play; the live session (Showtime) is that session while it is running.
Everything on one install of Victory: your workspaces, your people, and the person who runs it.
Title, roster, scenes, storyboards, and the rules and content for your game.
One scheduled session of your campaign, with or without an audience.
The table is live: players are in, and an optional audience view runs alongside your GM workspace.
Author manuscripts and rulesets in eWrite so your content is ready for the stage without re-creating it each session.
Arrange scenes and cues on the scene planner (Storyboards) so your prep lives in the world, not in a folder.
Manage rosters, schedules, and cues in your session-prep workspace (the Producer's Office) so you are not re-prepping from scratch each week.
Bring the prepared material to the live table and run the session with your players, your helpers, and an audience if you have one.
The homepage shows the stage transition first. The full interface gallery covers the current alpha’s production board, library, authoring, cartography, identity, asset, and live-session surfaces.
Open the interface galleryVictory comes preloaded with Socio, a quickstart, campaign setting, and initial plot that provides the first playable content for the VTT. Socio is content running inside Victory, not the name of the software itself; the platform is intended to support other games, settings, and authored play flows as well.
That is the current number. We are not presenting a larger user count or invented testimonials.

The project starts from a practical goal: let game builders put rules, content, and play flow into the VTT so other people can open the game and play it without rebuilding it around generic tools.
Read why Victory was built ↗What changed recently (changelog)Join the Victory Discord ↗Victory on GitHub ↗Grant A. Murray on LinkedIn ↗Static HTML/CSS/JavaScript surfaces, Vue for newer interaction-heavy venues, and PixiJS as the renderer for stage composition.
Go services with domain packages for access, participation, Show Runs, Scenes, Storyboards, eWrite, and related concerns.
Postgres persistence for accounts, productions, rosters, Scenes, permissions, and authored content; WebSockets for live session synchronization.
Discord identity, chat, and audio surfaces; Caddy serves the frontend and routes application traffic. See the full technical brief for the current system shape.
Victory is free to use, including commercial games within the current published terms, with full access to the software rather than a reduced feature tier. Paid commercial terms begin after $2,600 in Victory-Related Revenue during a License Year; published annual tiers above that are $49, $249, and $999, with custom terms above $250,000. Read the current licensing terms.
Show, Showing, and Showtime map to concepts you already know: your campaign, a session, and the live moment. See the 2-minute glossary above.
Victory is in public draft, so it may change as the product develops. eWrite manuscripts and Rulesets are Markdown-based source; keep copies of authored source outside the alpha while scene and stage export paths are still in development.
Victory is pre-launch. Two published reviews of Socio are available, and we are collecting more early feedback and beta-tester stories as people use the product for longer.
The Windows build is available now. Use the Google Form for feedback, questions, live-alpha access, and examples of the game you want to build into the VTT. The Discord is for alpha access, feedback, and play-test groups.