Technical brief / build 0.1

Victory software architecture

Victory is a browser-based virtual tabletop with a persistent content model, a live-session runtime, and authoring surfaces for building game-specific rules and material into the application.

Status: public alphaUpdated: September 23, 2026Scope: current implementation and deployment model

What is the current system boundary?

The current system boundary is a static public website plus a separately deployed live application. The website is a Cloudflare Pages deployment. The live Victory application is a runtime composed of browser clients, Go services, PostgreSQL persistence, WebSocket session state, and a stage renderer.

The system separates durable production data from a live Showing. A Show is the persistent production; a Showing is an instance of that production; Showtime is the active live state.

Client UIHTML/CSS/JavaScript with Vue for interaction-heavy surfaces
RendererPixiJS stage composition
ServicesGo application and domain packages
PersistencePostgreSQL
RealtimeWebSocket session synchronization
Public siteStatic HTML on Cloudflare Pages
ComponentImplementationResponsibilityStatus
Shared frontend shellBrowser clientNavigation, identity, access boundaries, and shared application surfaces.Active
Stage runtimePixiJS and client stateMaps, tokens, drawings, cues, and other stage objects during live use.Active alpha
Domain servicesGoShow, Showing, roster, participation, content, and permission operations.Active alpha
Live synchronizationWebSocketsPropagation of session state between connected clients.Active alpha
Discord surfacesDiscord bridge and mapped voice statePresence, chat, and audio-adjacent integrations where configured.Partial / environment-dependent

How does a live session move through the model?

A live session moves from persistent Show content to a scheduled Showing and then to active Showtime state. The browser renders the state appropriate to the participant’s role while the application services remain responsible for persistence and authorization.

Location

Installation boundary

Top-level container for venues, operators, and the installation’s shared context.

Show

Persistent production

Campaign or game instance containing title, roster, scenes, rules, and authored material.

Showing

Session instance

A scheduled or audience-facing performance of a Show.

Showtime

Live state

The active state of a Showing while clients are connected and the stage is running.

AudienceReads the audience-facing session state.
CastParticipates through character and player surfaces.
Director / Producer / GMRuns the session and manages production state.
Crew / AuthorsPrepares content, assets, rules, scenes, and cues.

How is content authored and reused?

Content is authored in eWrite, organized through Storyboards and production surfaces, and reused through the Library and Workshop rather than being reconstructed inside each live session.

eWrite

Structured authoring

Markdown-based manuscripts, Rulesets, and Skill Directories.

Storyboards

Spatial planning

Cards, columns, rows, bands, and production structure before live staging.

Library / Workshop

Reusable content

Scenes, assets, metadata, composition, storage, and permissions.

Greenroom / Trailers

Participant identity

Character, player, profile, and participation surfaces associated with a Show.

The intended product direction is system-agnostic at the platform level and game-specific at the content level: a game’s rules and authored material should be usable inside the VTT instead of being reconstructed from generic components for every session.

Where is Victory deployed?

The public explainer and the live application are deployed separately. This keeps public documentation and release links available even while the live runtime changes during alpha development.

Public websiteCloudflare Pages

Static product information, comparisons, licensing references, and release links.

Live applicationSeparate application deployment

Go services, PostgreSQL, WebSockets, Caddy, and browser clients.

Windows consumer pathPublic alpha installer

Installer with automatic update support through the public release repository.

Linux / Debian pathSource and deployment files

Podman deployment materials are available; no packaged Debian installer is currently published.

browser client
    ├── HTTP / application requests ──> Go services ──> PostgreSQL
    ├── WebSocket session state ──────> live Showing state
    └── local renderer ───────────────> PixiJS stage composition

authoring surfaces ──> persistent Show content ──> Showing ──> Showtime
Discord integration ─> optional presence / chat / voice-adjacent state

Engineering history and milestone records are maintained in the Victory repository’s Construction/History directory ↗.

What is persistent, and what is session state?

Persistent state belongs to a Location or Show: authored manuscripts, rulesets, scenes, rosters, assets, and production structure. A Showing references that material for a particular session. Showtime is the transient live state produced while participants are connected.

Clients do not need the same interface surface. Audience, Cast, Director, Producer, Crew, and Author roles are different access and presentation contexts over the same running production. The current alpha is still refining the boundaries between role permissions, content visibility, and live controls.

That distinction is also why the product is not described as a collection of unrelated panels. Authoring and preparation are intended to produce durable material that the live runtime can consume, while live interaction should not silently replace the canonical authored source.

What should a technical evaluation assume?

Assume a public alpha, changing interfaces, and incomplete operational documentation. The current site describes the implementation that exists or is actively represented in the repository; it does not promise feature parity with established VTTs, production uptime, or a finished content ecosystem.

For a meaningful evaluation, build a small scenario, author the rules and reference material, run one Showing, and record where the workflow requires manual reconstruction. Those observations are more useful than comparing isolated features such as maps, lighting, chat, or player views, which are common across virtual tabletops.

Engineering history, release artifacts, and licensing documents remain the authoritative references for their respective subjects. This brief is a current implementation summary and should be updated when those sources change.