FoundryVTT
Foundry Virtual Tabletop (FoundryVTT) is a highly extensible, self-hosted virtual tabletop for running tabletop RPGs through a browser, focused on customization, community modules, and a one-time license model. Its core purpose is to host persistent campaign state and enable deep automation and UI extensions through a versioned JavaScript API.
It is aimed at GMs, small teams, and developers who want maximum control and extensibility. Foundry recreates core tabletop problems: maps, tokens, dynamic lighting, fog of war, shared scenes and actors, and automation of rules and character systems. It removes recurring hosting fees via a one-time host license.
Use Cases
- Run weekly home campaigns with custom house rules and maps.
- Build reusable character sheets, macros, and token automation.
- Play remote synchronous sessions with shared scenes and state.
- Prototype turn-based workflows or scripted demos for teams.
- Facilitate collaborative scenario design using a visual shared canvas.
- Test tablet viewing with TouchVTT and mobile improvement modules.
Strengths
- WebGL canvas (PixiJS) enables dynamic lighting and fog effects.
- Document model (Actors/Items/Scenes/Journals) provides structured game state.
- Modular architecture supports community modules and a package marketplace.
- Comprehensive JavaScript API for building systems, automation, integrations.
- Players join via modern browsers without per-player purchases.
- One-time license for hosts yields predictable, non-subscription cost.
- Self-hosting suits teams needing full control (Coolify deployment trivial).
Limitations
- Limited native mobile support; tablet usability depends on modules.
- Advanced features often depend on community modules of uneven quality.
- Operational overhead requires a technical owner for configuration and updates.
- No built-in voice or video; external tools required.
- Moderate vendor lock-in if heavily extended (migration complexity unverified).
Final Thoughts
Try Foundry now if you need deep customization, automation, and a predictable one-time hosting cost; it suits groups with a technical owner and willingness to use community modules.
Choose a managed cloud when you need zero administration, built-in services (for example voice/video via third-party hosting), or enterprise SLAs that a self-hosted setup does not provide.