// the take
A container image that automates installing, licensing, and running a Foundry Virtual Tabletop server, so you don't hand-roll the Node.js install and config yourself. It's for Foundry VTT users who want to self-host on Docker, Podman, or Kubernetes rather than pay for Foundry's own hosting. It's a deployment wrapper, not a Foundry alternative — you still need a paid foundryvtt.com license.
Supply chain hygiene is unusually serious for a hobby-adjacent project: SLSA 3 provenance, CodeQL scanning, OpenSSF Scorecard, multi-arch builds down to ppc64le and s390x. The download cache coordinates across simultaneously-starting containers so a shared cache only fetches each release once instead of racing. It bundles the official `fvtt` CLI, pre-configured with the container's paths, so pack/unpack workflows work with a plain `docker exec` and no extra setup. Deployment docs cover real production concerns (Caddy/nginx reverse proxy, Cloudflare Tunnel, k8s with Kustomize overlays) instead of just a bare `docker run` example.
The hostname-to-license binding is a sharp edge: if you don't pin a stable hostname, the container gets a random ID on every restart and silently fails license verification afterward — easy to hit on first try and confusing to diagnose. Config files (`options.json`, `admin.txt`) regenerate on every startup by default, so any change made through Foundry's own setup GUI gets wiped unless you remember `CONTAINER_PRESERVE_CONFIG`. Updating Foundry itself means pulling a new image and recreating the container by hand since the in-app update tab is disabled — there's no in-place upgrade path. The bundled `fvtt` CLI is missing entirely on s390x because its LevelDB dependency won't build there, so platform parity is incomplete despite the image itself shipping for that arch.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →