Victory vs Foundry VTT

Foundry is the choice when ownership and control matter most.

Foundry VTT is a mature, self-hosted platform with a one-time license and extensive customization. Victory is a public-draft experiment aimed at connecting authoring, preparation, production, and live presentation around a persistent campaign.

Last checked: September 20, 2026Foundry official site ↗

Feature comparison

QuestionVictoryFoundry VTT
Best fitPeople who want to test an early, browser-based workflow built around authored worlds, preparation, and production.Groups who want a powerful, customizable VTT they can self-host or place with a hosting provider.
AvailabilityPre-launch public draft; early access is collected through the Google Form ↗.Released product with downloadable software and browser-connected players.
Hosting modelThe live application is separately deployed; users do not self-host the public marketing site.Self-hosted by default, with official guidance for self-hosted, cloud-hosted, and partner-hosted setups.
Core playLive stage, maps, tokens, cues, drawings, and a dedicated audience-facing mode.Full virtual tabletop platform with a broad ecosystem, customizable systems, modules, and browser-connected players.
Authoring and prepeWrite, Storyboards, Library, and production spaces are designed as connected parts of the workflow.Strong extensibility and content ecosystem; the official product positioning centers on the VTT, systems, modules, and self-hosted control.
Data and controlStill being developed as a hosted product; export and operational details are part of the public-draft work.Foundry emphasizes self-hosting, control over the game experience, and ownership of your data.
PriceFree for noncommercial use. Official branded Small Commercial Use is free up to $2,600 in Victory-Related Revenue per License Year; published tiers above that start at $49/year.Foundry’s official FAQ currently lists a $50 USD one-time license; hosting may add cost.
Confidence levelOne alpha tester so far; product claims are intentionally limited.Established product with a mature documentation and module ecosystem.

When to choose each

Choose Foundry

If you want control now

Choose Foundry if self-hosting, owning your data, customizing the platform, and using a mature ecosystem matter more than having a managed workflow.

Choose Victory

If the workflow is the experiment

Try Victory if authoring material, arranging scenes, managing production, and revisiting a persistent world are the problems you most want explored—and you are comfortable with a public draft.

Choose both

If you want to compare in practice

Keep Foundry for a real campaign while testing Victory with a small alpha scenario. Compare the preparation experience rather than making unsupported claims about feature parity.

Sources and caveats